Notices by Vyr Cossont 🏳️‍🌈🏳️‍⚧️ (vyr@universeodon.com)

@kainoa hahahahahaha no

why would i want to touch some no-name rando's third party fractional reimplementation of a hideously powerful and complex closed-source API, enormously increasing my maintenance burden to ship on a platform i don't like that runs on devices i don't have and is owned by an ad company, producing a UI that is as weird and non-native on Android as an Android app would be on iOS

@kainoa this falls under "literally wouldn't do it even if you paid me", i think. maaaaaybe if i worked at the company making the alleged translation tool.

i have similar thoughts around React Native and Xamarin

@kainoa for background, this kind of project tends to be marketed at business management desperate to ship on the other platform, but the process is deeply unpopular with devs and the results are often unpopular with users

same thought process as "we already have a mobile web app, why can't we just stick that in a web view and call it a day"

i'd expect similar criticism with the eventual macOS port of Feditext: even though Apple's Catalyst implementation of iOS APIs for macOS is quite good, much of the code underlying either platform is identical, and they had all the money in the world to make it work, there are still some gotchas and some weird UX corners to work around.

@atomicpoet @supernovae yeah they're tooooootally not gonna embrace, extend, and extinguish another open protocol. that could never happen twice. three times. four times, if you count "ruining the entire web" as one thing.

this is straight up bad news. if i wanted Meta to store everything i ever touched and use it to show ads to me and everyone i talk to, i'd still be on Facebook.

@aral remote media caches expire very frequently and yeah it's kind of embarrassing, but,

a better scenario is one where your home server can fetch missing media from the source server for the client. keeps traffic routed through the home server where it belongs, preserving privacy and caching it for everyone on your instance.

it's the web but also it's really not? AP and existing AP implementations have as much in common with email and Usenet as they do with conventional web scenarios. and if we're giving up the home server's role in caching and access control, we should be trading it for something *better* than the web at scaling, like torrents.

good morning and heads up:

Gargron wants to disable custom emoji in account display names because people fleeing Twitter complain about :verified: when they realize anyone can fake it.

*all* custom emoji in display names, because it'd be impractical to just disable :verified: and Unicode visual lookalikes such as ✔️☑️✅√ and friends. that includes pride flags, and you know, i was *just talking* about the history of Fediverse contributions from people who might fly pride flags <https://demon.social/@vyr/110118781991020640/embed>, but i've also seen custom emoji used in display names to mark programming languages, games, all sorts of communities…

*and* he likes to remind people that Mastodon™ is Trademarked, and Licensed, and thus customizing it to not do that would be forbidden: