froddd
froddd on Hacker News
And is not viewable in the UK. Not hitting a lot of points in the shareability league
Do you have a source for those claims?
The “source” you do mention seems rather anecdotal, and linking it to the discussed topic requires a fair number of other assumptions, too.
Most places have laws against publishing such content, not recording it in the first place.
Edit: I do however agree with the sentiment.
Most of what I’m reading on rootmy.tv says the vulnerability it exploits has been fixed. So, if one were to keep software up to date on their TV, there is an improbably small chance it can actually be remotely jailbroken — am I reading this right?
This is exactly how developers of malware want you to behave. Update without really thinking about it.
I do wonder how long it will take before an attack is developed by submitting a semi-genuine vulnerability, shortly followed by a ‘fix’ including malicious code.
The manifesto refers to “working software”. It does not say anything about “okay quality”.
The app settings offer a way to set default browser to the system default (which is what I have selected), as well as a toggle to “Ask me every time” — I have this turned off and never see the pop-up.
EDIT: also just tested turning this checkbox off. I then clicked a link in an email, got the pop-up, unchecked “ask me every time”, clicked default browser, and didn’t see the pop-up next time.
I’m in the UK and use the Gmail app, I don’t ever see this sheet. Is this US-only?
I don’t see the sheet for imgur.com either because, well, they’ve blocked access completely for UK users. :shrug:
I thought the law said it’s illegal to post footage of people without their consent if it’s publicly accessible. Which means videos of some random on your driveway or some random in a public place are treated the same, but this depends on where they’re posted. This doesn’t address the fact that this seems to be generally flouted!
Would love to hear more from a lawyer on this!
Yes, that demo. You can clearly see the resize pointer flashing briefly, but the user continues aiming right inside the window. I’m not sure why he’s not stopping when the resize pointer appears. It seems erratic.
Indeed, just enough. And the correct resize pointer shows all along the rounded edge, so I agree, this doesn’t seem like the problem it’s made out to be.
I’m referring to the demo in the original article. The mouse pointer moves rather rapidly onto the inside of the window. You can just about see the resize pointer flashing as the user does so. I don’t think I ever attempted to resize a window with such erratic mouse movements. Approaching the corner at reasonable speed shows the resize pointer where expected.
This is absolutely true. The demo in the original article seems quite deceptive in that respect. Nobody would attempt to resize a window by launching their cursor at the corner with great speed as the demo shows. The resize pointer seems to show in exactly the right place, and allows for an extra hit area slightly outside the rounded corner — I don’t see any problem with that.
As for the fact that one cannot resize from inside the window, it makes absolute sense for every other corner of the window, where the user would instead be clicking an icon or some other button (try the top right corner of the finder, where the search button sits).
So, while I agree on the whole that Tahoe is a huge step backwards in terms of design, this seems like an odd gripe to point out, as it doesn’t in fact seem to be an issue at all.
Edit: clarification
Just installed it to see if it might be better than AdGuard on memory usage, and now I’m getting constant “Pssst! You forgot to apply some settings” notifications as soon as I leave the app. Clicking it takes me back to the app, where it does an update of everything, and… That’s it. Leave the app again, and the notification reappears. Quite annoying!
Edit: it appears it doesn’t remove ad content blocks like AdGuard, and doesn’t let me pick and choose elements to add. I might revisit in a few months, but for now I’m back to AdGuard.
The only part of the API that is free is the passwords API, which would not help for this use case.
Every other endpoint requires a subscription. This is very far from “The API is free”.
> searching by account wouldn't tell you anything useful
The API can return the domains listed in stealer logs for a specific email address: https://haveibeenpwned.com/API/v3#StealerLogsForEmail
Change the password for what account though? The dashboard doesn’t seem to list the actual website(s ) linked to the email/password breached, so how am I to know which password to rotate?
If I follow the recommended best practice, I have a different password for every website or service. That could be hundreds of them. Am I supposed to rotate all of them every time there’s a breach?
The details about the “Stealer Logs” on the dashboard even state:
> The websites the stealer logs were captured against are searchable via the HIBP dashboard.
There is no way to use the HIBP dashboard to figure out what domains my email address appears against.
Am I meant to change all passwords associated with that email address? Or do I need to get a paid subscription to query the API to figure out exactly what password(s) to change?
This has always confused me. On the one hand, HIBP is an invaluable service, but, on the other, it does nothing more than stating you’re in trouble, with no clear way forward.
Interesting. I would say you’re definitely the minority here, and I would still argue that limiting content width does work better for most.
When you say you sometimes enlarge the font, how many words per line do you aim for or end up with, roughly? You’re describing behaviour that aims to render text more readable, so obviously it isn’t simply a case of “I like text content to be as wide as possible”.
If a text-heavy website does not constrain the width of its content, what do you tend to resize the browser to? Does it depend on text size? Or other factors?
Interesting choice of example. I would probably have gone with the PayPal or eBay apps, which (on iOS at least) still refuse to let you select the text from the address you have to send the item you’ve sold to.
Is the biometrics step (fingerprint reader) on macOS much different from a ubikey? I imagine implementation may have some differences, but in practice it seems I can already protect access to my GPG key using the built-in reader, so what’s the advantage of ubikey in that respect? Genuinely curious.
The argument that cyclists (implied: all cyclists) ride at full speed on pavement at all times is akin to arguing that cars (implied: all cars) go over the speed limit at all times. It’s daft at best, and utterly outlandish.
You should stop and have coffee in a street shared only by pedestrians and cyclists, and observe the behaviour of cyclists. I have observed it to be mostly slow, controlled, courteous and respectful of pedestrians.
The data you present does not say that:
> 35% des cyclistes tués, 63% des cyclistes blessés gravement le sont dans un accident sans autre véhicule impliqué.
35% of cyclist deaths, and 63% of cyclist seriously injured occur in an accident with no other party involved.
Another graph in that report shows that a vast majority of cyclist deaths occur while cycling for leisure. I would hazard that most cycling in cities is utilitarian.
Why would a VPN provider do that?
> Are there still customers giving tips as "a reward for good service"?
Sad if this is no longer the case.
In the UK at least (and the rest of Europe too, as far as I can tell), this is still very much the case. The curve varies with the individuals tipping. I would be quite happy to give 20% if the service was outstanding. I’m equally happy to not tip at all if the service was very poor.
Soya is a bad analogy here. When forests are being destroyed to grow soya, it isn’t primarily soy to feed humans, but to feed cattle/stock to then feed humans. This is an order of magnitude more destructive.
Edit: fully agree with the sentiment, getting rid of the profit-driven mindset would be beneficial to all.