pampoon

@pampoon@lemmy.world
0 Post – 11 Comments
Joined 1 years ago

I don’t know what it means, either.

Page 0

That is 100% what they did.

You should be prompted when opening after updating to the latest version.

5 more...

Logins are returning non found errors. It’s a bug. If you had a previous session that’s as already logged in, you should be able to access it.

Bell icon at the top right. Should bring up your inbox which holds your replies and messages.

Declined the refund and picked up some shirts and pins from his merch store. $250k is a lot of income to lose out on, so hopefully any bit helps! Christian deserved it for all the work he’s put into Apollo the last decade. At least his legacy can live on through the influence he’s obviously had over the design of the Lemmy iOS apps.

I’ve found from hopping around some other instances that have upgraded to 0.18 that it is still pretty buggy. It does seem to be giving more information about the errors, instead of just failing like in 0.17, but spend any time browsing on those instances and you’re bound to be inundated with JSON and query errors. It also seems to get worse the longer you browse.

The UI changes are nice, and I do appreciate not having my feed auto-updating constantly, but I think you’d be making the right choice to hold off on upgrading until they can iron 0.18.1 out all the way. I’m not super knowledgeable about TS and Rust, but as a user it seems that switching from WebSocket created/shined a light on Lemmy’s issues with caching in general.

The refresh is, I think, supposed to be a feature of Lemmy. Basically the feed would be updated with new rankings as posts’ rankings change. However, I think it’s bugged out since the huge influx of users and supposedly the devs are working to replace the protocol used to do the update and make it not so jarring.

The fediverse directly helps with that exact problem by allowing actual instances to remain small as needed. There’s no requirement that an instance have millions of users, which is what drives up cost. Personal instances can still participate in all other federated instances’ communities.

Mastodon has been a good Guinea pig for proof positive the model can work, with something like 4 million+ active users.

0.18 is where they have swapped WebSocket for HTTP, as well as tried to fix a load of bugs related to using WebSockets (like the new posts pushing the main feeds down).

0.18.1 is meant to re-enable CAPTCHA on signups, which was removed in 0.18.

You have it right, just have to give it a few seconds when you start typing and you should get a drop-down list of options to pick which auto fills the link for you.

It is not 7

92 more...