this post was submitted on 30 Jun 2023
2644 points (97.7% liked)
Fediverse
28752 readers
29 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
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
I'm using liftoff:https://play.google.com/store/apps/details?id=com.liftoffapp.liftoff&pli=1
Apk of liftoff if the google play won't let you install the app: https://github.com/liftoff-app/liftoff/releases/tag/v0.10.1
others: https://lemmy.world/post/465785 and https://lemmy.world/post/401441
Awesome thanks I'll give it a try. Using Connect right now and love it so far. Also got Jerboa and will be trying it as well.
Jerboa is nice but it's having some widespread bugs right now. Hopefully things get ironed out with the next update, but for now the instance lemmy.world is having trouble communicating with the rest of the Fediverse. I had weird issues with Connect too where it wouldn't let me post because it didn't recognize community names, despite being on the community before hitting the "post" button.
I'm browsing in Firefox at the moment, it seems stable at least.
Feeling the hit with Jerboa as well, but Firefox is running nice and smooth with Lemmy right now. Going to definitely work with more apps to see which work best.
I can't even sign in. It basically says that my account doesn't exist.
Check that your instance is correct (lemmy.world) and try again when the server works better. Right now the server seems to be having a lot of trouble loading pages, etc, and maybe that's why it's not working for you.
Yeah, seems it was a server issue. I had used the correct instance last time as well, but it worked now. Thanks!