What if they don’t want that multi step process?
Hard thing, but what are a few steps to avoiding AI spam results?
There’s nothing inherent to this proposal that avoids spam or SEO. You describe it as a “moderation issue” and then mark it as out of scope.
If avoiding AI spam or SEO sites is a feature of this proposal, then it should be addressed directly.
no one can index exponential amounts of data, nevermind the predatory SEO and AI.
Google is. The NSA almost undoubtedly is. A bunch of other governments are. AI companies probably are. Meta probably is.
When a user wants to search something up, they first search for a topic in web-rings, and then they select that web-ring.
From a usability perspective, that doesn’t feel great. How does a user find the first web ring search engine? What if they don’t want that multi step process? How do users avoid predatory web rings that are trying to sell them stuff? How does this compete with existing search?
Instead of returning a random number, what if we make the program guess?
This is a sign that our (in the anglosphere) laws are broken: vigilante justice shouldn’t feel necessary. But because executives, shareholders, and employees are literally getting away with murder, it feels appropriate.
Nice!
you just need to say the magic words…
The Venn diagram of Lemmy users and Outlook users is probably pretty close to two separate circles. I’m sure there’s some commonality, but probably not a lot.
Debugging. It’s a whodunnit where the victim, murderer, and investigator are all you.^(apologies to Filipe Fortes)
As someone who has tried to make useful and accurate progress bars: fuck progress bars.
I thought those were for only when shit is seriously wrong and execution can’t continue in the current state.
That’s how it starts. Nice and simple. Everyone understands.
Until
some resource was in a bad state
and you decide you want to recover from that situation, but you don’t want to refactor all your code.
Suddenly, catching exceptions and rerunning seems like a good idea. With that normalized, you wonder what else you can recover from.
Then you head down the rabbit hole of recovering from different things at different times with different types of exception.
Then it turns into confusing flow control.
The whole Result<ReturnValue,Error> thing from Rust is a nice alternative.
I remember getting these for games. They were awesome, but they never fit my keyboard.
what if the spores get thirsty?
Poverty and pressure to commit pension fraud were shown to be excellent indicators of reaching ages 100+ in a way that is the opposite of rational expectations’.
I love shitting on Python, but I feel like all those problems are present in libraries for other languages as well. There’s a tonne of that crap for JS/TS.
Similarly, I find a fair number of Rust crates (that I want to use) have virtually no doc or inline examples, and use weird metaprogramming that I can’t wrap my head around.
I am brainstorming right now.
M E T A
Let me guess, the downside is infinite teeth.
What is spilled cannot die
The proposal should include mechanisms to support moderation and user feedback. That flavour of crowdsourcing is difficult because users, search engine maintainers, and web ring participants may be malicious.