Browsers not taking the OS style/needs into consideration and deferring entirely to websites is one of their cardinal sins. We've had CSS APIs in the spec with system styles for years and nobody implements them. Why?
Instead of every website needing to build a table of contents, web browsers should be exposing that via the accessibility tree.
Instead of every website needing to have a UI for paging, web browsers should be able to get the OrderedCollection and render the UI or however many pages you want.
Instead of websites having a million JS-riddled form rendering libaries, web browsers should be able to expose form fields however the user likes.
This should work for 2D, TUI, and 3D depending on browser
the linux ecosystem is probably the worst example of whete this fails. I have like 6 totally different app styles to deal with at any given momebt because of all the toolkits and the fact that flatpack makes it even more annoying to get the app to just use your preferred kde/gnome/etc theme 😭
I get this limits what apps can do and giving access to raw graphics is important, but it being the default makes it more of a pain for both making apps (especially cross platform) and trying to have a consistant experience as a user. Let alone the accessibility issues when apps decide they should reinvent rendering without thinking about screen readers or high contrast themes or magnification etc.
Working on some federation bug fixes for account migrations and groups, as well as a new mobile app build!
We’re writing a FEP for our federated Comment Controls feature too!
it was building on my research into non-english programming languages and Arabic programming languages in particular. The idea was to try and build a programming language that was not anchored to any particular writing system.
The observation I made was that this becomes impossible because of how names work in programming. to use a library someone else wrote you have to use the exact names that they exported for their functions etc. so you are forced into linguistic parity with them.
I've just been told that Apple are transitioning to cleartext iBoot images. We already knew there wasn't anything naughty in iBoot (decryption keys had been published for some systems/versions, plus it's tiny anyway and doesn't have space for networking stacks or anything like that) but this means that, going forward, the entire AP (main CPU) boot chain for Apple Silicon machines is cleartext, as well as SMC and other aux firmware that was inside iBoot for practical reasons.
The only remaining encrypted component is SEPOS, but it's optional and we don't even load it yet for Asahi Linux. All other system firmware other than iBoot and the embedded SMC/PMU blobs was already plaintext.
That means that there is no place left for evil backdoors to hide in the set of mutable Apple Silicon firmware. All updates Apple publishes going forward can be audited for any weirdness. 🥳
(In practice this doesn't really change much for the already-excellent privacy posture of Apple Silicon systems running Asahi, which have always been way ahead of anything x86 since there's no Intel ME or AMD PSP equivalent full-system-access backdoor capable CPU, but it helps dispel some remaining paranoid hypotheticals about what Apple could potentially do, even if already very unlikely.)
It's kinda funny how node.js still doesn't have first class suppport for ESM everywhere. Most tooling has migrated to it years ago and yet stuff like the new "single executable applications" feature still defaults to commonjs.
https://nodejs.org/api/single-executable-applications.html#single-executable-applications
The constant disappointment of devices like smartphones, for me, is that having a permanently-internet-connected computer full of sensors that I keep on me at all times should be a thing that I can treat as an assistive tool that is integrated into my sense of self, constantly taking in information, processing that in workflows I've created, and sharing that with me
in other words, it should be a programmable extension of the perception of the body
and the entire ecosystem around smart phones is very meant for Not That
Mayve if the wev gets overrun with shit and becomes unusable the average persob will get off aocial media and get back to physical networks and the weirdos can have their space since it becomes too unprofitable for corpos to spend as much time here. It sucks we'll miss out on some of the social benefits but the current state is automated rage bait hell which isn't great for society IMO
Why are big Instances bad for the Fediverse?
It's quite simple:
bigger instance -> more moderation work -> need for bigger team -> harder to find consensus within the moderation team -> less strict moderation
Also:
bigger instance -> more different ideologies among userbase -> harder for other instances to decide to block that instance / or greater impact on federation if big instances are blocked
Additionally small instances can't easily block big instances, because doing so would impact their own userbase a lot and drive even more people to large instances.
So big instances mean a lot more work for smaller instances, because they have to deal with much more individual bad actors instead of just FediBlocking them in bulk.
All Fediverse softwares should have a 2k limit for monthly active users, so all instances automatically temporarily close registrations when that limit is reached.
#FediverseMeta #BigInstances #FediModeration #FediMods #FediBlockMeta
Hello, world!
We are FAFO, a non-profit semiconductor and analytical chemistry research lab in Munich.
We exist to bring together people and tools necessary to advance not the cutting edge of manufacturing, but the cutting edge of making bathtub semiconductors and other Weird Hacks in your local hackerspace.
We've just rented out our first location and brought in a gorgeous 1980s JEOL T330A SEM. Restoring it to working condition is our first project, and this is where we'll keep you posted.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.