i have a rooted android (running calyx) and it just works and its great. i never fuck around with it at all, whether due to necessity or ricing desires.

it’d be helpful to post to sth like masto yeah, as its much more public facing than matrix.

you could take ask on the repo or ask the dev, they’re obvs active on the fediverse. (poss relevant: https://github.com/superseriousbusiness/gotosocial/issues/1468.)

is it not possible to just search in the code of spacemacs if you know it can do it? seems like your best bet. if you can’t find it searching, ask on the repo? otherwise, as others have said, i wouldn’t think it’s a simple thing to achieve. best to see if you can reuse the work others have already done.

blocking instances for users was added in 0.19. it works like community block: you don’t see any posts from an instance, but you can see the activity of users from that instance on any other instances where they do stuff.

https://github.com/LemmyNet/lemmy/pull/3869

[this is not an endorsement of federating with any meta product. i believe in deplatforming hostile actors, which they’ve well and truly proven themselves to be.]

i also fixed authentication for the 0.19 release, but when your instance actually upgrades (lemmy.ml already has, for testing), it will require you to delete the lem.plstore file in .emacs.d/ and log in again with your password.

& by all means holler if you run into authentication issues during the transition.

EDIT: all good, I worked it out, I found some other api docs.

Is the ModeratorView listing type in this release? If so what feed view is it available in? I can’t see it in the lemmy.ml webUI at the moment, nor in the API docs, but the code is merged.

understatement of the year

ah its back up now, thanks.

i was going to test these new changes out for my client, but it seems that https://voyager.lemmy.ml is down?

cool bananas.

lem.el also implements a client, similar in design to mastodon.el. i did the api layer so that others could implement other kinds of interfaces such as a gnus backend if they desired.

does that really matter? its clear that lem.el is an Emacs library, and is thus named as such (.el), and is thus not a standalone piece of software. I really don’t think its a problem. there are no Emacs libraries with the same name.

from a quick check, i have C-p and C-S-B working, but C-n and C-s and (many i think) others not working. ff 114 on linux.

ah, Lenny. I really love Lenny.

made some progress. mainly spent time working on getting the sorting types and listing types going, so you can cycle between them on the go. v basic display of post details in byline, etc., but that can easily be spruced up by pulling code from mastodon.el. + markdown rendered posts/comments, uwu!

https://codeberg.org/martianh/lem. the readme has a rough todo list.

logging in and loading lem as package is still pretty rough, or kinda broken. but i’ll get it sorted soon.

still gotta build a comments tree also, that’s a biggie.

can you see comments that way? you just subscribe to communities i imagine?

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.

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.

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?