When you use some service you have some expectation that they’ll treat you fairly and predictably. Sure their Eula let’s them do whatever the fuck they want legally but that doesn’t change the fact that if they opt take certain actions (like arbitrary taking people’s usernames) then they risk losing user trust.
If the admin just took your username one day would you just quietly accept it? What if they edited or deleted your comments? Would you just shrug and say “well it’s their site they can do what they want” and just walk away?
Look what happened when Spez got caught editing posts on Reddit, for example. Massive user outcry.
Ok well, the modern web technology ecosystem is incredibly featureful and flexible, it allows a huge array of options for building rich interactive applications, all delivered to your browser on-demand in a few seconds.
Sure some of the technologies involved aren’t perfect (and I challenge you to find any system that feature-rich that doesn’t have a few dark corners), but there really no alternative option that comes close in terms of flexibility and maturity.
So, how the hell is this supposed to prevent bots? Unless Google are planning to completely lock the browser down to prevent user scripting and all extensions then surely you can still automate the browser?
Did I say it was a native dropdown? Nope. I said it was implemented as a separate window.
You can demonstrate that by trying to take a screenshot of the whole window when you have an open dropdown (cmd + shift + 4, then press space to select a window), and you'll see the contents of the dropdown aren't in the resulting screenshot (but are if you select an area or screenshot the whole screen).
Regardless, the fix is the same: use the inspector tab to navigate to the option element inside the select in the DOM itself, you can manipulate the elements there, although if you want to change the styling supported CSS styles are extremely limited. If you really want to control the appearance of a select element you're probably going to have to render them yourself.
You can access the option elements inside the select via the dom and style them there. In most browsers on a Mac (which that looks like?) those selects are actually implemented as separate windows - not even part of the browser, so you’re going to struggle to access them directly.
Idk, maybe. There are thousands of copyright infringement lawsuits, sometimes they win.
I don’t necessarily agree with how copyright law works, but that’s a different question. Doesn’t change the fact that sometimes you can successfully sue for copyright infringement if someone copies your stuff to make something new.
I just don’t trust Brave very much. They’re doing ok now but eventually they’ve got to make some money. Their approach means they have to invest significant effort to porting fixes in chromium over to their forked version, and they can’t drop behind or they’ll have at least security issues. I’m not sure how sustainable it is.
Fair enough. I must say I didn’t even consider the per-search payment option - I just assumed it would be abusively expensive to encourage committing to a monthly fee, but clearly not! Thank you for demonstrating that so comprehensively.
That’s better but it still means I’d be using multiple search engines just so I don’t rack up costs indiscriminately. And honestly if I’m paying to use it that seems unnecessarily inconvenient.
$5/month for 100 searches per day (or something high enough I’d be unlikely to hit it when using it as my sole search engine) and I’d be totally willing to switch. As it is it’s just too expensive.
Kagi is so expensive. $5/month for 10 searches per day, $10 for 34/day. A staggering $25/month for unlimited searches.
I gave it a try after it came up a couple of weeks ago. It’s quite good, but it’s not that good. Its better than DuckDuckGo, it’s a bit less overloaded with seo spam than google, but it hasn’t found anything that I haven’t been able to find with my usual method - a combination of mostly DDG with smatterings of Google and a lot of adding “reddit” to searches.
I would pretty happily pay $5 a month for a single search engine that did everything, but I just use search too much so I’d have to keep my existing multiple search engine approach or pay loads.
If you post something on a public website and it gets indexed by search engines, how does that work? Or how about sending email to a mailing list that subsequently sends it on to all the recipients?
In each case those organisations would likely be data controllers rather than processers, so would need a privacy policy, decide on their legitimate basis for processing, mechanisms to handle SAR/RTBF/etc. My guess is Lemmy servers would need the same thing.
Technically speaking, things are far more secure today than they were back in the dawn of the internet. Protocols are now almost exclusively encrypted where they almost exclusively weren’t. Private communication is (in theory) easier to achieve.
Practically speaking, however, now there’s always somebody there attempting to monetise your interactions. To mine useful information from what you say, or to sell you something while you say it. Or both.
That’s only going to get worse with the rise of AI, as companies realise the vast databases of past interactions might actually be worth something.
Best you can really hope for these days is to retain some anonymity and some separation between your public personas.
Lmao.