dan

joined 2 years ago
[–] [email protected] 61 points 2 years ago* (last edited 2 years ago) (2 children)

I mean. Sorta.

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.

Dude’s allowed to be annoyed about it.

[–] [email protected] 6 points 2 years ago (2 children)

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.

[–] [email protected] 3 points 2 years ago (4 children)

You mean HTML, CSS, JavaScript, etc?

[–] [email protected] 5 points 2 years ago (7 children)

What’s the “web protocol”? Are you talking about HTTP?

[–] [email protected] 48 points 2 years ago (6 children)

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?

[–] [email protected] 1 points 2 years ago (1 children)

I know but I really like the name wefwef so I’m presenting that’s not a thing ;)

[–] [email protected] 3 points 2 years ago* (last edited 2 years ago)

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.

[–] [email protected] 9 points 2 years ago (7 children)

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.

[–] [email protected] 3 points 2 years ago

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.

[–] [email protected] 8 points 2 years ago (4 children)

No but a lazy copy of someone else’s work might be copyright infringement.

[–] [email protected] 15 points 2 years ago

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.

view more: ‹ prev next ›