>alt-righters love to larp about civil war, ton of them in this thread
Oh, yeah, they sure do. What happens when everyone eventually figures out politics is pro wrestling, and the same donor class runs the whole show? The fake left/right divide goes away, and the rich find themselves outnumbered, and their money won't buy them a way out.
It definitely will. The only civil war could be working-class cops and PMCs against people who are paid by the hour, who have to show up with an hour's notice, who have their urine tested, who have their complaints about discrimination and dangerous conditions ignored, and who are fired at will - and that war is always going on.
Wealthy people will (do) rely on people with guns to protect their physical vicinity, and the technology, organization, and propaganda provided by the people posting on this thread to multiply the effort of the people with guns.
edit: I bet you could have a civil war in the US that wouldn't affect the financial industry or the wealthy at all, even while the war was going on. Personal security would just become one of those things that people looking for jobs at FAANGs would expect as part of the package.
Correct, it doesn't seem like they did; the NYT story was debunked.
> dragged an enemy flag through the senate
The rebel flag isn't an "enemy flag" any more than the Republic of Texas flag. It's a historical curiosity that has some function as a completely detached cultural signifier.
They killed a cop? Wow, I only read NYT's retraction of the story, if there was an update on the retraction then it missed my radar. Can you point me to a link from NYT claiming that rioters killed a cop?
He deleted his account for the reason stated in the top comment (https://news.ycombinator.com/item?id=25672752) about Facebook is changing their policies, now that Biden has been confirmed as president to suck up for the ad deals.
He specifically ordered Pence to throw out the Electoral College result. Pence refused on constitutional grounds. How is that not an attempt at sedition?
Never thought I'd have anything nice to say about Pence but pushing back was the right thing to do here. H/T to him
To say nothing to his tacit approval of a mob storming the capitol on EC certification day...
The reality is that we just don't know what happened. We cannot know what happened. Perhaps some nations and companies are just too big and too powerful to exist and people are now starting to realize that.
Probably not because of the ban. Probably for Facebook's relentless facilitation of the person who incited treason and sedition, as well as the cultivation of conspiracy theory groups that produced the insurrectionists.
Can you point to any resources that explain how to eradicate your surfing behavior from Facebook's tracking? I'm sure it's not as simple as clearing cookies and never visiting a Facebook property again.
> All the skills I have built over the course of almost a decade are obsolete now, because I do not imagine myself working for other people as an iOS dev without having my own hobby iOS apps on the App Store. It feels like all the blogging I have been doing has been a waste because I cannot participate in the knowledge I myself write, and it’s pointless to engage in the knowledge of others if I cannot try what they write.
The fact that a faceless entity can lock you out of developing like this is just wrong. I fear for the future of such closed off ecosystems.
The URL bar is a disaster for end users. It's full of random junk that users can't read so they stop trying, which means they can then be tricked by phishing websites hosted on any domain at all. Research shows about 25% of users don't look at the URL bar at all even when typing in passwords, they navigate purely by sight, so it's impossible to stop them being phished. The human cost of the resulting hacking is significant.
The fact that the software industry has routinely prioritised historical inertia, the needs of web developers, and all kinds of other trivialities over the security of billions of people is embarrassing. I'm glad to see the Chrome team finally get a grip on this and make the URL bar actually useful for people.
> The URL bar is a disaster for end users. [...] 25% of users don't look at the URL bar at all even when typing in passwords
"Side view mirrors are a disaster for drivers. 25% of drivers don't even check them before making a turn."
[I'll stop the metaphor here, as I think my point was clear]
This change does exactly nothing to improve security. As for usability, it just puts one more layer of paint over the underlying "complexity" - and we've seen before how well that works (see basically every part of Windows 10 for examples).
As someone who has worked on the front line of the fight against phishing and account takeover in the past, I can assure you and others that you're dead wrong. Making this change was a recommendation I made to the Chrome team years ago because the number of people who would reliably type in their username and password to a site hosted on hacked web servers (supershop.co.hk/account_login.php etc) was just so high. And when those accounts got hacked, scamming and sometimes even extortion would follow.
Your side view mirror metaphor is unfortunately not clear at all. The side view mirror is simple and performs its function correctly as designed. It can't really be improved without totally replacing it with something else like a camera. Now of course not everyone will use the URL bar even if it's redesigned to work correctly. But right now the bar is practically designed to look as intimidating and useless as possible.
Perhaps you're so used to parsing URLs in your head you don't realise it, but URLs are a baroque and absurd design that nobody without training could properly figure out. It's basically random bits of webapp memory and protocols splatted onto the screen in a large variety of different encodings. In a desktop app dumping RAM straight onto the screen would be considered a severe bug. On the web it's tolerated for no good reason beyond history.
To give just one example that has regularly confused people in the past: URLs are read left to right except for the domain name (the important part) which is read right to left. You don't stop reading a domain name at .com, you stop reading it at the third slash or possibly a colon, but that form is rare.
As someone who has had to teach grumpy old high school teachers how to not fall for phishing and mitm attacks, I really can't see the problem here.
The way I used to teach was very simple and very effective: there are 3 parts to a URL - the first part tells you if the connection is secure, the second part tells you who you're connected to and the third part tells you where on that site you are. The first part needs to be httpS, the second part needs to be the site you're expecting and the third you can ignore. They're even shaded differently to make it easier to read. "If you're going to Google and the black part ends with anything but google.com, call IT" made sense to even the oldest and most reluctant people I've had to deal with. The problem was actually getting them to check every time and not forget.
It seems to me that this change will not help people without training, change nothing for people with training, and make sharing links even more confusing for everyone.
Are you saying someone is less likely to get phished on "supershop.co.hk" than on "http://supershop.co.hk/account_login.php", even where the http:// part is replaced with a red padlock and /... is grayed out?
I see only one real solution to phishing: don't let users type passwords manually. WebAuthN and password managers both automatically read the domain and won't try to authenticate on a domain that isn't a perfect match. I've had more success with that than any other anti-phishing measure I've tried deploying (history-based domain trust, explicit trust on first use popup, detecting unicode gaps and domains in credential fields...).
Sure, absolutely. People understand domain names, they're found on billboards, adverts, business cards, all over the place. And it's a simple text match. Does the bar say "google.com" or "google.co.uk"? Yes? Then you're on Google. So when it's simple people get used to checking and can be reasonably told they're expected to do it.
The greying out and replacement of padlocks etc, the anti-phishing training, it's all just working around a historical design problem in browsers. There's no need for it to exist. Notably, mobile apps don't have this problem.
Exactly. This fits right into his playbook of (1) cry loudly about something and say you’re going to take action (2) do nothing while his base gets pumped on how Trump is “hard on Twitter” and not putting up with their obvious bias (3) the next scandal drops in a week, everybody moves on and forgets.
