• 4 Posts
  • 132 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.


  • It depends on the jurisdiction. In the United States, we have the DMCA which has been weaponized by content creators and publishers, but we also have a “safe harbors” provision to the DMCA that is supposed to protect online service providers from being liable for copyright infringement based on the actions of their users - as long as they meet certain provisions and restrictions and perform certain duties and dilligence. And yet even with that in place, it does not stop content providers from suing service providers and forcing those service providers to incur the pain and expense of mounting a legal defense.

    I am pretty sure that Lemmy.world admin team are European and that the instance is hosted somewhere in Europe, so they would have their own jurisdictional laws to follow.

    TL/DR: even if a service provider is technically protected from the actions of their users it is still subject to provisions and conditions, and that still doesn’t stop them from being sued and having to mount a defense. Some people just don’t feel the hassle of all that justifies the whatever benefits they’d gain from fighting that fight.

    Certainly you’ve heard of ‘The Pirate Bay’, who’s ‘users’ famously used their platform to share copyrighted materials…the founders of The Pirate Bay were arrested, tried, and convicted, and were forced to serve jail time. Turns out the “but it was our user’s doing it” defense wasn’t as reliable as everyone here seems to be suggesting.


  • 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.




  • This doesn’t invalidate my earlier statement that citizens are still subject to city ordinances.

    There are around 20,000 cities and municipalities in the United States, most of them have public-nudity/indecent-exposure laws.

    You successfully made the point that the legality of city ordinances can be challenged in higher courts (and even sometimes overturned) but the reality is that most people have neither the funding nor the time nor the expertise to take that up…which means ultimately you’re still subject to a city/municipality ordinances as well as state and federal.

    In 2017, Tagami v City of Chicago, the US Court of appeals for 7th Circuit ruled 2-1 that the city’s public nudity ordinance did not violate the complainant’s rights and upheld the lower court decisions (which meant that City of Chicago’s ordinance remained intact and validated as enforceable by the city).

    At the end of the day, yes you do have to be cognizant of the ordinances/codes of the city in question and cannot rely on State/Federal law alone.





  • 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.