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.
What I’m more worried about are posts relating to news mainly. Where even if the immediate first level comments are fine, there are threads that get out of hand really quickly.
I agree that while posts inherently designed to be controversial may not benefit from Active considering the influences voting has (though me being on an instance that has downvotes disabled may be influencing my view here!), Active may make it significantly easier for an otherwise innocent post to devolve into a flame war.
The main excuse for this kind of algorithm seems to be around “promoting discussion”, but in my experience tech that’s intended to promote discussion does inherently promote flame wars too, as they’re extremely difficult if not impossible to distinguish without a human in the loop. I’ve attempted to write something about this on the microblogging side of the fedi, directly influenced by this post
I’m just throwing this out there but having the default sort incentivize comments seems like it’d highlight posts meant to cause flame wars… Is that what we want out of this platform?
.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
alternatively: why are you linking to an image at all and not just making a text post
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.
.world is a newer gTLD whereas .ml is a more well known country code TLD. whatever auto linking code the lemmy UI uses likely just isn’t up to date with all these comparatively recent TLDs
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.
i tried but i can’t lookup your comment because your instance is returning html instead of activitypub data
also remember just like how lemmy has it’s kbin, mastodon has it’s interoperable alternatives.
i bet a fair bit of the complaints i hear from people on lemmy (low character count, wanting to follow topics instead of people) would be solved by trying out a misskey fork such as firefish, iceshrimp or sharkey.
i don’t think there’s any instance out there with a char count lower than 1000, and antennas are really good (why limit youself to following a single hashtag when you can follow any number of arbitrary keywords?) if you’re in a well federated instance (provided you’re ok with them not feeding into your home feed and them not being retroactive (so after you set up an antenna you’ll need to wait for new posts to filter in))
they aren’t as polished as mastodon since mastodon kinda ate everyone’s lunch in terms of developer attention (and upstream misskey is an almost one-man-show mess developed entirely in japanese which is why everyone prefers to fork instead of collaborating), but they’ve been getting really good.
just avoid flagship instances (> 1k active users) for the time being. scaling is still something not many of them have solved just yet
i was half considering boosting it outside lemmy out of context tbf
longer than a year in my case.
and yes it’s always the 3rd video
just draw the rest of the owl
It could’ve changed since then but back when I ran my own single-user instance I had bans federating in from other instances listed in my admin panel.
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.
while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;
this seems unenforcable. as in, you can’t really tell where someone discovered a post from. yeah you can just remove the buttons from those views clientside and it’ll probably work for the majority of cases, but alternate clients or modifications to lemmy-ui can simply put the buttons back in (or in cases of unmaintained or differently opinionated clients, just not remove the buttons at all). the backend can’t really differentiate which view a vote comes from. federation especially can’t differentiate which view a vote comes from.