• 7 Posts
  • 763 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle


  • It would be nice if the clients could group cross-posts or posts with the same URL, so that you don’t see duplicate content in the feed. Like right now with the posts regarding changes with Discord, there are 3 posts in the top 20 of my Hot feed, two of which that are cross-posted and another with the same press release URL. Everytime I cross post, I feel bad for people who follow both communities since i know i’m cluttering up their feed, so I do so sparingly, but there are other users who seem to be cross post happy.






  • I would hope that in 25-50 years from now, gendered locker rooms and bathrooms will be a thing of the past, and slowly replaced with individual unisex stalls. Maybe for high volume places (like a stadium or airport) there will still be bathrooms with a wall of urinals, but those will probably not be labeled “men’s” and will just be urinals.


  • This may be unpopular to some, but I think there should be more interoperability between Lemmy and Mastadon. I know from Mastadon you can @mention Lemmy communities, but most users don’t know about that. Maybe depending on the privacy settings of a Mastadon post, if that could be “forwarded” to a Lemmy community as a post, and it would be useful for many who follow a community in Lemmy but not the author or hashtag in Mastadon. It’d also be nice to be able to follow people who use Mastadon and have that show up in your feed on Lemmy.


  • I hate LinkedIn, but having a way to keep in contact with former co-workers is good from a networking perspective for finding a new job. Someone I hadn’t talked to in 10 years reached out with a position they were hiring for, and that’s not something I would have been looking for or known about.

    The useful parts of LinkedIn are managing business acquaintances, and it’d be cool if there were a decentralized privacy preserving way to be able to maintain that contact list of people, without it being used to harvest data for some data broker somewhere.




  • With P2P file sharing, your client is sharing the files with random people on the internet and you’re identified by your IP address (or a VPN IP address / seedbox IP address / etc). MPAA hires companies to check for popular content and log the IP address, time, and content shared, and then sends that to the ISP. The risk and issue is sharing content with anyone randomly, since that is how your ISP is informed of the activity.

    With media servers, unless you’re somehow sharing publicly, it’s safe to assume your members aren’t going to report you to your ISP. I guess in theory the ISP could see high upload bandwidth and investigate, but more likely than not, if there are limits, automated systems will just throttle the bandwidth, and no deep packet inspection or other forensics is performed.