MV (Jerboa dev)

@MV (Jerboa dev)@programming.dev
0 Post – 72 Comments
Joined 1 years ago

I do not see how critisms for the JS API docs are relevant for my openapi documentation.

This documentation aims to solve all those problems in a language agnostic way. It descibes the endpoints, the request object, the status, the response object, the authentication needed in visual/text. It allows you test it right from the browser, allows you to copy a working curl command, search for endpoints based on keywords, allows you to import the entire spec into postman/alts.

I ve never had any problems with CF instances but I mostly test with voyager.lemmy.ml

(Author btw)

Can you expand on this? This was written for Kotlin usage. It automates generating API based on this spec.

I have no idea what you mean with 'using other approaches to calling the endpoints'

Lemmy has only one API. It's same API used for lemmy-ui.

This is just a "better" documentation for it.

The API works for for cloudfare instances too.

There is also a swagger ui variant

https://mv-gh.github.io/lemmy_openapi_spec/swagger_ui.html

2 more...

Ah yes, all though I ve never really experienced HTTP days in their full glory

I'll look into using it. If it has a github action or easy way to publish it from cli

Looks like the best openapi front. I looked into using it, but it didn't seem free. Too bad this one is outdated. Lemmys API has changed quiet a bit since then.

1 more...

The full sentence is This account (%s) is being verified

It's verifying that everything is correct, acc not banned, JWT works, instance alive, ...

It only shows that, if you are attempting something that causes it to be verified while already verifiying that account.

Nbd, should ve resolved itself in a few seconds

That list gets generated based on the lemmy instances tracked by fediverse.observer site that have a monthly active user amount greater than 50.

Jerboa is just showing you the error it got from your instance. I can look into the source code for Lemmy but that won't be for a while.

It is caused by a bug introduced in lemmy 18.3

https://github.com/dessalines/jerboa/issues/1109

I have a fix for it already

The swipe gesture feature uses a new experimental component. As far as I am aware we can't configure the sensitivity. We have decided to have it off by default. We also fixed the swipe direction not being aligned with the description.

We cannot solve that issue on our end. It is a problem with the toolkit that we use, see https://issuetracker.google.com/issues/294102838

You can disable text corrections if you want a work around

https://github.com/dessalines/jerboa/issues/194#issuecomment-1635789189

"community ban" is not something that is coded into Jerboa as far as I know.

1 more...

What "embed links"'? Those in markdown? or all links opening externally? Either of way I can't reproduce this. We did make some minor changes regarding opening links externally so that Firefox private tabs are supported. What browser do you use, what settings do you have for custom and private tabs. What version of jerboa. Android/phone info. Basically more info = better

6 more...

Bottom bar collapse exists the other way, some users prefer to not see the bar by default and then you can hold to show the bar.

I definitely wanted to make, tap/hold actions fully configureable. It's somewhere on the backlog, I'll create an issue if it doesn't have it already.

That's a lemmy bug, not Jerboa. I reported the bug already. We don't get a choice as frontend on what gets returned once that option is set.

https://github.com/LemmyNet/lemmy/issues/3691

That's already been fixed, and will be part of 0.0.51

That feature doesn't exist yet.

But there are some considerations to be made in implementing this.

Like the images that shouldn't load, do we hide them, do show a black shade or placeholder. If so which placeholder because i doubt that you want to see Jerboa icons everywhere instead. If we hide them there there is no difference between postviewmode largecard shortcard so do we keep showing both? Someplaces it's probably better to hide them like the avatar.

This will most likely be part of a much bigger "data saving" feature where you can enable loading images(previews/comments/avatars/banners) on WiFi only/all/never.

And it be pretty cool if you could granular select which images you do and don't want to load. But there is no UI for that yet. So that will have to be designed too.

What version are you using? 0.0.44 significantly increased the limit.

3 more...

Not in a way that is easily shareable. Working on a log viewer next.

It's a bug introduced since lemmy 18.3. Update to 0.42 and it should be fixed

2 more...

It's more the other way around, some ppl prefered, having the bar collapsed by default. And then hold to reveal it

Since it is probably gonna be atleast one more day before a release you can get the fix here early https://github.com/dessalines/jerboa/files/12209937/app-release.zip

Can you tell me what broke?

1 more...

The release on Fdroid does not contain these experimental changes.

Only the above builds

Here you go, I added it

image

1 more...

Settings > Look and Feel > Scroll down

2 more...

There is no real order of which issues get done. Everyone is welcome to contribute any feature/fix they find important.

I just work on things I find have priority which is mostly bugs first. The next big feature is probably backwards compatible API which is a huge amount of work.

There is a issue for the creation of communities. Already but it doesn't specify exactly it. Like where do we add this in UI, do we make a fullblown screen or just a popup. Which logic for showing this creation menu. Some instances don't allow users to make them. etc

I genuinely don’t understand how there can be so many languages and all of them be painful to use

What about kotlin?

2 more...

Wow, never even realized that. Make an issue on github and I'll take a look.

Also does it work if you disable that setting?

There is a bug that in communityview of an 0.18 instance it will only show first page. It is fixed but not released yet.

2 more...

Can you also test if the problem is still fixed with this build and that the flick to exit works in the ImageViewer

https://github.com/dessalines/jerboa/files/12618555/fix_zooming_jerboa_debug.zip

We didn't actively impose this limit. I switched the image library that the ImageViewer uses. And that was its default zooming limit. I think its the same in other apps where they just keep it to the default settings.

Alright we will be dropping this feature until we make a proper swipe to exit

The update you are talking about, is it the latest 0.0.46?

In settings do you have custom tabs or private tabs on? (in Jerboa not chrome)

4 more...

Can you give the steps to reproduce this, as I can't reproduce this problem rn.

6 more...

I fixed that a while ago. And I have added support for dming users in Jerboa, should be there in the next release.

https://imgur.com/a/P7ZcVPO , can you give more info about your android version and device?

4 more...

Yeah that would be great but i am not sure if that release includes the logging of HTTPClient, could you try it from latest build?

Lemmy 18.3 added it html sanitation which doesn't seem to be properly configured

Yes but exactly which versions are we talking about. 0.0.43 to 0.0.44?