while i don’t have any specific opinions about this that other people haven’t addressed, i just want to flag up something;
How this could be enforced? No voting from the All and/or Local feed. Seems easy and straight forward.
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.
this is how it starts. first you open one for your cat as a joke and next thing you know you’re going meow meow :3 nyaaa~~ at people online and suddenly social media starts makign sense
and nyaizes your text so all your "na"s end up "nya"s. western forks like firefish/iceshrimp/sharkey have that separate from the cat ears toggle but honestly why would you disable that?
Surely that would be possible with Authorised Fetch, yet nobody mentions the possibility.
Not really (in practice, anyway). Authorized fetch without cooperation from the remote instance only works on a per-instance basis. If you have a mutual from an instance then every follower from that instance would see your theoratical “mutuals only” post, if the only access control you have is authorized fetch.
There are some people working on circles and other ways of limiting visibility more granularly than what we have, but those will have to be supported by both ends. You may be able to hack together a gigantic mentions only thread with double digits of people on there without modifying server code too much, but the UX there would be terrible enough for that to not be viable (and certain anti-spam functionality like hellthread MRFs may end up kicking in which prevent that from federating to instances that have those enabled (especially after the recent Japanese spam attacks))
Look into opening an account on an Iceshrimp instance like fedia.social, or an Akkoma instance like 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.
nah, there are plenty of truth wannabes (freeze peach bigotry safe havens) that actively federate. just look at literally any competent server’s blocked instances list and you’ll see a few examples. there’s a reason why nobody* runs completely open federation
*: aside from people who’re friendly with that crowd ofc
(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.