[alt: youtube thumbnail with the caption "this is the best keyboard according to ai"
all keys are either : or 3. the space bar is meow meow meow meow meow meow]
[alt: "lebron james reportedly forgot to align his floor vertices" in the style of a clickbait instagram post. on the left is lebron james, crying, on the right is a screenshot from pannenkoek's recent invisible walls video]
[id: the sharkey mascot but with the deal with it glasses, a giant blunt, you know i had to do it to them hands and lightning mcqueen crocs poorly edited on top]
the difficult part isn't getting in the shower the difficult part is getting out
mnmmgrh worm worter
alternatively: why are you linking to an image at all and not just making a text post
every time I see this post it gets even bluer
tallarico's really outdone himself this time
They aren't forced to do anything. Manifest v3 is just a part of the WebExtensions API (which is not a standard and is really just "whatever Chrome does except we find/replace'd the word chrome to browser") which both Safari and Firefox chose to implement in order to make porting of Chrome extensions easier.
Before that, Firefox had a much more powerful extension system that allowed extensions quite a lot of access to browser internals, but that turned out to be a maintenance nightmare so they walled those APIs off (not a coincidence that Firefox started getting massive performance improvements after that, and extensions stopped breaking every other release) and decided to go the WebExtensions route. I have no clue what Safari was up to but I think they implemented it after.
If they don't implement Manifest v3, extensions that want to work across multiple browsers need to support both the older Manifest v2 and the later Manifest v3, which would be a burden not many extension authors would want to bother with, which would make them just say "yeah we're not supporting anything outside Chrome". Firefox avoids this problem by extending the v3 API to allow for the functionality necessary for powerful ad blocking Google removed in v3 (webRequestBlocking) while also implementing the new thing (declarativeNetRequest) side by side, so extensions that want to take advantage of the powerful features on Firefox can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.
Firefox does have it's fair share of extensions on top of the WebExtension API already (sidebar support for one), so adding one more isn't too big of a deal.
Oh no it'll federate alright.
The thing about ATProto is that unlike AP they don't seem to expect each instance to have it's own community with it's own rules and vibes. They seem to be using federation just as a way to "scale up".
If they can get any non-bluesky-the-company folk to create instances then that's just scaling they don't have to pay for and a convenient legal scapegoat for the inevitable consequences of their lax moderation. Why wouldn't they federate?
the only thing i know about powershell is that the linux binary is named pwsh which i learned the hard way after writing pow and then accidentally tab completing poweroff and shutting down my pc
in fairness that might've been a sign
If they're banned from their own instance, that ban federates out and they're completely banned off that account.
If some other instance bans them, that ban is instance specific and that person can still interact with communities and people from other instances, except the one that banned them.
you are morally obligated to pirate windows 10 ltsc
(if you must use windows)
This is exactly the reason why I myself am suspicious of anyone who tries to start shit when some instance defederates (or even implies they're thinking about defederating) from another.
Now, can "bad" defederations happen? Maybe. But the thing to realize is that each instance is it's own community, and they all differ on what they accept and what they refuse. Some will be stricter, and some will do the bare minimum to not end up being Voat 2. And that's why federation works, because you have the choice to pick where you stand in that spectrum.
The trolls need people to troll in order to not implode, and they will pull every trick in the book in an attempt to keep as wide a reach as possible. That's why anything without moderation capabilities of sort (and isn't, like, DMs or otherwise small groups only) do not work in the long term.
Good fucking riddance. Happy fizzling out in no-user-str.
A better idea would be a generic content warning system replacing the existing NSFW toggle. This would not only improve compatibility with the rest of the fediverse (which does use support CWs) but also give you way more filtering options than just "safe, tits or gore".
CWs should be applicable to both communities and individual posts, and would "stack" on top of each other. (Each post would "inherit" the CWs of it's community.)
this is true i was the wiring in the wall