Email or username:

Password:

Forgot your password?
All posts Baa's posts Back to profile
7 posts total
Baa

I remember when Minecraft Forge used to distribute downloads through some even dodgier version of ad.fly that distributed malware, so I made a forum post warning of the dangers of it and it got deleted by a mod so I reported the mod and it got closed by the same mod (What's the point of a mod report button if the same mod can administer it?).

Glad the Minecraft modding community is looking a lot healthier these days, it was pretty toxic back then.

1 May at 10:56 | Open on mk.absturztau.be
Baa
Baa

I don't really use birdsite so I didn't really understand the sheer scale of their bot problem until I saw this video... what the fuck...

15 March at 13:29 | Open on mk.absturztau.be
:blobcatlaptop: gravitos :blobcatcomfsip:​

@Baa it almost feels like the bot creators now just slap bots for the lulz, something like "oh, your extremely expensive api? we have hands and curl, dude, we dont need it"

15 March at 14:38 | Open on wetdry.world
Baa

TP-Link have "emulators" where you can try out their Router's software in a browser before buying.
It's really useful, it convinced me not to get it at all by immediately showing me this message on login ​:ump45Disgusted:​

#routers #networking
12 February at 0:01 | Open on mk.absturztau.be
Baa

Whenver I write a README for something I've made I usually include some deployment, running, installation instructions etc.

I try to write them for someone with very little knowledge of Linux, or the terminal. While learning for the first time I ran into far too many instructions that assumed I knew much more than I did, which was very frustrated (looking at you, any guide that suggests using vi to edit basic config files).

And also, because I know in about a month's time, when I return to said instructions, I will have completely forgotten whatever the fuck I was doing and will really appreciate aforementioned instructions.

Whenver I write a README for something I've made I usually include some deployment, running, installation instructions etc.

I try to write them for someone with very little knowledge of Linux, or the terminal. While learning for the first time I ran into far too many instructions that assumed I knew much more than I did, which was very frustrated (looking at you, any guide that suggests using vi to edit basic config files).

And also, because I know in about a month's time, when I return to said instructions,...

10 February at 2:04 | Open on mk.absturztau.be
Baa

Just found this BBC screenshot I took when the Panama Papers thing was big, crazy stuff.
4 February at 1:03 | Open on mk.absturztau.be
Baa
Go Up