Technically should be possible, it’s just likely far more difficult to implement in a PWA because you have to handle conflicts with any other gestures and web-related things
This is partially a problem with how Lemmy works at the moment. Ideally, all communities should be synchronized and shown on all instances/servers, as of now any new severs from other instances will only show up on your own instance after the first time someone from your instance subscribes. This means someone has to manually type in the url and subscribe to an external community from your own server/instance so that your own instance can “discover” that the community exists and add it to the list. Hopefully this gets better down the road—I’m sure it will—but in the meantime https://lemmyverse.net/communities is a great place to discover new communities.
I was running into this. I’ve noticed that some instances seem to have limits to how many comments you can fetch at a time, especially when there is no “limit” or “page” set. Setting “limit” or “page” or a parent id seems to avoid it. The limits for each server might be under getSite(), but if those limits are related to this issue specifically, haven’t tested it
I was running into this. I’ve noticed that some instances seem to have limits to how many comments you can fetch at a time, especially when there is no “limit” or “page” set. Setting “limit” or “page” or a parent id seems to avoid it. The limits for each server might be under getSite(), but if those limits are related to this issue specifically, haven’t tested it
Lemmy is not very developed in this area. As far as I can tell, JWTs do not expire and there are no refresh tokens. I think instance admins can manually revoke JWT tokens globally, but otherwise they are valid indefinitely. I’m hoping this will be improved,
because JWTs are already not the most secure—especially without ttls, 2fa, and refresh tokens
I am working on a Lemmy client and have noticed that the Login system is secure, but it isn’t very robust. Usually, there is something called a “refresh token” provided that automatically verifies users and lets a user stay logged in indefinitely. Lemmy doesn’t have that implemented at this time, so eventually you will be logged out by your browser as a security measure when your cookie expires and you will have to log in again. For Safari, the maximum time is 7 days before you are logged out.
So, until Lemmy implements refresh tokens or similar, this will probably be how it is on most browsers and Lemmy clients.
Yes, I started with this layout intentionally to make it easy for those using the Reddit website or app to switch over. There will be a range of themes, colors, and customizability down the road too
It’ll be starting out as a web app, and then I’ll be releasing it on iOS/Android when the web app is stable.
The main goal with this project is to create a friendly, high-quality, public-facing website that aggregates all Lemmy instances, posts, communities, etc. so that Google and other search engines will be able to index the content easily. It’ll also make Lemmy more inviting to the average person on the Internet. Beyond that, I just want to build something that’s accessible by default, supports moderators with good tools, makes community discovery easier, and just makes the whole Lemmy experience more fun in general.
It’s gonna take a lot of work, but I think it’ll be worth it!
Technically should be possible, it’s just likely far more difficult to implement in a PWA because you have to handle conflicts with any other gestures and web-related things