The lack of keyboard interface on Lemmy is killing me, but really what I want is a good client in Emacs. However, it’s beyond my Elisp to design and start such a project, but I could probably help. Anyone on it?
The lack of keyboard interface on Lemmy is killing me, but really what I want is a good client in Emacs. However, it’s beyond my Elisp to design and start such a project, but I could probably help. Anyone on it?
i’m the mastodon.el maintainer. i wonder if a decent idea for this would be to have an API library that could be used with gnus, elfeed, md4rd, or anything else? it seems like everyone will want to browse it in their preferred environment.
some lemmy things are visible in mastodon.el, but it’s currently not great. not only because of how masto rendering is based on a microblog style view, but also because a lot of content doesn’t federate that well yet.
i took a look at the lemmy API docs, but they don’t seem to provide an overview of the endpoints?
I think this would be the best way to go.
Myself, I’d love to be able to interact with Lemmy through Gnus, but it would be great to have a general emacs API for flexibility so you can choose the front-end.
It looks as though the api for a client is defined in api_common.
thanks for the link. so https://github.com/LemmyNet/lemmy/blob/main/src/api_routes_http.rs shows the paths and params, i tried them in a rest client and it’s no too hard to follow.
the mastodon.el http layer isn’t great, but it could be v quickly adapted for this case.
Thanks, yes that’s a more useful source than my one.
https://codeberg.org/martianh/lem has some basics, functions returning plain JSON. i didn’t do any auth, but if its oauth and so similar to mastodon.el, we cd also just move its auth code into the fedi.el library. and fedi-http.el is already set up to handle auth tokens.
discovering lemmy’s query parameters is quite a pain for me, as i don’t know rust.
That looks a promising start. I’ll have a look into it when I have some time. I hope some others do too!
I don’t know Rust either, but it does appear to be relatively easy to understand; could be worse anyhow.
It would be nice to have a fully documented API to work from: probably not a priority for the lemmy devs right now, I’d imagine.