Should there be a service to restore your Twitter account backup and put it on the Fediverse?
-
-
evan@cosocial.careplied to evan@cosocial.ca last edited by
I'm a strong yes.
A lot of people said something like, I'd rather have LOLA.
You are correct; LOLA is better than what the poll is about.
But it's not either/or. We can have more than one feature on the Fediverse.
-
jwildeboer@social.wildeboer.netreplied to evan@cosocial.ca last edited by
@evan I have the complete backup of my 12 years on Twitter and was almost ready to put it on the fediverse as toots with a little script I made myself. But then I thought again. My posts would be without context, a lot of links wouldn't work anymore and it wouldn't serve any real purpose, ultimately. So I keep the backup on my NAS, I copied some of the pix I posted to my photo library but that's about it. Hence I voted strong no.
-
spla@mastodont.catreplied to jwildeboer@social.wildeboer.net last edited by
@jwildeboer fully agree, make no sense import them here because they could be out of context @evan
-
evan@cosocial.careplied to spla@mastodont.cat last edited by
@spla @jwildeboer there's a Web. We can preserve links to Twitter so you can see the context. And we don't have to blast things out over Mastodon; this could be a service that lets people view and react to Tweets, but doesn't send them out.
-
trwnh@mastodon.socialreplied to evan@cosocial.ca last edited by
@evan @spla @jwildeboer really depends what "on the fediverse" means. i think if it was "a program that converted your tweets to (html/as2) documents for static hosting" then that seems pretty doable. the messier part is in how the fediverse (currently?) handles fetching objects by their id -- there are a lot of expectations and requirements that come into play, like the shape that the as2 must match (or else it gets discarded as invalid), or even lifecycle of such objects (as they replicate)...
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@evan @spla @jwildeboer like, i would have to think **very** hard about whether i want thousands of servers to store copies of my ancient tweets in perpetuity without me being aware of all of them. i can do this calculus before making each individual fedi post, but doing this calculus for hundreds of thousands of tweets all at once? totally different equation.
to be clear, putting them up as html has different considerations. agents don't generally cache or reproduce html forever.
-
thisismissem@hachyderm.ioreplied to trwnh@mastodon.social last edited by
@trwnh @evan @spla @jwildeboer I quietly pretty much already have a tweets to AS2 converter written
-
trwnh@mastodon.socialreplied to thisismissem@hachyderm.io last edited by
@thisismissem @evan @spla @jwildeboer so do i, but indirectly through a much more roundabout path -- i selectively extract whichever posts i find have continuing value, then archive them on my website, which currently uses hugo and has an output format and template defined for static as2.