sockenklaus

joined 2 years ago
MODERATOR OF
[–] sockenklaus 2 points 2 years ago (2 children)

Could you please link to a post affected by this?

[–] sockenklaus 1 points 2 years ago* (last edited 2 years ago)

Which version are you on? The current version is 0.0.37-alpha and there are no known issues regarding comment replies not working in that version.

[–] sockenklaus 1 points 2 years ago

Literally unusable!

Seriously: It may not be a big problem but please write an issue on GitHub. It can be marked as low priority and may not get fixed for some time but at least it doesn't get lost this way.

[–] sockenklaus 2 points 2 years ago* (last edited 2 years ago) (1 children)

Run ./gradlew lintKotlin to check for lint errors or ./gradlew formatKotlin before commit to automagically fix them. Saved me a ton of time.

[–] sockenklaus 1 points 2 years ago

Could you please link to the post so I can test this?

I did some pull requests on Jerboas image viewer, maybe I can find a solution.

[–] sockenklaus 2 points 2 years ago

Yes you're right but this wasn't exactly intended.

[–] sockenklaus 10 points 2 years ago (1 children)

Lemmy 0.18 introduced API breaking changes namely because it switched from WebSocket to HTTP as transfer protocol. They also dropped captcha support in 0.18 which is the reason why lemmy.world and other bigger instances are waiting for 0.18.1 to re-introduce captcha support.

[–] sockenklaus 5 points 2 years ago (2 children)

This is more than weird. Jerboa dropped support for instances < 0.18 a few releases ago. I think 0.0.34-alpha was the last version that supported 0.17.4.

[–] sockenklaus 5 points 2 years ago (1 children)

What you're describing is an issue introduced with Jerboa 0.0.36-alpha and has been fixed in today released 0.0.37-alpha.

[–] sockenklaus 16 points 2 years ago (8 children)

This is nothing new: Jerboa doesn't support instances < 0.18.

[–] sockenklaus 2 points 2 years ago

Yes this is possible since 0.0.36-alpha but be aware that that version introduced some other issues that need to be fixed quickly.

[–] sockenklaus 8 points 2 years ago

I'm trying to make is that jerboa might not be as ready as we think for being a lemmy client.

I'm one of those random guys who try to improve things submitting a PR now and then fucking up things in the progress and trying to fix them again.

What I want to say is: I think you might be right saying Jerboa might not be as ready as many think. It started as a side project of one of the two guys who develop Lemmy full time. Dessalines even writes in Jerboa's README that people can submit issues but he will most likely not be able to work on them.

Now Lemmy exploded: A lot of people started contributing to Jerboa (including me) with vastly varying skill levels (me definitely on the lower end), there's no clear route the app will go in the future, no or little standards we can use as orientation.

And actually I'm not surprised at all that Jerboa might not be ready because this app went from "Just a little side project with 150 stars on GitHub on June 3" to "Probably most popular Lemmy client with 787 stars on June 27". This has been less than four weeks. I don't think any project is able to adapt to this influx of requests, changes, attention in this short time.

view more: ‹ prev next ›