blawsybogsy

joined 4 years ago
[–] [email protected] 1 points 11 months ago (1 children)

no one else is having issues with this?

[–] [email protected] 11 points 11 months 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?

[–] [email protected] 1 points 11 months 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.

[–] [email protected] 2 points 11 months ago* (last edited 11 months 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.

[–] [email protected] 18 points 11 months ago* (last edited 11 months ago) (2 children)

(or a b)

i never thought of lisp as concise before

[–] [email protected] 4 points 11 months ago

understatement of the year

[–] [email protected] 1 points 1 year ago

ah its back up now, thanks.

[–] [email protected] 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?

[–] [email protected] 1 points 1 year ago

yeah actually, rendering markdown is what requires the binary

[–] [email protected] 1 points 1 year ago (1 children)

glad you got going!

thanks for opening issues in the repo.

bindings are just work to do. development moving v fast, mainly I'm just still trying to add basic features. eg posting is only 4 days old.

I'm not sure about the markdown issue, I just require markdown-mode. mayb I use a fn in the mode that requires the binary.

Lemmy uses markdown, so to render post content I take the markdown data, render it using markdown-mode, then render the HTML output.

not sure how else to do that, nor how to not rely on markdown mode.

I shd look into it more, but mainly I had to just find my own way, as Lemmy is hardly documented at all.

feel free to make more requests, its easier than fumbling along alone.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (4 children)

that's interesting and also pretty frustrating. i didn't think i'd encounter such issues using plstore. are you able to provide a backtrace for the error? it'll show what is calling the encryption functions, and there could be an error before the one displayed. also try manually opening the .plstore file in your .emacs.d directory and encrypt and decrypt it while open. maybe you do just have some plstore problems. / btw, lemmy and lem.el require markdown, so best to install it. the latter requires markdown-mode too.

40
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

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/[email protected]. i have also seen links that just have "/c/[email protected]"... 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 ›