Brandolini’s law, aka the “bullshit asymmetry principle” : the amount of energy needed to refute bullshit is an order of magnitude bigger than that needed to produce it.

Unfortunately, with the advent of large language models like ChatGPT, the quantity of bullshit being produced is accelerating and is already outpacing the ability to refute it.

Have you contacted the operator of the bot?

The L4sBot user bio lists how to get in contact with the handler @[email protected] .

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.

Then they can ask.

When a new/casual user is looking at https://[instance]/communities, with the “ALL” button selected, why would it ever occur to them that they would need to ask others if that really is all the communities communities?

There really should be a link to this on every instance/communities page with a note that if users really want to see “all” communities, they must use a 3rd party search tool to do it.

This is a solution for 1 single person. It doesn’t solve the greater problem that the experience is VERY inconsistent for new users depending on whether they got lucky and first joined a large instance or if they got unlucky and joined a small instance. It also doesn’t retroactively repair the horrible first experience that new users have with lemmy.

What you offered really isn’t an solution as much as it is mansplaining…and that’s not really helpful at all when what we’re talking about here are the perceptions of new users.

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.

The word “all” fundamentally means everything? By calling it “all” they are really doing a disservice to everyone who, gasp, assumes “all” means “all” when it really means “local communities and local user foreign subscriptions”. I don’t know what they should call it, but redefining the words “all” to be “not all” is super confusing, especially for users new to lemmy.

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.

I would NEVER recommend a modern HP printer, but…I have a HP Laserjet 4000 (Circa 1997) that I ‘acquired’ from the company I worked for that went bankrupt.

This thing refuses to die. current impression count is over 500,000 prints. All its patents expired over a decade ago, and it’s still easy to find parts and toner (originals, and now even 3rd party knockoffs). It’s old enough now that modern generic drivers have built in support for it. The only parts I’ve ever had to replace are the rubber sheet feeder rollers which dry out and stop working correctly after 12-15 years.

So, I guess the point here is that some really solid printers were made a couple decades ago, back when manufacturers still took pride in their products, and they are old enough that the hardware is no longer protected by patents (so practically open) and robust driver support without all the bullshit. Picking up something from this era and cleaning it up would come close to satisfying a lot of your requirements.

Removed by mod

Removed by mod

You are mistaken. City ordinances absolutely comes into play here. In the US, you are subject to federal law, any additional state laws, any additional county laws, and then any additional city municipal-codes/ordinances.

Here’s the Seattle city ordinance that applies:

Seattle Municipal Code, Chapter 12A.10.130 Indecent Exposure, Paragraph A.

A person is guilty of indecent exposure if he or she intentionally makes any open and obscene exposure of his or her person or the person of another knowing that such conduct is likely to cause reasonable affront or alarm.

source:

http://clerk.seattle.gov/search/ordinances/124301#:~:text=10 as follows%3A-,12A.,cause reasonable affront or alarm.

Well, I already named the jurisdiction: Seattle, Washington, USA.

The date/time shouldn’t matter since the ordinances haven’t changed, but it was Aug 12, 2012 just in case anyone reading this just happened to be in Seattle at the time and saw us. It was spectated by quite a number of people due to the size of the production - we had lights, a make-up/hair stylist, my assistant, the model, plus security.

It depends entirely on the jurisdiction. Take the city of Seattle, for example (I know this because I planned an executed a nude photo shoot in public view inside the city limits and sought legal council ahead of time to ensure I wan’t risking being charged with any crimes). The general rule for Seattle hinges on whether the activity is intended to tittilate or sexually arouse observers - and if that is obviously not the intent, then even full nudity is not illegal. Many other large cities have very similar ordinances.

The smaller the town, and the more conservative the region, the stricter and less flexible the ordinances. There are beaches in South Carolina, for example, where they even regulate the minimum amount of coverage for bikinis and beachware.

Removed by mod

It comes across as if it was a business decision without regard for their customers…without the basic understanding that their customers ARE their business.

Some were produced that were claimed to be dimmable - and I wasted my money on a few and was still unhappy with them. The other problem I forgot to mention earlier was the startup time: the earlier bulbs (and the cheaper ones) wouldn’t just ‘turn on’ when the power was turned on…they took some time to start making light, and the colder it was the longer it took - this is an aspect where LEDs are amazing - maximum brightness within milliseconds of getting energized.

One problem is that CFL bulbs is that they contain small amounts of mercury (about 4mg per bulb). Because of that, disposing of them responsibly requires going through big hassles rather than just throwing them in the trash. Also, because of that mercury, accidentally breaking one means contamination of the environment around the break.

Flickering - always was a big problem for these things.

Longevity: They were very sensitive to heat, which meant that they loved to burn themselves up in a lot of applications.

Dimming: CFLs were NEVER good at being dimmable.

CFL was just a very poor technology detour on the way to the vastly superior LED lights.