#monsterdon

bobert

#monsterdon happens pretty late in Germany, so I wrote a little script to record the toots and play them back later. Then that turned into a whole thing: https://monsterdon-replay.gerlach.dev

You can replay the timeline for the last 116 monsterdons.

Solarbird :flag_cascadia:

@combatwombat oh my gods

this is amazing

Robert W. Gehl

@moira @combatwombat

agreed, this is cool as hell.

It keeps the (public) posts in context, so that's a big plus.

If someone deletes their old posts, are they also removed?

bobert

@rwg @moira No, they stay. It's not a continous sync. I'm not sure if that's ok though... On the one hand, if you publish something on the internet, it's out there forever (this site being an example of that). On the other hand, it's not nice to keep stuff against peoples will.

Robert W. Gehl

@combatwombat @moira

Right. I would work on that, because some folks may want to delete their stuff. Not doing so would probably be interpreted as scraping.

I'm not sure how you'd implement that, but I'm raising it as an issue.

Solarbird :flag_cascadia:

@rwg @combatwombat There's also a question of how do you tell deletion from an instance going down (not the same) and so on.

Robert W. Gehl

@moira @combatwombat

oh, yeah.

I don't know how these reply feeds are populated -- maybe polling the source once every X days and updating would work? (that way, if the posts are deleted, they'd disappear, but if they are from a server momentarily down, they will reappear in your replay)?