Please cite your evidence for review.

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.

There’s only 66 nautical miles of international water between FL and Cuba.

The South China Sea is 1.3 million square nautical miles.

You are a few orders of magnitude off for a rational comparison.

I don’t think they suck at forecasting…I think they are probably exceptional at forecasting but willfully lie about project costs when submitting bids for projects in order to come under the competition and win the contract. There doesn’t seem to be any penalties for this, so why would they stop?

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 @L3s@lemmy.world .

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.

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

Removed by mod

Is the new community for sharing knowledge only, or is it also a place to ask questions (ie: “What is the etymology of [xyz]?”)?

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.