This is due to poor error handling in the API client code, triggered by the server returning some sort of error. There’s an open issue but it hasn’t been taken up yet.

There’s an open PR you can follow here: https://github.com/dessalines/jerboa/pull/514

The last few days have been incredible with the amount of contributions pouring in. We had 13 first-time contributors in just 3 days, and the release before that was 14 contributors.

This is improved in 0.0.33. Now it’s just tap anywhere on the comment that isn’t also a button. There’s a setting to configure if you want that comment to collapse or just the replies.

As a workaround for now, you could consider using a browser like Firefox focus. It’s basically an always-incognito browser.

I’m currently working on making it so that fediverse links opened in Jerboa will open in Jerboa. After that I think we could see about how to support that “add more links” setting in the UI.

We just released a big new update to Jerboa that adds a lot of much needed features and polish. We had 14 new contributors too!

That’s definitely a bug, I opened an issue here: https://github.com/dessalines/jerboa/issues/513

Thanks to everyone who has opened issues or submitted PRs! 14 new contributors this round!

Great suggestion!

On second thought, we want to implement a full search, and I think that this will be confused if there are two different menus both using the same icon.

There isn’t exactly a roadmap at this point, its sorta a free-for-all with lots of people implementing the features they want. Making issues on github definitely helps visibility and will help it be prioritized once the app is in a more complete state.

I 100% agree with you, we’ve implemented this as an option and it’ll be in the next release.

Can you make an issue on github? This is something we should definitely implement.

There’s an open PR that’ll fix the font size issue. I’m using it now and it’s great. I’m also personally working on trying to add my personal must-have UI options from Boost.

I imagine it’ll be possible in the near future to improve the accuracy of technical AI content somewhat easily. It’d go something along these lines: have an LLM generate a candidate response, then have a second LLM capable of validating that response. The validator would have access to real references it can use to ensure some form of correctness, ie a python response could be plugged into a python interpreter to make sure it, to some extent, does what it is proported to do. The validator then decides the output is most likely correct, or generates some sort of response to ask the first LLM to revise until it passes validation. This wouldn’t catch 100% of errors, but a process like this could significantly reduce the frequency of hallucinations, for example.

Consider charging at home, if you can. If your typical driving patterns consist of driving <100 miles from your home and it’s possible to plug in at home (a standard 120V outlet is sufficient typically), then you don’t need public charging stations. Just plug your car in at night and it’ll be full every morning.