Just because you wish to talk about your own country does not mean I want to listen to the politics of a country I am not a citizen/resident of nor have ever set foot in. That’s what content warnings and other functionality allow me to do. Unfortunately, Lemmy.

(Also notice how I specifically single out “US politics” and not “politics” in general. That is a different thing where “politics” is sometimes used to mean “anything I don’t like not from a white cis het from the upper middle class person”. That is not the case here. I am simply tired of hearing about Trump and Biden and Harris and whoever the new VP is or whoever the Republican Main Character of the day is or the Democrat Main Character of the day is)

True, that will at least let you figure out what is a fediverse link and what isn’t. Most implementations I know either use the same URL for both the AP representation of a post and it’s HTML one (differentiated by the Accept header), or have a redirect from the HTML view to the AP representation when an AP type is requested (or, very rarely, the via Link header/<link> html tag), which means you can reuse code used for the “search URL to load community” feature in order to make this possible.

Given the list of fedi instances your instance is aware of is already present in the API, clients already have the tools to do this, I believe.

How do you expect for that auto-detection to work? Just a regex on example.com/c/community? What happens when some other instance software decides to use a different URL format? Or do you just assume Lemmy is the only thing out here?

Doesn’t help. Everything from the meme/joke/fun communities you’d expect people to use to tune out The Horrors™ to discussion about the ActivityPub standards (what little exists that doesn’t conflate it with Just Lemmy or Just Mastodon) devolve to US politics in like two comments. For me at least this entire section of fedi is a US politics-radioactive one I try spending as little time as possible (that includes posting non-politics!)

I find myself having significantly more fun on the microblogging side of the fedi, ruining jokes to ground in like 4 minutes with my oomfs and making followup meta jokes about how jokes only last 4 minutes. People actually use content warnings to hide away The Horrors™ when they want to talk about it, which means filters actually work. (Things like alt text for images also helps with word filters!)

this is what happens when lemmy tries to handle microblog content not specifically tailored to it’s exact quirks

Look into opening an account on an Iceshrimp instance like https://fedia.social, or an Akkoma instance like http://pleroma.envs.net. Their APIs are an extension on top of the Mastodon APIs (and both support Markdown and should expose them to apps). Sharkey also has some Mastodon API compatibility but it’s quite broken and might require some odd workarounds to get stuff working.

That said, for rich text, parsing the HTML will be more than enough for nearly all cases.

(vanilla) mastodon does not have markdown, and content from other instances (marked up or not) get transmitted as HTML over the wire (and the mastodon API serves sanitized HTML to apps).

mastodon forks like glitch, and clones of the mastodon API like those on pleroma/akkoma and iceshrimp do serve the markdown source AFAIK, but unless OP’s looking to… idk, support MFM (which, on a non-web app would be difficult) I don’t really see the point in that.

.world is unique in that because of its size it has kinda ended up being “Lemmy” to most people. I very much doubt the people posting porn on .world care about instances and federation and just treat .world as a centralized site

…and I thought of a web game you can make with this, if anyone’s bored and looking for something to do: https://brain.d.on-t.work/notes/9on0iba4evg40hic

• pick a random page
• find all pages nearby
• make the player guess the random page from the nearby pages
• if they haven’t guessed the exact page, compare the coordinates and score based on distance to the correct page

I have just been informed you can also see pages nearby other pages with a special URL query (apparently no interface exists for this yet)

https://en.wikipedia.org/wiki/Special:Nearby#/page/Utrecht

yeah same here unfortunately. but then I am currently somewhere I’d consider middle of nowhere

actually there was one plane crash but that’s not necessarily an article I’m interested in

(talking about microblog fedi here, Lemmy/threadiverse is it’s own thing)

don’t do hashtags. hashtags (especially common ones like #memes) are overrun by repost bots and low quality garbage.

the trick is to be on a small-to-medium instance you vibe with (1k active users seems to be the sweet spot. anything larger than 2k I’d avoid. do NOT join any flagship instances like mastodon.social), follow fun people from your local timeline, and see who they boost. and follow up the boost chain until your timeline is sufficiently fun.

how did he toot then?!

it used to have it hardcoded in software but I believe they made it an instance option a bit before the reddit exodus

if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.

threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi

re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.

git commit -m $(date)

I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about

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.

the rule of thumb here is that you should really just use one browser ad blocker. having multiple will conflict especially regarding anti-adblocker prevention (as uBO will try to hide itself and redirect to a “defused” version of an ad script and whatever other ad blocker you have will think that’s an ad and block it)

not entirely sure how well DNS ad blockers fit into this. there is a chance they could make your ad blocking detectable by blocking a request uBO intentionally lets through (possibly in a modified state), but as far as i’m aware there haven’t been too many issues stemming from combining DNS blockers with uBO and the likes.