Citiverse è uno spazio aperto a tutte le comunità. Se vuoi aprire un gruppo locale o una sezione per la tua organizzazione, puoi contattare gli amministratori: pagina dei contatti.
I'm reading through some of my #Mastodon post/repost/reply history to find something I thought I'd linked to a while ago.
-
I'm reading through some of my #Mastodon post/repost/reply history to find something I thought I'd linked to a while ago.
I've noticed a couple replies seem to have lost the thread they replied to. Is that a bug with today's 5.0 update?
If I could "view source" on a post to see the underlying #ActivityPub event, I might be able to find the thread myself, but I guess the UI doesn't provide that? Anyone remember the API to fetch that?
aha, it's: GET /api/v1/statuses/:id
The API returns an empty in_reply_to_id. Now the question is... is that because I missed providing that ID in my original reply? Or because the server lost it?
-
aha, it's: GET /api/v1/statuses/:id
The API returns an empty in_reply_to_id. Now the question is... is that because I missed providing that ID in my original reply? Or because the server lost it?
After much more spelunking, it seems to be that:
1) The author of a status I replied to deleted the original status.
2) Instead of giving me back my status with its original in_reply_to_id, Mastodon rewrites history to make it appear as if I I'm just talking to myself.
I was only able to verify this because I have my own backup of my mastodon history, which Mastodon can not rewrite.
-
After much more spelunking, it seems to be that:
1) The author of a status I replied to deleted the original status.
2) Instead of giving me back my status with its original in_reply_to_id, Mastodon rewrites history to make it appear as if I I'm just talking to myself. I was only able to verify this because I have my own backup of my mastodon history, which Mastodon can not rewrite.
This is the kind of thing that made me originally write #Diskuto and now it's making me want to work on the next version.
I have mixed feelings on that.
-
After much more spelunking, it seems to be that:
1) The author of a status I replied to deleted the original status.
2) Instead of giving me back my status with its original in_reply_to_id, Mastodon rewrites history to make it appear as if I I'm just talking to myself. I was only able to verify this because I have my own backup of my mastodon history, which Mastodon can not rewrite.
@NfNitLoop are you sure of that one? This doesn't sound right. That would be rn emense amount of extra work for a mastodon server to do.
-
@NfNitLoop are you sure of that one? This doesn't sound right. That would be rn emense amount of extra work for a mastodon server to do.
@liaizon I'm using "rewrites history" loosely here. It's serving me my old status with its in_reply_to_id missing, even though the original had it.
Maybe what's actually happening is that it still has that ID in its database, but just doesn't expose it via the REST API because that ID is marked as deleted. But from the outside, the effect is the same.
-
@liaizon Here is my reply.
-
@liaizon I'm using "rewrites history" loosely here. It's serving me my old status with its in_reply_to_id missing, even though the original had it.
Maybe what's actually happening is that it still has that ID in its database, but just doesn't expose it via the REST API because that ID is marked as deleted. But from the outside, the effect is the same.
@liaizon My test confirms it:
-
@liaizon I'm using "rewrites history" loosely here. It's serving me my old status with its in_reply_to_id missing, even though the original had it.
Maybe what's actually happening is that it still has that ID in its database, but just doesn't expose it via the REST API because that ID is marked as deleted. But from the outside, the effect is the same.
@NfNitLoop maybe this tool is easier to check with https://browser.pub/https://mastodon.social/@NfNitLoop/117480686894226589
-
@NfNitLoop maybe this tool is easier to check with https://browser.pub/https://mastodon.social/@NfNitLoop/117480686894226589
@liaizon Nope, same problem there. On your link, you can see the inReplyToAtomUri, but on this one it is missing: https://browser.pub/https://mastodon.social/@NfNitLoop/117480686894226589
If it's just proxying to the Mastodon API, it's not going to be able to show *more* data...
https://mastodon.social/@NfNitLoop/117480686894226589 · BrowserPub · A browser for exploring ActivityPub and the fediverse
Explore the open social web through the lens of ActivityPub and the fediverse.
(browser.pub)
-
@liaizon Nope, same problem there. On your link, you can see the inReplyToAtomUri, but on this one it is missing: https://browser.pub/https://mastodon.social/@NfNitLoop/117480686894226589
If it's just proxying to the Mastodon API, it's not going to be able to show *more* data...
https://mastodon.social/@NfNitLoop/117480686894226589 · BrowserPub · A browser for exploring ActivityPub and the fediverse
Explore the open social web through the lens of ActivityPub and the fediverse.
(browser.pub)
@NfNitLoop this isn't using the mastodon api
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi
Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy