this post was submitted on 12 Jun 2023
495 points (99.8% liked)
Technology
37739 readers
439 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Touch and feel is comfortable (if I can remember to middle-click links so I don't keep closing Lemmy tab), communities are growing, framework looks robust. My only concern is that if I ever move from one server to another (if I decide to self-host), it appears I'll need to manually rebuild all of my subscriptions which sounds painful.
You can always ask the owner of the instance to get your sub list directly from the database. I know I wouldn't mind.
Adding it to your own might be cumbersome, but it's a thing you only do once
A built-in profile export/import feature would be phenomenal.
It would be awesome, however I'm a bit skeptical on the technical possibilities around. While I think it's definitely doable, the amount of inter-node chatter this can cause could be massive. And then at some point somebody would absolutely try to import a user who has never asked to be exported in the first place. Massive DDoS potential.
I really hate sounding like a naysayer, but I'm wouldn't be holding my breath out for this one.