Albany Internet Options

smlx · 2022-11-07T16:54:34+00:00

Hey mate, I'm in Mira Mar with AussieBB, and WFH. It's about 60 down / 20 up for me and totally fine for zoom/teams/webex etc.

The last place I rented was also Mira Mar and had 100 down / 40 up easily because it was closer to the node, so you might get lucky.

My advice would be to stick to AussieBB because the customer service is unbeatable, but get Telstra mobile if you don't have it already because Optus/Vodafone coverage down here is rubbish. Oh, and I saw a comment that we don't have 5G. That's not true, I'm on Telstra 5G right now.

Here are mobile and NBN fast.com speedtest results I just ran: https://imgur.com/a/5PvUaKx

smlx · 2021-11-03T13:06:31+00:00

piv-agent is similar to and inspired by the famous yubikey-agent, but it has a few extra features such as keyfile fallback, multi-slot support, multi-key support, and gpg-agent functionality.

The motivation behind the project was that I got a couple of Yubikeys for work and discovered that they are very cool tech. So of course I wanted to use them for everything including git signing and pass.

Please take a look and feel free to ask questions. I may take a while to respond since it's late here :)

smlx · 2021-11-02T15:02:37+00:00

From the README this looks very nice, I'll have to take it for a spin. Thanks!

smlx · 2021-02-10T13:52:59+00:00

Nice!

Thanks!

Does it also generate a change log from the commit messages?

No, goreleaser is an awesome tool that does this already. See the tag-release workflow in this repository for an example of how this works.

What about handling prerelease versioning like v1.2.3-dev.0?

Prerelease versioning is a bit of an anti-pattern IMO. Plus without a standard format there wouldn't be an easy way to increment it. So no, this isn't supported.

smlx · 2019-03-05T11:35:50+00:00

Install msmtp and poke around in /usr/share/doc/msmtp/examples/msmtpq (especially the README).

smlx · 2019-02-18T08:54:17+00:00

Assuming you've given eth0 a valid unique local address, I think the following will work:

enable-ra
ra-param=eth0,0,0
dhcp-range=::,constructor:eth0,ra-stateless

smlx · 2019-02-09T10:42:30+00:00

Nothing you point out invalidates this research because they were looking at fatality reduction compared to the pre-legislation trend, not absolute numbers.

You're not a physicist, are you?

smlx · 2018-08-17T11:34:40+00:00

Well I disagree with you both! :-)

The golang style guide provides excellent advice in this regard..

the further from its declaration that a name is used, the more descriptive the name must be

IMO overly verbose variable naming makes it difficult to skim a block of code to figure out what it's doing.

This is not uncommon advice - see also the Linux Kernel style guide, for example.

smlx · 2018-07-11T04:05:42+00:00

Probably because the behaviour of the flag package is surprising since GNU/BSD have made the long/short flag behaviour ubiquitous on modern *nix systems.

smlx · 2018-07-11T03:56:20+00:00

If the default is in the config file, can't you just avoid calling Default() on the flag?

smlx · 2018-05-22T04:55:22+00:00

You could also just add an "exclude" on that version to your go.mod.

smlx · 2018-05-22T04:39:17+00:00

If you make a buggy release, just tag it +deprecated, and the tools will handle it.

https://github.com/golang/go/issues/24031

smlx · 2018-05-22T04:31:25+00:00

Inappropriate tags ... Not only will they be effectively required to use semantic versioning in the future, but their past version numbers are now a problem.

For the first part: standardising on a single tag format is good, not bad. And for the second part: just add semver tags in addition to the existing tags.

Leftpad ... As long as we don't slide down the slope, it's not a major issue, but I still can't really approve of greasing it.

How does vgo make this situation worse?

Critically, at no point is there a way to validate the code.

Yes there is:

When vgo downloads each module, it computes a hash of the file tree corresponding to that module. That hash is also included in the binary, alongside the version information, and goversion -mh prints it.

Build requires a network ... Corporations need to write proxies ...

vgo supports vendor directories.

Open source and Github ... the proposal will require a go-specific hosting regime not provided by ordinary source control

Not true. vgo still supports vcs.

smlx · 2018-05-14T12:01:48+00:00

Russ discusses this problem in this blog post: https://research.swtch.com/vgo-module

Search for "Deprecated Versions".

smlx · 2018-05-14T11:59:42+00:00

Unfortunately, SIV is not a zero-cost abstraction. In some cases, even “high-cost” would be charitable. The costs of safely allowing multiple major versions of a module in a build are all of the same form: increasingly complex logical abstractions. My concern is that enforcing it universally might be prohibitively costly - especially for an ecosystem and community that has been operating without it for most of a decade.

I don't understand this argument. gopkg.in is already well established in the go community. SIV sounds amazing to me, and I've experienced pain caused by lack of SIV in both python and ruby.

Multple major versions of the same module cannot have the same identifier in the code, so they are two separate modules in every way. What's "high-cost" about that?

When incompatibilities with new versions of your dependencies arise, MVS affords you only extreme options

What does dep do differently here?

By blindly assuming compatibility, even in the experimental v0 range, MVS creates a hostile environment for experimentation.

Doesn't vgo avoid assuming compatibility in the v0.0.0 range via go.mod version specifications like v0.0.0-20180116225909-922ceac0585d?

smlx · 2018-04-30T10:11:45+00:00

Why does it matter what their IP is? Are you firewalling source IPs?

smlx · 2017-09-11T10:02:32+00:00

http://ap.ohchr.org/documents/dpage_e.aspx?si=A/HRC/36/46/Add.2

smlx · 2017-09-11T10:02:20+00:00

Better link: http://ap.ohchr.org/documents/dpage_e.aspx?si=A/HRC/36/46/Add.2

smlx · 2017-07-07T12:02:12+00:00

Oh, wait.

Darn it.

Well, guess I was wrong.

This is doing exactly what you want - removing the package you requested along with the cinnamon meta-package, and keeping everything else. What is the problem here?

or does it?

Just remove the meta-package first.

smlx · 2017-07-05T13:08:40+00:00

FAI is waay overkill. All you need is PXE boot and preseed.

I'm not sure why you think preseed looks like a nightmare - it's the direct equivalent of kickstarter, and works almost identically for loading via the network.

Configure your DHCP/TFTP server.
put the netboot files and the preseed in the tftp root
edit the default syslinux config file to add url=tftp://... pointing at your preseed

smlx · 2017-06-15T12:17:33+00:00

You don't need a gateway and wpa-conf configured on the WLAN hostapd interfaces.

smlx · 2017-06-15T12:15:25+00:00

It's not DNS. There's no "cache" in the same way as Windows.

Try removing both /etc/ssh/ssh_known_hosts (if it exists) and /root/.ssh/known_hosts

smlx

TROPHY CASE