I cannot find boomstick anywhere in here
19,028 karma · joined May 31, 2011
Iceland on the other hand....
This is all we want.
That and the subsidy, rare earth, power output decrease, and China manufacturing problems (them undermining the market with intentionally low prices to kill US solar). All of these problems have solutions, but the main problem right now is partisanship.
The only real problem is the inverter sync problem. Inverter supply increases grid instability, so much so that most residential units are not allowed to push back into the grid.
The only reason they "want it to be law" is so they can strangle competition.
And guns
And no foreign wars
And the right to marry whomever you want or be in a relationship with whomever you want.
And minimal State with demilitarized police.
And leaving you alone to do whatever.
I really wish Libertarians would actually win.
> Mercator useful for sailing
This is the only correct answer, and everything else is unscientific nonsense. It hasn't been replaced because... it just hasn't. Mercator + knots + nautical miles is a system that is extremely useful for navigation. Since we aren't sailing ships around a whole lot anymore, a lot of teachers forget to mention the relationship between the three. I imagine that was more common knowledge back in the day.
That being said, I do like the new proposed projection for how we use maps today. I think another useful tool would simply be overlay maps.
ATZ
AT&F
ATDT5551234
The truth is we need to drastically shrink the size of the federal government. Its unbelievably inefficient.
This is a large conversation about Consent, which is a concept Silicon Valley refuses to acknowledge.
First, what surprised me is that during the enrollment process, the client is not required to sign a challenge and the server is not required to check it. There's some irony here. Adding this to the flow would be simple layered security, instead of complete reliance on the TLS channel. Something for the Internet Standards people to take into consideration.
Next, passkeys are annoying the way most major websites use them. You can in fact, make a great login experience using passkeys, but not that way capitalone.com Google does (Sorry to pick on you two guys, but it's pretty bad). I won't even mention statefarm.com because their entire website is in a constant state of being javascriptastically broken. Websites treat Passkeys as an accessory, when really it should be the other way around. Passwords, and... sigh, sms, need to be treated as unwelcome accessories.
To make a better user experience:
1: When enrolling a passkey, use the consumers name and permanent business key on your side. Something like `John Doe - PK501867` where PK501867 is an external customer identifier.
2: Lose passwords. Make this a secondary login method on your website, hidden.
3: Don't require SMS "2fA" if they use their passkey. You shouldn't be doing SMS anyway, so stop.
4: Don't use the "well known endpoints" for passkeys or anything related. It's an annoying and confusing consumer experience. Let the user initiate the login. Don't be clever.
5: Instead, just put a button called "Login with Passkey". When they click it, begin the auth flow in the browser. Use async RESTful calls with proper verbs (POST) and correct http signalling. If they authenticate, then redirect. If they don't, update the page but don't cause a navigation.
This by far, keeps the browser 100% functional and follows a natural user experience. It pushes users to use their passkey.
Languages have conventions and best practices that aren’t portable.
We could port COBOL to c and do a crap ton of goto/jmps and make a
BEGIN MESS