• 13 Posts
  • 137 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • Yeah, I am comparing linear distance to surface area, but if we call that 66 mile distance a diameter, were talking about roughly 3500 sq miles…which is a rounding error compared to the vastness of the south china sea.

    The south china sea is longer than it is wide, but even at its narrowest width between Phillipines and Vietnam, it’s over 550 miles across. That’s just incomparable to the distance between Florida and Cuba. Anything between Florida and Cuba is figuratively parked right in USA’s backyard.

    I legit tried to find the exact location of this latest aerial encounter between China fighter pilot and allied forces aircraft (because you’re right, that’s relevant) but couldn’t find it…the info must either be classified or intentionally censored.









  • True. And yet Cloudflare has to maintain its own army of lawyers to defend the constant barrage of lawsuits against Cloudflare claiming that they are facilitating copyright infringement. The average salary for 'Associate Legal Counsel" at companies like Cloudflare is about US $303,400. (source is Cloudflare themselves: https://www.salary.com/research/salary/employer/cloudflare-inc/associate-legal-counsel-salary )…and that’s just one of many. They are literally paying MILLIONS of US Dollars a year to defend against that. You think the admins for Lemmy.World have that kind of pocket change?

    Also, “caches” are temporary in nature and are different from permanent local copies (which is the model employed by lemmy). There is a technical difference, and even with that technical difference, Cloudflare still gets sued all the time for it.


  • You seem to have a fundamental misunderstanding of how federation works and either don’t know or don’t realize that content is replicated across instances that are federated with each other by virtue of users subscribing to it.

    If you are a lemmy.world user subscribed to a piracy community on another instance, then that content is replicated and hosted locally on lemmy.world also. You’ve never noticed how you can access content that originated on a foreign federated instance and still be able to access that content when the federated instance is down? That content physically resided on the lemmy.world instance until it was blocked.





  • You are obviously speaking from the privilege of someone not only familiar with how lemmy works, and who understands the difference and pros/cons of joining a large vs small instance and can probably even name a bunch, but also someone who knows of obscure tools and github repos that host those tools. What prevents users from switching using that obscure tool you referenced is that most users never heard of it and didn’t know it even existed. You are using the argument that new and casual users should have god-level knowledge and understanding…which is exactly the point I’m trying to argue against. Casual and new users don’t know what they don’t know. They don’t know what other communities are out there and they don’t know that when they view “all” that they aren’t seeing them. Think about this from the perspective of someone who doesn’t know what you know.

    Regarding your argument about NSFW and foreign language search results…that already happens now when users of your instance have subscribed to those things. You can’t argue that it would become a problem when it’s already happening right now. If it really was the problem that you think it is, then the solution would be to mimic what every other search tool figured out three decades ago and put an option to exclude nsfw results when viewing/searching “all” communities. It’s already possible for communities to flag themselves as NSFW, and it’s already possible for communities to designate their community language setting, it would make sense that those options be presented to users for filtering. These filtering options are things we need now regardless of whether search results come from actual-all or subset-all. I’m just suggesting that “all” mean “actual all”.

    But, just for fun, let’s steelman your claim that it would be technologically infeasible for “all” to be “all fediverse” as opposed to a subset of just what this server’s users subscribe to (it’s absolutely not technologically infeasible, but lets pretend it is) - even it that scenario, they should at least change up the UI for the communities page to make it clear that when the user selects “all” that they aren’t really getting all - it should be made clear what the user is actually getting, which is “local, plus foreign content that is subscribed to locally”. It simply is not truly “all”, so presenting it as “all” is only leading to more confusion about what the users are seeing.


  • TottalIy agree. i was not impressed with season 1 of Picard. I forced myself to watch season 2 and I almost just quit watching mid season - it just felt like they lost the magic. I wasn’t even going to watch season 3, but then I heard about all the cameos and thought it would be nice to see the old gang back together and it turned out to be the best season of the bunch. Still, Strange New Worlds is lightyears better, imo.



  • It’s a massive usability issue and a massive content discovery issue, imo.

    For lemmy users who got lucky and had their first lemmy experience on a top 5 instance where a lot of popular off-instance communities are already subscribed to, then users would see a huge list of both local and foreign communities. For users who got unlucky and had their first lemmy experience on a small instance, their view of “all” looks like a ghost town.

    Part of the problem is semantical. If they are going to call it “all” then it should really be all (all lemmy communities available on all federated instances). If it isn’t going to actually show everything, then they should call it something else that indicates it’s only local communities plus whatever local users are subscribed to.