ok @Gargron let’s test this #quoot thing and see if it’s real
Post
ok @Gargron let’s test this #quoot thing and see if it’s real
@blogdiva
I see it the quoted post, FWIW.
I'm using phanpy in Firefox.
*siiiiiiiiiigh* don’t see it on the app
(Lenovo Tab, Android 13)
UPDATE: including image on Iceraven/Firefox (Android)
OOOH BOY
so for those of y’all following this #quoot saga:
1. on a browser, if you want to quote a post, you have to use the reply button on the post. am providing an image of this thread to show how it’s working on the browser interface
2. this reply-quote feature isn’t found on the android app yet
3. they still refuse to use the oEmbed standard that allows for rendering a link into a full toot or activity pub object… 🧵
@blogdiva It's not found on Android because they haven't released the feature to everyone, it's a gradual rollout.
@blogdiva Is this for every instance/server, or can that be changed by each admin? cc @pixelcats
@blogdiva Oof. That is not intuitive AT ALL!
so the Mastodon team is trying to literally implement #censorship as an #ActivityPub feature with quoted toots:
❝ The issue here is having a mechanism for the client to know that an URL is an AP status, then exposing the status object so it can be displayed in the client (and c͟h͟e͟c͟k͟ f͟o͟r͟ q͟u͟o͟t͟e͟ a͟u͟t͟h͟o͟r͟i͟s͟a͟t͟i͟o͟n͟) ❞
https://oisaur.com/@renchap/115225686379955802
with physical speech, the only way you can be forced into “quote authorization” is by having your fingers and tongue cut off and being banished into silence… 🧵
i cannot stress enough how beyond foolish is this whole quoted toot debate. it’s literally political.
YOU DO NOT NEED CONSENT TO QUOTE ANYBODY
there is a reason #fairUse is a standard of free speech in so-called democracies. only authoritarian systems demand to inspect and approve what you will write beforehand.
this is LITERALLY what’s happening with people quoting Charlie Kirk. the MAGA fascistocracy decided they DON’T CONSENT to others quoting Kirk to show who he was… 🧵
@blogdiva Yeah the way they bent over backwards to try and implement quote consent is so bizarre. Like, nobody asked for that and it doesn't actually solve any of the problems they suggest. Such a waste of time.
there is no technological issue on rendering a toot inside a post.
here’s the page to the oEmbed standard; which hasn’t changed much since it was first created:
https://oembed.com/
there are several issues with oEmbed:
1. if your metadata sucks, your embed will suck too
2. the lazy rely too heavily on javascript for keeping the formatting intact
3. which means that it takes work to keep up with aesthetic rendering
4. if the original post changes, so does the embed
so that means…🧵
that the biggest problems with embedding posts have to do with rendering, not authorization
1. embedded posts are usually impermanent: they change if the original post changes. so quote posting, doesn’t work as an evidenciary mechanism. an image of the post would be more suitable for that.
2. since the embedded post can change, it adds a layer of web design/CSS upkeep. that’s because you don’t embed all the HTML, only the post’s content as metadata… 🧵
@blogdiva tbh. Why is this so hard. This is honestly one of the main reasons fedi 22 didn’t take off lol
We are a network of scientists, developers and organizations building the next generation of digital spaces for open science.