blawsybogsy

joined 5 years ago
[–] blawsybogsy@lemmy.ml 4 points 1 year ago

understatement of the year

[–] blawsybogsy@lemmy.ml 1 points 1 year ago

ah its back up now, thanks.

[–] blawsybogsy@lemmy.ml 1 points 1 year ago (1 children)

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

[–] blawsybogsy@lemmy.ml 1 points 2 years ago

cool bananas.

[–] blawsybogsy@lemmy.ml 3 points 2 years ago* (last edited 2 years ago)

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.

[–] blawsybogsy@lemmy.ml 2 points 2 years ago* (last edited 2 years ago)

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.

[–] blawsybogsy@lemmy.ml 1 points 2 years ago (1 children)

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.

 

Is there anywhere that lemmy's various types of internal links are documented? like !community links @user links, links of the form https://lemmy.com/c/community@otherinstance.net. i have also seen links that just have "/c/community@otherinstance.net"... at the moment i'm only developing rendering code for them as i happen upon them, which is ad-hoc

 

Or is it documented? with mastodon, i set up clients to always load URLs in my app if they resembled masto-compatible URLS. I'm unsure how to go about this with lemmy. the lemmy-js-client "documentation" makes no mention of webfinger at all, though the lemmy repos have PRs fixing it.

[–] blawsybogsy@lemmy.ml 21 points 2 years ago (1 children)

ah, Lenny. I really love Lenny.

 

The Limit property is just a number, but it is different for different API endpoints. I'd like to have a list of the different values so i can easily stay within the max for each endpoint. Are the values documented somewhere? From the official js-client docs site, not even a given endpoint documents its maximum.

[–] blawsybogsy@lemmy.ml 1 points 2 years ago

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.

 

i have requests to fetch comment and post data, but i'm struggling to work out how to build a tree from the responses? do i fetch comments with arg parent_id to get a comment's children, and do so recursively for those comments returned that themselves have comments?

[–] blawsybogsy@lemmy.ml 0 points 2 years ago* (last edited 2 years ago) (1 children)

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

 

testing, pls ignore :)

[–] blawsybogsy@lemmy.ml 1 points 2 years ago (1 children)

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.

[–] blawsybogsy@lemmy.ml 1 points 2 years ago* (last edited 2 years ago) (3 children)

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.

view more: ‹ prev next ›