Untitled attachment

Notices where this attachment appears

1. Embed this notice
   z428 (z428@loma.ml)'s status on Wednesday, 23-Oct-2024 03:41:07 JST z428

   in reply to

   @_elena Very brief summary on that: In Hubzilla, you have your posts and communication living in a channel that can have multiple clones on different instances. So in case you lose access to your main instance (because it goes down or is discontinued or the admin decides to block you), you still have access to your history in there. In Mastodon or even Friendica, such a scenario would completely strip you of all your previous data as even though you can export your full history manually, you can't re-import this anywhere except for the contacts. In some systems like pixelfed, not even a full data export is possible. Not sure whether this is an individual requirement of mine but it feels very difficult from an "own your data" perspective. On Mastodon, there's a change request - github.com/mastodon/mastodon/i… - for that which hasn't been implemented yet.

   cc @chris and @jupiter_rowland who know the Hubzilla details much better than I do. (Mostly Friendica/micro.blog user here.)

2. Embed this notice
   heluecht (heluecht@pirati.ca)'s status on Tuesday, 23-Apr-2024 18:19:51 JST heluecht

   in reply to

   @pfefferle @deadsuperhero Ich habe schon 2018 ein Issue im Repository von Mastodon erstellt, dass sich um die Problematik kümmert: github.com/mastodon/mastodon/i…

   Im Issue github.com/mastodon/mastodon/i… (auch von 2018) gibt es diesen Kommentar:
   

   I believe what we do now is convert an Article object into title + URL to the original, so you can view the post as it's supposed to be, rather than trying to display it internally. So, I think this is resolved.

   
   Ich würde mich sehr freuen, wenn sich da etwas ändern würde. Aber ich sehe es nicht als Aufgabe, dass wir um Mastodon herumarbeiten. Es gibt augenscheinlich Mastodon-Forks, die Article unterstützen. Vielleicht kann jemand einen diesbezüglichen PR stellen.