Apparently [email protected] is its own server now ( lemmy.one )
I think there’s a bug somewhere :)...
This magazine is from a federated server and may be incomplete. View on remote instance
I think there’s a bug somewhere :)...
Crossposts are a great way to follow posts from one community to the next, and discover more user contributions. I would love to see that on Lemmy.
We are happy to see that many of you are exploring Lemmy after Reddit announced changes to its API policy. I maintain this project alongside @dessalines....
When reading posts sorted by date, I often have the timeline import a whole bunch of old posts from one community at the top. This is annoying since I basically have to reload the page, otherwise all relevant content is gone....
Would Lemmy be a good fit for adding individual “blogging” as a feature? What I mean is the ability for a user to create posts tied to their account instead of a specific community. The default Lemmy Frontend/webapp has all the basic features that would normally make up a blog: ability to make posts, markdown editor, hell...
Apologies for all the translators that weren’t able to sign up before (it was email issues), this should be fixed now.
Lemmy is structured in a way that backend (database, api, federation etc) and frontend (html, css, javascript) are completely separate. This makes it possible to create other frontends which can take the place of lemmy-ui. I have long been playing with the thought of having a Lemmy frontend that looks more like a traditional...
I think we need to add a couple more barriers to prevent spam. What about limiting posting to X amount of posts, or for new users or something?
https://lemmy.ml/pictrs/image/ktM7WtDoYD.png...
Disclaimer: I am a multiply marginalized person on the radical left....
Where did the API documentation in the documentation go? There used to be this great listing of all of the API calls but it seems to be gone now?