this post was submitted on 16 Aug 2024
22 points (100.0% liked)

Free and Open Source Software

20886 readers
20 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago
MODERATORS
 

So I just updated eternity and I cannot see any posts. Anyone have a similar issue?

top 15 comments
sorted by: hot top controversial new old
[–] Starfighter@discuss.tchncs.de 9 points 1 year ago (1 children)
[–] sleepybisexual@beehaw.org 1 points 1 year ago

Didn't work for me

[–] FlareHeart@lemmy.ca 9 points 1 year ago (1 children)

I'm using Voyager and everything's been good for me.

[–] sleepybisexual@beehaw.org 1 points 1 year ago

Havntt tried that client, but I fixed my issue :3

[–] ililiililiililiilili@lemm.ee 5 points 1 year ago (1 children)

Eternity is working fine for me. Try logging in again (or clear the app's data and then login).

[–] sleepybisexual@beehaw.org 1 points 1 year ago

I did. I even uninstalled. Still broken

[–] 68silver@beehaw.org 3 points 1 year ago (2 children)

Yep having the same problem. Logging out and back in did not help. So I rolled back to previous version.

[–] Cube6392@beehaw.org 4 points 1 year ago

I wonder if its because Beehaw is staying on 18.x while awaiting Sublinks

[–] sleepybisexual@beehaw.org 1 points 1 year ago (1 children)
[–] sleepybisexual@beehaw.org 1 points 1 year ago

Rolling back worked

[–] user@lemmy.one 1 points 1 year ago

I use summit and jerboa as backup.

[–] IrritableOcelot@beehaw.org 1 points 1 year ago (1 children)

Yeah...Eternity 0.2.1 doesn't work, Voyager can't even find beehaw.org in to log into it, and so I've been using Jerboa as a backup. Turns out downgrading to 0.1.2 does work, but meh.

[–] sleepybisexual@beehaw.org 1 points 1 year ago

Yea, currently on jerboa too

[–] coja@lemmy.ml 1 points 1 year ago

Try Voyager

[–] BrikoX@lemmy.zip 1 points 1 year ago

It's not mentioned, but I think the compatibility layer for 1.19 releases breaks support for older versions. Ask your instance admins to update the backend.