Okay, but is being present at a protest where others push through a barrier enough for the first amendment to no longer apply or do we know he was one of the people doing the barrier breaking? The original post implies he bailed out after only 5 minutes - quite possibly because he wasn't on board with the (relatively mild) escalation. At this point, we don't know. But if he did cross that line, he should be criminally prosecuted like the students with American citizenship (if they even are...) and not presumed guilty being punished via the immigration system without any kind of trial.
Can we charge all Jan 6ers with the murder or manslaughter of the congressional security police officers?
There's the case of the getaway driver in a bank robbery that resulted in murder also getting murder, and that is basically what the two poster up is advocating for.
I mean, given how the site performs on average I don't think they've optimized so much that the extra cpu cycles of ANDing with the fixed constant of 2^64-1 and then looking up or hashing a 16 byte integer - whatever they do - rather than a 4 byte one would increase the load significantly. Let's be pessimistic and say it's 20 extra cpu cycles, that's not gonna be much of a problem if their load balancers were made in the past 20 years.
Perhaps a little tin foil hatty and definitely not the only reason but Microsoft owns Github and also makes a boatload of money off of Azure. Incumbent cloud providers like Azure have a major advantage in terms of having plenty of IPv4 addressing available whereas a new entrant to that market would have to buy or lease that space at a premium. Thus, these companies have an incentive to keep IPv4 a necessity.
IPv4 is going to be a necessity for many many decades no matter what Microsoft do. Even when IPv6 is at 99%, people aren't going to want 1 in every 100 people to not be able to access their site at all. It'll need to be like 99.9% before we start seeing serious IPv6-only services.
I don't know what the percentage would be, but we do have some historical precedent that could give us a clue.
Best one I can think of is when bigger websites started actually dropping SSLv3 and TLSv1.0 (and later TLSv1.1) support, cutting off older browsers and operating systems. Google and Amazon still support TLSv1.0, but plenty of others (including Microsoft) have dropped 1.0 and 1.1. HN itself doesn't accept 1.1 anymore either.
Then there's browser support. Lots of websites - big and small - cut off support for Internet Explorer 6 when it was somewhere below 5% marketshare because the juice was no longer worth the squeeze. Of course, few of those actually fully cut off the ability to browse the (now broken) website fully but it's a datapoint suggesting trade-offs can and will be made for this sort of thing. Or to put it in the present: a significant amount of webapps don't support Firefox (3% market share) to the extent their product is completely unusable in it.
Sure, but the implementation in the public clouds is totally backwards.
What they should have done is have their core network default to IPv6 with IPv4 an optional add-on for things like public IP addresses, CDN endpoints, edge routers, VPNs, etc...
Instead, their core networks are IPv4 only for the most part with IPv6 a distant afterthought.
Coincidentally, I bought a 12v car horn yesterday with the intent of wiring it into my ebike's power supply with a little button on my handlebars.
Not because of other cyclists or pedestrians wearing (anc) headphones but because modern cars are so heavily sound-proofed they don't hear a bicycle bell anymore. A recent incident with an inattentive taxi driver in a brand new EV nearly flattening me prompted me to want to pursue this.
I'm still waiting for my cheap AliExpress dc-to-dc step down converter but otherwise I have everything I need and I think it should work. The horn module itself is definitely loud enough: I connected it to a 12v power supply at my desk and jumped out of my chair.
Yeas ago I motorcycled a lot, all over the world. I escalated to an air horn and hi-viz. But I pretty quickly realized that these made no tangible difference to the behavior of larger vehicle drivers. So I ended up for later vehicles with a stock horn and hi-viz only for heavy rain.
These days our family cycles a lot for commuting. It’s really easy to observe that people in vehicles treat us far better if we look like humans, wearing normal street clothes, rather than wearing high-viz or, far worse, cycling gear.
The bike bell is for polite notice, not alarming. The best alarm system you have is your voice, which is variable volume and tone. For ultimate effect slap the panels of cars, as it is very loud inside the vehicle.
Slapping panels in the US will occasionally get people trying to fight you, as I've had happen. Not really sure what a good solution to that looks like short of cultural changes.
As a pedestrian I slapped a panel of a slow car that failed to yield to me at a crossing. The driver glared at me and looked ready to reverse into me. I never slapped any panel any more.
Sadly I had to kick a few cars that thought they could run me off my motorcycle. Worked every time. All of them didn't look out the window or they would have looked right into my face. Yelling and horn did absolutely nothing.
Most of them were extremely apologetic or even shocked (as if I appeared from thin air). None of them were angry for scratching their door. Some people are just lost in thought it seems...
> or even shocked (as if I appeared from thin air)
Motorcyclists are invisible. Never rely on others seeing you, ride as if they're an obstacle you have to navigate.
You can hide a whole truck behind the A-pillar of modern cars, let alone a motorcycle. At certain angles, human eyes have complete blind spots that we're not aware of because our brain filters them out. Motorcycles fit perfectly into those.
Never hover in people's blind spots. Pass quickly or stay back. Do not drive parallel with another vehicle. Goes for cars too.
When approaching another car perpendicularly (like an intersection), remember that humans lose depth perception because their nose covers one of the eyes. A driver literally cannot tell how far you are. Our usual proxy is the distance between headlights. Motorcyles have 1 headlight so this heuristic doesn't work, but we don't realize that it doesn't.
Yup. If you don't have armor around you the only real defense is to assume you are invisible unless you know they've seen you or can't help but see you (for example, going in the traffic direction in front of a stopped car that's waiting to go--they're looking at the cars, they'll see anything else coming along.) Doesn't matter if you have wheels or feet under you, you still are invisible.
Oh I know. They look at me while turning left cutting me off.
Maybe I need a bigger bike, the 2cyl 400cc is particularly invisible. ;)
Best one was a woman who cut me off doing her left turn. I high-beamed her and honked. She put her hands in front of her face and came to a dead stop in my lane directly in front of me. I was already braking before I honked. Nothing happened. I stopped wondering and just assume everyone is out to kill me.
> I high-beamed her and honked. She put her hands in front of her face and came to a dead stop in my lane directly in front of me.
Personally I skip the honking and high beams. Just perform evasive action assuming driver will continue on their current path at roughly their current speed. Swerving behind their path of travel usually works great.
Spooked drivers behave erratically. Very dangerous.
So far I've had 0 serious incidents in ~8 years of riding. A couple close calls when I was being an idiot. So I think my approach is working :)
Honking is more for the people behind/around me. I also don't want to be hit by inattentive people following me to closely.
May I ask where you are riding? I am currently in Bavaria. The danger level is usually higher after the winter. Drivers need to re-accustom themselves to sharing the road with two wheeled riders.
Evasive action could be even more dangerous in cities. In my experience being able to come to a stop without hitting anything is even better.
Lot's of dead people had the right of way. Ride safe, I agree. I also had 0 accidents so far in 30 years. But you still experience new things you hadn't thought would be an issue.
San Francisco Bay Area. I never got into motorcycling back in Europe although the roads are lovely, the short riding season felt like a deterrent. Also the extremely long process to get a license.
Here in CA it was almost scary easy to get M certified.
When I was commuting 60k/day on my bike in shitty suburban conditions, I used one of these instead - you get limited use per trip, but you can always fill it up with a CO2 cylinder/bike pump:
That’s a crappy pressure vessel holding 350ml of 80psi air, for about 100J of stored energy. I’m not entirely sure I’d be comfortable with that, especially anywhere with my face in the line of fire it it fails.
Those two pressure vessels are highly engineered and are wrapped with materials with pretty good tensile strength. Also, they’re made out of materials (fabric and rubber) that absorb a decent amount of energy when they tear and that don’t fragment. And the whole assembly usually depressurizes slowly.
Having personally blown up beverage bottles by overpressurizing them (be very very careful doing this!), when they go, they go violently.
I've blown up beverage bottles for fun. Hooking an air compressor to a 2L bottle and exploding it makes a satisfyingly loud boom.
*We had a valve on the air line so we could be at a safe distance when pressurizing. Be very careful. It's unpredictable exactly at which point they'll blow. Sometimes they hold full pressure for a couple seconds and then go.*
When we did it, it always went off on its own. It's been a long time since I did it, but I think the longest it took would've been on the order of 30 seconds. Really makes a person jump when it finally goes.
Because the danger posed by a fairly low energy pressure vessel is highly related to it's failure mode. That's why OSHA has rules about what compressed air pipes can be made of--it's not about the pressure resistance, it's about what will happen if one fails.
It's likewise why most military boom is mostly not actually boom. With artillery you obviously need a very tough case, but standard aircraft-dropped iron bombs are mostly that: iron. They don't need that kind of strength except specialized bunker-busters, they're built that way because for a given weight of bomb you'll do more damage by throwing bits of bomb casing from a smaller charge than from a bigger charge without the fragments.
If this is a modern bike, 80psi is way too high. 50psi is sufficient and will give you a more comfortable ride as well as higher efficiency on real-world surfaces.
80+psi is for old-style road bikes with narrow 23mm tires. Modern bikes (even road bikes for racing) don't use these any more; 28mm is the minimum these days.
Not to be pendantic (but to be pendantic) 80psi is the correct pressure for 28mm tires ridden briskly on good roads. At least according to ye olde Silca tire pressure calculator. Back in the day when folks ran 23mm tires they would typically run above 100psi (though that may not have been optimal...).
That calculator is wrong. Cycling people have been overinflating their tires for ages (as well as using too-narrow tires), with the assumption that the ground is perfectly smooth. Lower pressures yield higher efficiency (and better comfort) on rougher surfaces.
You're overinflating your tires. A lower pressure will increase your speed and efficiency unless you're riding in a velodrome. Here's a video about this:
The video's result for both tires they tested was peak efficiency at 5 bar. They had a really coarse sampling of a whole bar, so that works out to a pressure of 65–80 psi.
It's a soda bottle - it fits in your water bottle holder, and you can replace it for a couple of bucks if it fails. 80 psi is pretty low pressure (typical narrow tires are 100-120) and the bottle itself is very low mass, so the fabric around the bottle should ensure safety if it bursts.
IIRC these came out in the early-mid 90s; a bike messenger trick at the time was to fasten the horn to your handlebars with velcro, so you could take it off and hold it near a car window when triggering it.
I suppose I should maybe not worry about 80 psi so much. An ordinary bottle of soda on a moderately warm day is around 80psi. The energy is 1/2 * pressure * head space (roughly), and head space is minimal. But you can chill it in the fridge, then open it and quickly pour out half, then close it and let it warm up, and you may still be near 80 psi, and I’ve never heard of anyone getting maimed by an exploding soda bottle.
An hour and a bit each way, took about as much time as public transit and better than a coffee for waking up. A good road bike goes a long way, and the suburbs suck for road sharing but are great for not having to stop at many lights.
I wonder if one of those recently-emerging Chinese electric blowers that sub for canned air would generate enough air volume to sound the horn usefully. Possibly not quickly enough.
I did that, but I used battery - couldn't figure out how to hook up to the e-bike's 50v electrical system (plus the DC-DC converter with high enough current...)
So I am using LiPo 3S, 2200mAh. Works like a charm. I keep it at its storage voltage (3.7-3.8v per cell), and it hardly drained the battery (there is no paracitic drain). Whole thing was like $20.
Some locales are downright itching for a reason to road rage so I don’t blame you. One thing I have to say about being a motorcyclist is that our residents in California are so considerate and have never once mistreated me for beeping, lane splitting/filtering, stalling my bike at a green light, etc.
At least they’re forward about it - I’ve lost count of how many bike accessories claimed to be USB C, but they only charge when connected to their specialized cable that converts from USB A to C.
Double-sided USB-C connections require a handshake before sending voltage. USB-A ports can have the 5v line active at all times. Cheap USB C gadgets often don't make the handshake, they just use it as a 5V input, necessitating an A to C cable.
If you add 5.1kΩ pulldown resistors on the CC lines for USB-C, you can get the standard 5V without a handshake although current may be limited by some chargers without negotiation.
I think you're overstating this. The "handshake" is purely 2 simple resistors correctly installed. The problem is a lot of folks do it wrong for various reasons, most likely never testing with anything more than type a to type c cables.
One of the many deficiencies of usb-c (who knows what power your cable supports, charger supports, if you accessory will charge, of it will connect at all)
There is no handshake, all that's needed are two 5.1 kΩ pulldown resistors. By omitting them the manufacturer saved all of about 0.1c and made their device incompatible with compliant usb-c chargers.
> because modern cars are so heavily sound-proofed they don't hear a bicycle bell anymore
Agreed. I had a supercharged V8 Jaguar that I could barely hear.
And my Audi has a system that actually pumps engine noise into the cabin, so you can hear that, but not the outside world.
The Fire Department I was at was looking at "thumpers" - augmentations to sirens that make cars in front of them vibrate (a la those people playing too much bass too loud).
Not just sound proofing, but inattentiveness. I've been behind people on semi-rural quiet roads with my 40,000lb fire engine behind them, lights, sirens, and airhorns, and they've driven for a mile or two completely oblivious.
on the rare occasions where I need to loudly indicate my presence to a motor vehicle I wouldn't really want to be moving my hands - if I have time to move a hand to a horn I probably have time to brake/manouvre instead.
Generally in those situations I shout really loudly at the driver, and in general they seem to hear me
Aside: folks living near bike paths where this happens are going to suffer. I don't know what the solution is, but increasing volume to defeat increasing sound-proofing seems like a recipe for noise pollution.
I had a digital bell from aliexpress on my winter commuter because pogies on the bars prevented a typical dinger. It was very annoying and very effective; my wife referred to it as "the friend maker".
LOL. I put the loudest 12V train/air horn I could buy on my 60 mph escooter with a 72V to 12V buck converter and a motorcycle handlebar button. It was pretty easy to install. (I added a fuse too.) Stupid motorized vehicle drivers get the horn of doom.
cause a lot of lives have been lost! they even thoroughly blew up a school. it's generally considered to be in somewhat poor taste to celebrate your personal gain in situations like that. it's like openly celebrating a massive passenger airliner crash because you happen to hold stock in their biggest competitor.
I understand the ethical viewpoint, but does it generalize, and where are the lines of moral good/neutral/bad when you ”buy the dip”?
Bombing civilians is despicable, so obviously bad to buy.
Bombing legitimate targets is accepted warfare, but there are always civilian casualties in war, so war in general must be bad to buy.
Other causes for dips?
Insane tariff policy drives small companies to the ground and leaves low income families struggling, must be bad to buy.
Global recession hits due to a pandemic which claims innumerable civilian lives, must be bad to buy.
Global recession hits due to some other factor, lots of civilians die from depression or violence, must be bad to buy.
A huge market dip hits and causes millions of leveraged investors to lose most of their principal to margin calls, companies go bankrupt, people lose their jobs, lots of civilians die from depression or violence, must be bad to buy.
Is there a scenario where ”buy the dip” is not immoral by these standards?
A defect in a series of automobiles causes hundreds of deaths, causing the manufacturer’s stock price to plummet. Is it bad to buy?
Thousands of people die in car crashes every day and it barely registers.
Civilians die and are killed in horrible ways every day.
I think there's an important distinction in making money off of a tragedy your investment had no part in causing and happily announcing you did so.
To use a slightly hyperbolic example: A company that makes body bags is always going to be making cash when a massive amount of people die in a tragedy. That's fine, without that we wouldn't have body bags which is a thing we need. But they're not gonna do a press release on September 12th 2001 about how their sales volumes have spiked and are expected to continue to rise as victims are being pulled from the rubble. I would hope their execs are not watching CNN and rubbing their hands in eager anticipation when they see the second plane hitting the towers.
increasing the (social) pressure on maintainers to get PRs merged seems like the last thing you should be doing in light of preventing malicious code ending up in dependencies like this
i'd much rather see a million open PRs than a single malicious PR sneak through due to lack of thorough review.
yeah, but I got the impression that the EU is very much doing it as a retaliation to the US and UK doing it. Tho they could have limited it to just those countries.
The US, maybe. But wiki suggests ETIAS (the EU one) was proposed in 2016 whereas the UK ETA idea was created around 2023, so ETIAS can't be a reaction to ETA - perhaps the other way round?
I'm not sure if, without Brexit, the UK would have ended up with ETIAS anyway - it's a "mostly Schengen but not exactly" thing so it would have depended on what agreement they came to.
My impression was that the EU did it to prevent people doing visa-free layovers from claiming asylum, while the UK did it to negotiate a dual exception with the EU in the future.
ETA is a visa to the entire world in all but name. I'm not looking forward to the future where every county implements is and visa-free travel becomes a thing of the past.
Congratulations, you're a lot smarter than the average person. I understand this is sometimes a bit annoying, but at the end of the day it's probably something to be grateful for.
table stakes, but people still mess up on it constantly. The "yeah, but that's only a problem if you're an idiot" approach to this kind of thing hasn't served us very well so it's good to see something actually being done.
Trains shouldn't collide if the driver is correctly observing the signals, that's table stakes too. But rather than exclusively focussing on improving track to reduce derailments we also install train protection systems that automatically intervene when the driver does miss a signal. Cause that happens a lot more than a derailment. Even though "pay attention, see red signal? stop!" is conceptually super easy.
I'm not saying it's not important, it is. I just don't believe that '[the] majority of memory bugs are from out of bounds access'. That was maybe true 20 years ago, when an unbounded strcpy to an unprotected return pointer on the stack was super common and exploiting this kind of vulnerabilities what most vulndev was.
This brings C one tiny step closer to the state of the art, which is commendable, but I don't believe codebases which start using this will reduce their published vulnerability count significantly. Making use of this requires effort and diligence, and I believe most codebases that can expend such effort already have a pretty good security track record.
The majority of security vulnerabilities in languages like C that aren’t memory safe are due to memory safety issues like UAF, buffer overflows etc etc. I don’t think I’ve seen finer grained research that tries to break it out by class of memory safety issue. The data is something like 80% of reported vulnerabilities in code written in these languages are due to memory safety issues. This doesn’t mean there aren’t other issues. It just means that it’s the cheapest exploit to search for when you are trying to break into a C/C++ service.
And in terms of how easy it is to convert a memory safety issue into an exploit, it’s not meaningfully much harder. The harder pieces are when sandboxing comes into play so that for example exploiting V8 doesn’t give you arbitrary broader access if the compromised process is itself sandboxed.
I flew out of the UK twice in relatively short succession in ~2018 and the first time was out of London City: did not have to take off my shoes. I was pleasantly surprised by this and concluded common sense had prevailed and it was no longer necessary. The second time was Gatwick, and based on my prior experience I did not take off my shoes. I got yelled at because "everybody knows you have to take off your shoes at the airport!". Then got subjected to an extra search of my luggage as punishment. Of course there was a razor in my bag of toiletries (one of those Gilette cartridge ones with a million blades - not an oldschool safety razor) and promptly 'got got' for that as it could have potentially injured the person searching my belongings. 0/10 would not recommend.
reply