@kaia@brotka.st@Ollie@snug.moe I know that feel towards horses — unlike computers they seem like huge creatures that could make short work of you if the opportunity arises, but they are operated by forces of nature so you barely know how to interface with them. People don't seem as dangerous — you can mess with their minds, but horses — no, they don't care about your multi-layered bullshit. I've grown more comfortable with it as I got older, now I see that a lot of people aren't much different from horses and ultimately horses aren't THAT dangerous — they are very unlikely to attack you from the get-go, but I still subconsciously feel uncomfortable around them.
@kaia@brotka.st@jeder@miau.jeder.pl Don't you have to explain why you drive €200'000 worth of metal and wires and e-e-ew, plastic! to literally everyone except for those who are driving a similar or a more expensive piece of metal and wires and e-e-ew, plastic, themselves anyway? 🤔
@p@fsebugoutzone.org Damn, that's odd! I don't remember why I couldn't watch it then, I've even made an account on Hulu — I got an email notification about five years ago that reminded me of its existence. I even remember how I got kindly told by a user support person that it's better to say that I'm from California in the request to speed things up — this is how I found out CA had a special data retention law. But back then I couldn't get to premium content no matter what, so I had to pay a visit to good old… mininova (?) or whatever was up at the time 👴
@p@fsebugoutzone.org @RustyCrab@clubcyberia.co It's not even rent seeking at this point, just plain old stupid! Brings back the day when Arrested Development season 4 got released — to like 4 (!) streaming services. Choice, right? All of them were regionally locked though, meaning I couldn't pay for the subscription with a card issued by a non-US bank 😩 So no matter if I'm downloading it or not, either way you don't get paid.
@icedquinn@blob.cat And dbus is almost XML RPC! Why do people like XMPP, but hate dbus? It's like XMPP over UNIX domain sockets… for the shit you often don't need 🤔 But anyway — almost the same thing!
@p@fsebugoutzone.org https://github.com/simonrob/email-oauth2-proxy It's in Python so it's kinda wasteful — even without the GUI (I run it on a headless system), but it's the first one that I found and it got the job done. At least fetchmail can retrieve the messages fine. msmtp fails on my end, but I think it's something trivial to fix — never cared enough to look into it, in theory SMTP should work too.
@p@fsebugoutzone.org GMail no longer supports SMTP and IMAP? I think it does — you have to use a tiny proxy that translates normal SMTP and IMAP authentication to OAuth2 gibberish. I do this for Outlook — it works… most of the time 😅
@kaia@brotka.st Just give yourself a week to approve their requests, in this case they won't remember why they sent this request in the first place, if they don't like your most recent posts, they immediately unfollow — works every time.
@Kusojiji@freesoftwareextremist.com@SilverDeth@fsebugoutzone.org@p@fsebugoutzone.org I remember Loom having a spell mechanic based on short music phrases, you could find new spells by listening to sounds in the game world, to achieve reverse effect of the spell you had to play the notes in reverse order. On hard difficulty you had to use your ear to figure out spells, on easier the notes were additionally colour coded making it a bit easier.
@p@fsebugoutzone.org I've just given up on Go at this point — not only the implementation, but the language itself keeps changing too fast, with Rust no one promised something stable and even Rust isn't that bad. God knows, I tried keeping up with it — 32-bit PowerPC is no longer supported, but I've built the latest version of gcc-go that works on the machine this instance is hosted on, which is Go 1.10. I've backported Bloat to it and it works fine on this machine, but beyond it — backporting is too much effort. And it's not about essential things, it's no longer the language that "Go Programming Language" book is about, it's something else entirely. Like "Ya-ay, let's re-do iterators" — and no, some internal unification in the standard library does not sound like a good enough justification to me. But Go community seems to like it that way, go to HNews and you'll see articles like "I redid everything with new iterators so now you can't build my module with older toolchain". WTF did you do that for, just because you could? And it seems a lot of people weren't keeping up, so they have added an option to add a line to go.mod that forces a particular version of toolchain which… gets downloaded from the Internet — just like that. No, Google, it's not supposed to work like that, so fuck you! Just fuck you! In a lot of environments you can't do things like that and I can't do it like that because you have dropped support for the machines I want to run my tiny piece of software on. I'm not a corporate samurai, who builds only for the latest Intel and 64-bit ARM, hoping that it might also work on something else. So I'm out!
Go 1.20 might seem chosen almost arbitrarily, but it can build all the software in Go that I still use. I'm not relying on any other software in Go and not using it for my personal needs because it's cancer — Google has killed it for me.