cross-posted from: https://feddit.de/post/541247
> The community browser offers the possibility to search centrally for Lemmy communities.
> ::: spoiler spoiler
> There are still a few features planned...
A curiosity I didn't know about Lemmy.
> However, I just noticed a place where there is some lack of informed consent here on Lemmy: in the Lemmy UI, it appears that upvotes and downvotes are anonymous. I checked a long time ago, and realized that they weren’t really; the identity of the up or down voter is federated, but it is simply not shown by the UI.
> I would assume that many (probably most) lemmy users do not realize this: admins of your own instance and all federated instances have the ability to see who upvoted and downvoted what.
> It just now came to my attention that Friendica actually is showing this information publicly, in the form of “$username does not like this” for a downvote!
> — By [@firstname.lastname@example.org](https://lemmy.ml/u/cypherpunks) on [Great fedi thread on consent](https://lemmy.ml/post/732593/comment/378308)
I was looking for how to install Lemmy and found these videos, hope these can help if you need to install you instance.
cross-posted from: https://lemmy.ml/post/712978
> Does Lemmy currently use hashtags in any way? I'm assuming it doesn't since they don't show up in the UI anywhere. But while thinking about [non-lemmy software posting to lemmy communities](https://lemmy.ml/post/705776), I was wondering how lemmy would use hashtags.
> My suggestion would be for lemmy to handle hashtags in a similar way to current microblogging software, by putting them in the `tag` field and allow lemmy users to add #hashtags to their posts. [Lobsters](https://lobste.rs) displays tags beside post titles (though these tags are admin controlled I think). It seems like there is a maximum of 2 tags, which I think would be a reasonable limit for lemmy to display too. The UI could display the tags as badges, with some affordance to view any additional tags, and clicking a tag would show other posts with that tag.
> As for why, I think tags on lemmy would serve two main purposes:
> 1. They would enable better discoverability on non-lemmy software where hashtags are the main topical grouping mechanism right now.
> 1. While lemmy uses communities for topical grouping, some posts might fit into multiple categories, even unrelated categories. Crossposting sort of solves this, but crossposting can be considered spammy if it's done too much. And, on lemmy, crossposting creates another post which fractures the conversation. This may be desirable sometimes, but a poster may also prefer to keep all the conversation in one spot.
I saw from a recent post that [downvotes does not propagate](https://beehaw.org/post/244315). That seems counter-intuative to me, how does it actually work?
- Does my downvote affect the visibility on such a posts in my feed when I vote on it on my local instance?
- Does my downvotes on such an post impact the visibility of the post among my fellow lemmy-browsers on a third party instance?
- Will turning off downvotes on an instance give its posts and posters an *artificial boost* when federating compared to instances where posts can get downvotes?
I'm suspecting this can be used to create false consensus and artificially high visibility around posts.
A Lemmy post will often refer to a specific web link. Is there an API for the linked site to be notified about Lemmy posts referring to it (e.g. to be able to link back, or even to integrate Lemmy comments)?
This is a lemmy feature request. I'm happy to file an issue on github is people thinks this is worthwhile. I just want to gauge interest.
When creating a new post, could the `URL` field be expanded to also accept a lemmy community handle, i.e, email@example.com_? That way a user could create a post to announce a community that would link to the community, within the instance the user is on.
See [this post](https://lemmy.ml/post/690782) for an example. My lemmy account is on lemmy.ml. So when I follow the link in this post, I'm taken to lemmy.ca and can't directly follow the community. It'd be nicer if each instance detected that the link was a lemmy group and linked to the instance local community, in this case: https://firstname.lastname@example.org. I'm assuming this would just be a frontend thing and the ActivityPub json would still use the canonical url.
I'm running on a personal lemmy instance, and I've been able to simply re-subscribe to the communities that I was subscribed to on my previous lemmy.ml account.
But what if I didn't have that? How would I discover those communities?
On the micro blogging fediverse, I can use relays, follow other peoples boosts, or join gup.pe groups etc for content discovery and to give me federated content in general on which to do content discovery.
What does that look like in the lemmyverse niche of the fediverse? How does a small single person instance find new content? How do they get richer content search options etc? Right now, I'm just using search on lemmy.ml for that, but that's a work around, not a solution
It seems that it's just recently created communities, at least on the instance I'm on. Is that how it works everywhere..? I feel that "Trending" ≠ recently created. Either it should be renamed, or what I'd prefer is that a way to differentiate "trending" communities.
We are looking for someone who would be willing to provide a build server for Lemmy's continuous integration. This is used to ensure that new changes and pull requests pass all the checks, and that the code is written well. At the moment we are using a small VPS for this purpose (2 vCPU, 2 GB RAM). This works but is quite slow, and can slow down the development process with unnecessary waiting times.
For this reason we are looking for a community member with a spare server or computer, who would be willing to provide it as a build server. There are no specific hardware requirements, but the faster the better. The build server has to run 24/7 and run the [Drone Docker Runner](https://docs.drone.io/runner/docker/overview/). The setup is very easy, especially if your machine is already running docker. If you have such a server and are willing to provide it, please comment below with the specs.
Additionally we are also looking for an ARM builder, so that we can provide official releases for this platform as well. Note that some Raspberry Pi models seem unable to build Lemmy (our 4GB memory builder failed), so please try if the compilation works on your device. If you can provide an ARM builder, also comment below with the specs.
Hi ! This is a suggestion/thought on the option to show ALL communities posts on Lemmy's homepage.
The homepage UI is nice because it provides a single place to view posts from either Local to All instance, it makes the fediverse feel whole.
One downside is that, since some instances are much larger than others, the All section is often dominated by posts from a single instance.
I don't mind seeing lemmygrad.ml posts, but that seems a bit much. It's good to see a diversity of information/opinions (as opposed to Twitter's bubble).
A new sort option would be nice to give better visibility to posts on smaller instances. Maybe tweaking the weight to better account for community size . Let's say the default logic is a function of upvote counts, you'd scale the upvote based on instance size (eg weight=upvotes/sqrt(instance active users)).
Edit Lemmy's documentation call this the "score" https://join-lemmy.org/docs/en/about/guide.html#sorting
Let's say you're on reddit and someone posts an imgur gallery, from an app like Boost you can view and browse that album without leaving boost.
But if I post a link to a mastodon toot that has 4 images, and I click the post in jerboa it will instead open a new window into the actual mastodon page.
I've argued for the value of "post once distribute everywhere" but if that paradigm isn't right for the fediverse at the very least the ux for linking mastodon image posts could be improved. Instead of posting once distributing everywhere it would be at least possible to post once and then link everywhere. (this doesn't fix issues like trying to get stuff like pixelfed working but it's worth a thought)
The land of Lemmy, a vast expanse,
A place for all to share their thoughts and glance
At the latest memes and news from around,
With communities for every topic that can be found.
There's !funny for the jokes that make us laugh,
!asklemmy for the questions that we want to ask,
And !science for the latest discoveries to be found,
Lemmy has a place for everyone on the ground.
Whether you're looking for advice or want to share your own,
Lemmy's the place to go where you'll never be alone.
So come and join the conversation,
On the land of Lemmy, where ideas take flight without hesitation.
I've asked about this before, see my post history. But the fact that pixelfed, mastodon, and lemmy can all be subscribed to from one instance or another, isn't a replacement for a "post once distribute everywhere" solution.
Yes its true that a pixelfed and a mastodon can follow one another and because you can post images to mastodon and pixelfed images can have text they can often be basically identical in terms of potential feed content. But lemmy is something that I would post to communities.
It would be helpful if I could use an app to simultaneously post to my mastodon, my pixelfed, and to a range of lemmy communities and or cross posting between communities on lemmy.
I suggested in my previous post the ability to post to a mastodon with certain hashtags triggering getting sent to different lemmy communities. I think that still works as an idea but I think perhaps this new framing helps explain why it's not as simple as "have them follow your pixelfed from their mastodon". If posting once to distribute to both mastodon and lemmy community makes sense then I don't see why it shouldn't be reasonable that there are some cases where the same is true of pixelfed and mastodon (I said in response to one comment that you might have different audiences)
I think the biggest issue with lemmy so far is lack of content and engagement. Same thing is true with mastodon. The anti viral design ethos of mastodon encourages people to avoid tools like "post once distribute everywhere" I think perhaps people view it as potential for spam. But we really need some actual tools to make posting content easier.