blawsybogsy

this update...

One of the comments reads : Actually, we will probably never figure out, was it man or woman. but I thought this comment of the professor was an interesting eye opener. mastodonapp.uk/

There’s now a swagger documentation for the Lemmy API....

I just implemented a user overview of mixed posts and comments, but I’m unsure how to do so while respecting sort (hot, new, old, etc.). Currently I merge the user’s comments and posts into a list, then sort them all by timestamp....

additions:...

Mito docs are pretty scarce, here’s a helpful tutorial for getting a nice cruddy CRUD going.

“We create a search form, display products with ready-to-use HTML templates, organize our Djula templates with inheritance. Common pitfalls. That’s the basics every web developer should know!”...

I think it’s pretty safe to say that the majority of us are here to avoid another corporate takeover of our preferred platforms. It would seem to me to be a tad irresponsible to allow Facebook into our space with open arms, allowing them to hoover up our data. I would love to keep using Lemmy.world, but will happily change...

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

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

Is there anywhere that lemmy’s various types of internal links are documented? like !community links @user links, links of the form 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...

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.

This seems like a good place so far tbh

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?

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?