Just another Swedish programming sysadmin person.
Coffee is always the answer.
And beware my spaghet.
This looks really odd in relation to other fediverse software; Why /magic
and required to be on the root of the domain? Why hard-require routing the domain part of the user ID when .well-known/webfinger
exists? Why is there a X-Open-Web-Auth
header which the spec only describes as “its purpose is unclear from the code”?
So many questions.
I definitely like the idea of distributed sign-in, Solid did a decent work of that many years ago after all. This particular proposal just looks rather odd.
Still far too new a game, thinking of something from before the second millennium.
Deranged jazz and cool shades.
Yeet!
Freeing monsters through the power of the throw
Psychonauts?
Dungeon Siege (2002) is a nice RPG; 3D, isometric-style default camera, slightly tactical order-based movement/attack, and a fully streamed world - so no loading screens during gameplay.
It certainly has its fair share of jank as well, but it does well otherwise.
Are you planning to also do something like the Black & White multiplayer mode?
This actually looks surprisingly good, will definitely have to check it out once released.
Well, looks like there might be another few hundred hours of city building in my future.
Give me more Ayoade in gaming any day of the week.
The Battle for Wesnoth is one of those oldies but goldies when it comes to Linux gaming.
I’d also heartily recommend trying out OpenMW (not just because I’m part of the team there) as a modern way to play Morrowind, though the upcoming release is not entirely finished, there are a few blockers being hammered away at still.
Been slowly working my way through Shadow of War, between probably a bit too much Against the Storm, Surviving Mars, Stellaris, and Timberborn.
The design of IPFS - using content-based addressing with append-only interactions - makes deleting/revoking basically impossible to implement, let alone guarantee.
There’s the dat protocol (now hypercore by holepunch) that handled this better, with content being addressed by key instead, so that the owner of the private part of the key could modify content after “uploading” it.
Unfortunately, hypercore still hasn’t really reached that stable point where you’d like it to be for developing a software like this on top of it.
Honestly, something IPFS-based would probably be a reasonable answer, but I don’t think anyone’s made a generic image hosting system on it yet.