Notices by muesli (fribbledom@mastodon.social), page 38

@MightyBigCar

I think you can still compile this fine with Go 1.7+, if you use the regular go get approach. I only just bumped it to 1.11 after switching to Go modules today.

@nik

I don't think it is the kernel... unless those udev rules only apply to bash for some weird reason.

Just did a quick test trying that in zsh and it failed.

TIL: #bash provides pseudo devices for TCP and UDP connections:

echo "hello" > /dev/udp/127.0.0.1/1337

or

exec 5<>/dev/tcp/www.google.com/80
echo -e "GET / HTTP/1.0\n" >&5
cat <&5

I'm baffled how I've never discovered that until today.

@d7dd0d

Awww why, thank you! 💕

@clarjon1

I did! 😂

Disclaimer: I know we have some of the harshest systemd critics over here. If that sounds like you, then you may want to ignore this post and skip to the next one 😆

Still reading and using systemd? Great! To help you generate new services and monitor your system's logs & units, I created two little tools you may find helpful!

Check out service-tools over on GitHub:
https://github.com/muesli/service-tools

@r000t

Indeed I started creating my own test cases for problematic content & API responses. We probably wouldn't need a full (running) instance installation, as simple API mocks may suffice here. At least for my use-case.

The downside is that we obviously need to keep them in sync with API changes.

@jono

Welcome to the fediverse! 😊

@grumpysmiffy

They released a fix via the Firefox Studies feature, which you can enable (and then disable again) in your Privacy Settings.

@hugo

@multiplexd

That's certainly an interesting observation! I must admit I'm not a lot wiser when it comes to Mastodon's release management.

@multiplexd

What I like better about the blurred images is that they look less like a failed image load / error message. I always found those "black holes" in the page a bit disorientating.

Wrapping errors and other changes to the errors package coming up in Go 1.13:

https://crawshaw.io/blog/xerrors

#golang

@multiplexd

I actually prefer it that way. I guess that's just a matter of taste.

@y0x3y

You can check out the "Legacy Extensions" in Firefox's settings. This should show you all the disabled extensions you got.

@feonixrift @giocomai

When you start your day and already have a bunch of awesome pull requests waiting in your inbox: 💕

@mcevnon

Falkon is great and I like it a lot, but the lack of extensions is kinda killing it for me.

@esureL

It looks like it does exactly that, yes. I'm still gathering more information and details about the situation as we speak. Will toot about any findings, as usual.

@hugo

Oh, so you still got a running instance and just wanted to install a new addon right now?

Tough situation, really. I probably wouldn't risk it.

@hugo

Maybe restart Firefox. I must admit I haven't tried it myself so far. I kinda don't dare to restart my browser right now, since I badly depend on a few extensions 😆