Lemmy maintainer. Interested in politics, video games, and many other things.
When fetching a community or post for the first time, votes or comments are not fetched. You can subscribe, and will later receive new content.
Your instance is currently not configured correctly for federation. The following request should return json, but gives error 404: curl -H 'Accept: application/activity+json' https://lemido.freakspot.net/u/lemmy
(compare with curl -H 'Accept: application/activity+json' https://lemmy.ml/u/nutomic
). The default Lemmy installation has an nginx config which takes care of this.
This is a good find. It would make a lot of sense for Lemmy to format mentions in that way too. Could you open an issue in the Lemmy repo please?
By the way, the fetch problem you mention is already fixed in this pr (but not yet released).
I see, you make a good point. Your instance has been running for a year, but received very few users compared to lemmy.ml. My guess is that you receive new users mainly via join-lemmy.org/instances, is that correct? The problem is that most people only look at the top 2-4 instances, as you can see in the stats (removed everything thats not a Lemmy instance).
Problem is, that list is sorted by most popular and strongly favors established instances. I think it would help a lot of we put 2-4 “recommended instances” at the top of that page, particularly small or general-purpose instances like yours. It would also be pretty simple to have different recommendations for each language, which should help regional instances. There could be a sort of tag system as well, but thats a bit more effort to implement. What do you think?
We dont have any plans to change lemmy.ml administration.
I think that this is the better solution for the problem you mention.
You could point them to wolfballs.com, which seems closer aligned to them in terms of politics.
Did you install manually? Then you need to ensure that the ports for lemmy and lemmy-ui are set correctly in nginx config. You also need to apply changes with
nginx -s reload