Conversation

Notices

1. Embed this notice
   Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 03:55:31 JST Jorge Candeias

   OK, apparently venera.social is completely dead now... 😔

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 12-Jul-2024 03:55:30 JST BeAware :fediverse:

     in reply to

     @jorgecandeias there's already a "Fediverse Enhancement Proposal" for something like this.

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 03:55:31 JST Jorge Candeias

     in reply to

     This is revealing one major limitation in the whole idea of "you can move servers any time you want": it only works if the servers are still up. If the server is down, and stays down (which at this point I don't know if it's going to be the case with venera.social) you can't move. You can create a new account elsewhere, but whatever's connected with the dead account is gone.

     The #fediverse needs redundancy, methinks. Some sort of service that backs up account networks.

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 03:55:31 JST Jorge Candeias

     in reply to

     This case with venera.social (and libranet.de) is due to a database update what went catastrofically wrong. It's been getting worse and worse for the last 11 days. And at this point I'm getting somewhat skeptical that it's ever gonna get sorted out. In normal circumstances, you'd put the backups on, investigate the problem and start over.

     But what if there are no backups?

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 12-Jul-2024 04:37:36 JST BeAware :fediverse:

     in reply to

     @jorgecandeias I can in a few. Give me time.

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 04:37:37 JST Jorge Candeias

     in reply to

     • BeAware :fediverse:

     @BeAware That's pretty cool.

     You've got a link to point me to, by any chance?

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 04:41:33 JST Jorge Candeias

     in reply to

     • BeAware :fediverse:

     @BeAware Take your time. Thanks.

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 12-Jul-2024 04:41:33 JST BeAware :fediverse:

     in reply to

     @jorgecandeias I found it faster than expected. I think this is the one you would be looking for.

     https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

     Furthermore, here's the full list of current FEPs.

     https://codeberg.org/fediverse/fep

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 12-Jul-2024 05:06:24 JST BeAware :fediverse:

     in reply to

     @jorgecandeias ahh...I see.

     I was thinking that the proposal would remove the need for a cache system because you'd be in control of you. Not the instance. So if instance gets deleted, it'd be no big deal.

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 05:06:25 JST Jorge Candeias

     in reply to

     • BeAware :fediverse:

     @BeAware Got it, thanks.

     As far as I understood it, that's more of a tweak in the functioning of AP federation overall, closing the gap between the fediverse proper and how Bluesky works (and maybe opening way to full integration between the two protocols).

     My idea doesn't require any fundamental changes. It's just a service built on top of what's already there, and I can't really say how feasible it'd be.

   • Embed this notice
     Jorge Candeias (jorgecandeias@mastodon.social)'s status on Friday, 12-Jul-2024 05:25:38 JST Jorge Candeias

     in reply to

     • BeAware :fediverse:

     @BeAware It might, I guess (where'd one's data be stored? Locally on one's devices? That also can be dangerous. Distributed throughout the whole network? Hm... I dunno...), but I also suppose that you'd have a much harder time approving and then implementing something that changes stuff at the core of the whole shebang than just building a new service on top of what's working now.

     Then again, that's me talking off of my derrière. I don't know nearly enough about all this to have solid opinions.

   • Embed this notice
     BeAware :fediverse: (beaware@social.beaware.live)'s status on Friday, 12-Jul-2024 05:26:42 JST BeAware :fediverse:

     in reply to

     @jorgecandeias It would be decentralized like the rest of objects like posts and such.

     You're right though, adding something new vs using something that already exists would be a different experience and take different efforts.