Is it possible to automatically subscribe to all (federated) communities with the same name?
Example in the screenshot: I want to follow !astronomy, and I don’t really care whether the content is coming from from Lemmy.World, kbin.social and mander.xyz - I just want to see it all.
Obviously I could manually subscribe to them all, but is it possible to do so automatically? Ideally if a new similar community pops up on another instance, I wouldn’t miss it.
I read here that community grouping is a thing, so that instances with identical communities can work together. Is that a feature that could work towards this end?
I’m making an App for Lemmy and I’m planning on adding that feature. I also want to make it so you only have to register once and the App can register you to all the instances you choose automatically.
Edit: The Webapp is Nemmy, also the Communiy !nemmy@lemmy.world
Edit2: Please note that Nemmy is early Alpha, so not really useable as a daily driver yet.
Beep boop bop, for some reason I got a reminder and you didn’t, so here is your human-generated reminder:
3 hours have passed. The name of the app has since been posted: Nemmy
It’s a web app? Lemmy’s CORS settings are messed up, I assume you have to route all requests through a proxy?
That was a nightmare for my app
Yeah, it’s a web app. I route all requests through my own backend, so it’s server-server communication between Nemmy and any Lemmy instance, circumventing CORS by design.
Are you sure the CORS settings are messed up? I tried reaching the API a couple of times from my frontend for debugging and got errors due to authentication security. Are you referring to that or something else?
You’ll get a “Forbidden” error and if you check the request, it’ll say “Forbidden: Cross origin requests are not allowed”
-
We need a central registry of communities, aka subreddits, and users.
-
Figuring out if two posts are identical is going to be a challenge.
-
Some people are going to cross post but post slightly differently on each instance because they don’t know if their post will be federated
-
Maybe group by hashtag instead of community name?
-
We should steal the ideas that were good with Reddit and Twitter
Figuring out if two posts are identical is going to be a challenge
I think I could deal with duplicates pretty easily by checking if different properties of the post are identical, the more are the less likely it is that the post will be shown.
I think a bigger problem is the comments. What if a user reposts a post from r/astronomy on lemmy.world to c/astronomy on lemmy.ml? Which one do we show, and what do we do with the comments of the other? Merge them together, or just leave them? Maybe show a button on the post when there’s a duplicate und the user can switch instances?
Lots of figuring out to do, but it sounds fun!
Edit: The Group-by-Hashtag thing is also a good idea! That would of course make the whole thing less of a headache, but to make that work a lot of users need to do that.
What if users could just configure their own named groups for communities from the various instances, and when you view the group you’d see a feed from all of them?
What would be the point of registering across all servers? Is this just to secure your username?
Registering to all instances with the same username/password is just asking for trouble. They’re not all equal and some of them will get hacked somehow.
Very good point! I think @TheButtonJustSpins@infosec.pub has a good idea on how to circumvent that.
I could make my own database with hashed passwords using postgreqsl and RLS, which is pretty secure. The User then decrypts the hashed passwords once on login and is simultaneously logged into multiple instances of Lemmy to get the JWT of each instance, which is then stored in SessionStorage or even in a Cookie if the User wants to which would make this a one-time process.
On signup the User could just register to one instance and then I just generate random 32 Character passwords and hash them with the Users’ password, then get the JWTs and if cookies are enabled the that would only have to be done every year or so (or when the User deletes the Cookies).
This whole process is seems pretty easy, especially if you’ve done something like this before and I’m betting some other App Dev is already taking notes lmao.
Edit: Let’s also do a thought experiment on what data will be leaked if I did this 1:1 and the database gets somehow hacked:
For each User:
- Username (=> Gives away that you use Nemmy)
- Hashed Passwords (=> Hashed passwords cannot be read if you don’t have the original Users’ password until we have access to quantum computers which can literally crack the encryption algorithm)
How are you hashing a password with a random 32 character string? I feel like you are mixing terms here or so you combine the password and the random element first or do you mean you decrypt the hash with a symmetric algo and get the 32 char string?
Please link in a format that works for people on different instances: !nemmy@lemmy.world.
