I'll try over the weekend.
Thanks but this guide is a bit too oversimplified, which is guaranteed to leave the user with question marks after a few minutes of using it.
And I also dislike the hardcoding of recommended instances (lemmy.world and lemmy.ml).
The most similar and FOSS one is Revolt (revolt.chat).
The next Lemmy release so I can finally continue with my Lemmy bot.
#FFFFFF at 0, 6
because nobody needed such a thing until now?
I mean, as long as the bigger instances (that are also federated with lemm.ee, e.g. lemmy.world) stay, then your content is already "archived". Unless you choose to delete your account explicitly (which probably some instances will ignore anyway), your content will stay.
- you create a function with a page parameter and call the /user endpoint with a bearer auth header. page argument should be 1 at first call.
- using some library (or I think requests already has deserialization of JSON) you convert the JSON into some pythonic data type (e.g. dictionaries).
- exit the function when the length of posts and comments is 0.
- otherwise loop through the posts and comments arrays with a for loop
- on each iteration, serialize the dictionary to JSON and save it to some file
- increase the page counter by 1
- call the same function at the end of the function and pass in the page counter (which was increased by 1 previously). this is called recursion.
You don't need to "study" the API. The only thing you need is the /user API endpoint: https://mv-gh.github.io/lemmy_openapi_spec/#tag/User
I find a reputation system good, however it should use percentages instead of points to make it different than what the karma system in Reddit was. People are less likely to farm for upvotes when it can only show 100% max.
Afaik piefed does not really show the reputation percentage to anyone (I might be wrong), but just shows a "low reputation" when it is under a certain percentage.
Just make a simple script (with bash or something) and go through your post/comment history via the API. Save the JSON of the posts/comments somewhere.
seems right. I wonder why the devs didn't implement that. would have been a simple change
This can be done client side. This as a backend change would be useless and would waste ressources.