blawsybogsy

interesting. mastodon.el also uses plstore, so if it works (saving your credentials) your machine's encryption should be working. but the auth process for the two services is totally different, so I had to write the lem.el auth code from scratch. I can take a look at it v soon, I'm keen to have any auth issues sorted out asap.

it'd help if you cd describe when the error message appears, or what exactly you do that causes it.

actually a backtrace would be most useful to track down the error.

you cd also try opening the plstore file in your .Emacs.d folder and encrypting / decrypting it.

thanks!

feel free to message me or to open an issue on the repo if you run into issues getting lem.el going. others have already helped me iron out a few getting-started issues.

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.

thanks a lot for this

yeah, the relative ones are always on another instance it seems. if you strip the '/c/' you can hit the '/community' endpoint with the '[email protected]' part as the name parameter and it returns the community_view for it. works fine.

thanks for clarifying, so i guess my other link type is an error on my end somewhere...

i'm just unsure how to actually correctly fetch the next set items in order to update display, whether for scrolling or paginating. for my client i just want to append at the bottom of the screen.

hm, yes but they're rate limits, not the maximum values that can be passed to the limit param. they must be different because my rate limits are post: 6, comment: 6, and that's definitely not the max value for limit for fetching those items.

but i figure the whole community is already about best practices the API / endpoints