7,638 karma · joined June 22, 2009
https://mastodon.social/@poswald
https://www.makeleaps.com
https://hntokyo.io
I run HN Tokyo meetups in Japan.
Always looking for awesome people to meet up with. Get in touch!
pauloswald@gmail.com
[ my public key: https://keybase.io/poswald; my proof: https://keybase.io/poswald/sigs/HVlTjzK0n89ogL4IrN4QAX1JSJJUZRzfp_9MrlPIJ0A ]
Verifying myself at HNTokyo: aspe:network.forum:UTNSZUQ2C6PNVXP2VC36IN5NPQ
If you think about the logical hierarchy of controls on a browser it should be:
- global stuff (extensions, sidebar reveal button, etc...)
- tabs
- url, forward/back/reload buttons, etc..
If you're going to mix the global controls with url I still think the tabs should go on top (like real-world tabbed folders). Chrome gets this right and Safari should just copy them.
It's just not composable enough. You can't reuse business logic in web views, forms, admin views, API, background processing, etc... time and time again the Django tooling gets you 90% of the way there, then leaves you with no way to do what you need done cleanly so you one-off an ugly solution to it. Soon you code is littered with them.
We ended up with a solution much like this article and despite it being a bit of a pain it always works in all contexts.
I know 'big medicine' is the target of liberal and conservative critics alike, but it really does seem like once the medical community gets their reputations sucked into a bad theory it will take a good 40 years to change direction. I know good science is being done too, I just wish that we hadn't started a depth-first search decades ago.
There is real promise in the various inflammation-based theories. This drug seems like a big distraction.
I have one on my shelf here that I dug out of a river bank and made with my kids... we saved it and I shined it up by sprinkling sifted clay dust onto it and rolling it on a hard surface as it dried
edit:
One thing they could try to do is to sandbox the parser itself to lower attack surface area... but the damage is done here and I really doubt they will win a security tit-for-tat with Signal.
It attacks Cellebrite's ability to operate by casting doubt on the reports generated by the product that their customers may wish to use in court.
It places them in legal peril from Apple, and removes any cover Apple would have to not take legal action. (I assume someone at Apple knew they were shipping their DLLs?)
It makes a thinly-veiled threat that any random Signal user's data may actively attempt to exploit their software in the future and demonstrates that it's trivial to do so.
edited to add a bonus one:
Publish some data about what they are doing to help create a roadmap for any other app that doesn't want their data to be scanned.
I don't like using SMS for 2FA because it encourages people to social engineer the phone company to port the victim's phone numbers. I wouldn't want crypto in my messaging app for a similar reason.
Right now hacking a user's Signal account means you get some txt messages. Big deal. With payments there is now real reason to try to hack Signal accounts because some percentage of them will contain money.
I feel like there are a lot of parallels in modern-day situations. The common wisdom around PR is to get control of this kind of situation to prevent it.
It's easy to feel FOMO but if you educate yourself and still are not comfortable, then you're absolutely right to sit it out.
I guess I'm just calling out the people who are making fun of them for having their status page dependent on the same hardware it's monitoring when it's not clear that's the case just because they are both down?
I would suppose if it's a different TLD domain, then it would be more likely to conclude that.
https://github.com/oauthlib/oauthlib/blob/master/oauthlib/oa...
This seems to be very uncommon amongst service providers.
A third party is any party that does not fall within the definition of first party above.
This policy doesn't distinguish between companies that own multiple top level domains. I understand that it may be technically hard to figure out but at the policy level are two domains owned by one company really third party to each other?
Are example.com and example.us really always different first parties? What about apple.com and iCloud.com? Or those redirect chains that happen after logging into google such that login cookies are set on youtube.com and whatnot?
It does say 'in practice' but I feel like this is mistaking a technical limitation that it's hard to know if two TLD's are controlled by the same legal entity for a policy.
https://en.wikipedia.org/wiki/List_of_cognitive_biases
really... you think you know them all but you don't. Everyone needs to understand the IKEA effect for example
True, it can be hard to get to the stored passwords for manual entry and it doesn't work with a few sites, but generally speaking it picks random passwords, saves them fairly reliably and prompts to use them with biometric protection.
Making platforms more similar so it easier to target that platform is very nice for developers. If you can do it without losing what makes users want the different devices then there's no downside.
Tariffs against China are actually a tax on the American citizens, and only causes increased prices and unemployment.
and as far as I can tell you believe:
Tariffs against China are actually a tax on the American citizens, which causes increased prices and (eventually?) a shift to a different producer.
but that's not the argument you're making.
So it's effectively a way to convert your ICE car into a zero-emission EV by using that fuel.
I finally threw in the towel and bought a few of the new Synology Mesh routers.