Amikke @Amikke@qoto.org
- lang
- pl, en
Software developer, open-source enthusiast, wannabe software architect. I like learning and comparing different technologies. Also general STEM nerd.
Joined May 2021
@thor sometimes. When my dog was still alive I sometimes worried about the moment I will inevitably lose him. Obviously, that happened and it was indeed very sad, but it's better to enjoy the passing moment than worry about the inevitable. I know he wouldn't want me to be sad.
@rmikke quote post, not all clients display it. The quoted post: https://jorts.horse/@ancient_catbus/110197444611900623
Amikke
boosted
extremely ironic to see this shared by people against civilian gun ownership
Important lesson for social movements: You don't need to use the brick, but you must have one
Amikke
boosted
Baa 
Windows users are victims to stockholm syndrome, I’d like to remind everyone the following list of features is not normal or necessary:
Updates take forever and use loads of resources.
PC needs to be rebooted after installing any software.
Random software needs full control of your PC to make sure you’re not doing anything you “shouldn’t be”.
An internet connection is required to play.
Your computer talks to you? Why?
An operating system is 30GB large.
Updates are mandatory.
Advertising, everywhere, constantly.
You pay for this?
Troubleshooting anything is a nightmare, shrouded in mystery and undocumented chaos.
Amikke
boosted
@LaoBan also, this idea that you can't attach anything else if there is a GIF or video. that's ALSO not a part of the standard.
also, you're not allowed to have a poll with pictures attached.
thing is, if you make such a post from Pleroma, with GIFs and pictures together, and a poll, Mastodon will display it correctly.
it just doesn't let you create such a post. which is stupid if you ask me.
Amikke
boosted
The crazy part about this is, that Meta didn't HAVE to subvert the protocol or find ways to bribe instance admins into showing their ads.
All they had to do was **announce **they'd be supporting a supplementary protocol some time in the future, and part of the Fediverse start acting exactly counter to the ideal of an open protocol, thus starting the almost inevitable downfall of a network that worked extremely well, in some incarnations, for more than ten years.
Imagine Mail or SMS starting to fracture into cells of smaller networks, because Mail Provider A does not think their users should be able to email users from B and C, while C doesn't talk to D and D won't let you receive mail from A. Imagine not being able to send a SMS to T-Mobile number, because Sprint doesn't think you should be able to, and Telefonica blocking Cyta, because Vodafone is blocking PrimeTel...
Yeah, let's do that. Zuckerberg hasn't even entered the ring, and you already threw the towel.
Amikke
boosted
@realcaseyrollins People there and on Bluesky basically see the fediverse as extreme control freaks in endless warfare with each other, and having to pick a server knowing which servers are at war with any other is insane, and being banned, blocked or defederated for extremely innocuous things. I think they are basically correct
@thor you'd be very powerful then https://www.youtube.com/watch?v=fOWMDMTaUT4
Amikke
boosted
@thor @moffintosh not that I think that was the case in the 90s, just pointing out the extreme :p
@thor @moffintosh that's… probably true, huh. I've never thought about it. It would surely be more difficult to flip a bit in a RAM so chunky it's actually hand-woven.
@thor @moffintosh then there's also the evil bit-flipping rays from space
Amikke
boosted
Secure services are “hardened”
Insecure services are…. flaccid? 
@retr0id I'd like to read that manifesto, mime-type sniffing is quite useful and I don't see any reason to not do it except for if some dum-dum made it take priority over the declared mime-type in which case the fix is pretty obvious.
@coolboymew wdym, best waifu
@jaffathecake true, sorry, in that context I agree even if I hate that it's true. There's just something about front-end web standards always managing to choose the worst possible design that really grinds my gears.
And yeah, I forgot it's not W3C which is really nice since I generally respect W3C and HTML was a stain on them for me.
@jaffathecake completely disagree. HTML treating some tags as special cases that don't need to be closed is atrocious, and it ignoring `/>` and requiring an opening and closing tag to create an empty element is doubly so. HTML should treat all tags the same and tags with no content should have an option to self-close instead of pointlessly doubling the tag and creating noise.
Additionally, supporting `/>` in plain HTML comes with no downside as everywhere it appears it's intended to self-close the tag, and even improves resilience for cases where people used to XML and XHTML didn't know it gets ignored and used it.
Your arguments rely on the status quo of the decisions made by the W3C standard body. That body, at least when it comes to HTML, seems to really like proving itself incompetent since its inception up to today. They're like the Jim Cramer of standards, whatever they decided, the exact opposite is most likely a more sensible choice.
- lang
- pl, en
Software developer, open-source enthusiast, wannabe software architect. I like learning and comparing different technologies. Also general STEM nerd.
Joined May 2021
