blawsybogsy

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

ah i solved it, it's that the max_depth arg has no sane default, so a client needs to set it manually. currently the server has a hard 300 max value i think.

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

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.]

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

no one else is having issues with this?

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

i read the page title, then looked at first result and it was mastodon.social and second was mstdn.social.

mayb for your site to match its title you want to not make "federated" the default status sort option?

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

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.

 

currently my client displays child comments/replies to a given comment based on a get-comments request and the sort arg. if a child comment is returned by such a request, it will be included as part of the tree, but otherwise not. it means the child is subject to sorting itself.

but what is needed is that if a parent comment is displayed/returned by request/sort arg, all its children should be also. that seems to me to be how the webUI works also.

any tips on how to ensure that?

 

did a maniac hack on the old lem.el recently, mainly for the 0.19 release. overhauled the logic of all the sorting/listing commands. they should be more rigorous and flexible to update now. various other fixes too. pushed to main, so will hit MELPA soon.

also added unified inbox for replies, mentions, and private messages, and various other minor display improvements.

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

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.

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

(or a b)

i never thought of lisp as concise before

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

understatement of the year

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

ah its back up now, thanks.

[–] blawsybogsy@lemmy.ml 1 points 2 years 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.

38
submitted 2 years ago* (last edited 2 years ago) by blawsybogsy@lemmy.ml to c/emacs@lemmy.ml
 

A client library and UI for Lemmy, has most of the basics in working order now. interested to hear your feedback if you give it a go. other complex UI features like rich post composing and image handling will be ported from mastodon.el.

it is designed to have a clean API layer, so the functions in lem-api.el could be used to create other interfaces.

 

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.

 

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.

 

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?

view more: ‹ prev next ›