Hacker Newsnew | past | comments | ask | show | jobs | submit | dpacmittal's commentslogin

I used Linux exclusively for 13 years. Moved to Mac because I wanted a laptop that could give me 10+ hours of battery backup.

The magnitude of performance difference alone immediately makes me skeptical of your benchmarking methodology.

I'm not an expert in any way, but i personally benchmarked [1] juiceFS performance totalling collapsing under very small files/operations (torrenting). It's good to be skeptical, but it might just be that the bar is very low for this specific usecase (IIRC juiceFS was configured and optimized for block sizes of several MBs).

https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/1021


Use Veo

Tailscale works behind NAT, wireguard does not unless you also have a publicly reachable relay server which introduces its own maintenance headaches and cost.

There's a lot more detail in this reddit post from the author - https://www.reddit.com/r/OpenAI/comments/1q6yw5g/how_we_used...


A compiler is deterministic though.


Does a system being deterministic really matter if it's complex enough you can't predict it? How many stories are there about 'you need to do it in this specific way, and not this other specific way, to get 500x better codegen'?


Have you tried killing plasmashell and restarting it? That way you won't have to close your apps and logout


I don't think it's safe if the track is electrified


Electric trains don't get power via the tracks like that, they use power lines. Metros are a different matter, but that's not what the article is about.


Many UK long distance trains still take power from a third rail for some of all of their journey.

Overhead electrification is a long term goal for the non-Metro UK rail network but it is a long way off.

The other method is an electric train with a diesel generator car.


Interesting, TIL. Trains don't do that where I'm from for obvious safety reasons, but I understand infrastructure everywhere comes with different baggage.


Anywhere with third rail (which is predominantly London and the South-East of England) tends to be fenced off along the sides of the tracks or other things in place to strongly discourage you from walking onto the tracks.

Given that a considerable amount of the UK rail routes date from the late 1800s there are a lot of places where tracks cross roads and therefore mix with other forms of transport (including pedestrians). It's surprising just how little there is in between a pedestrian and a live rail in these situations, here's an example 5 miles or so away from central London: https://maps.app.goo.gl/nPcJM1YxBexaDDKY6

One of those live third rails start less than 5 yards away from where pedestrians regularly walk, with just some angled planks of wood to stop you walking towards them.


That is terrifying, thank you for sharing.


We just take it for granted here in the UK. The number of people who die accidentally on the tracks each year is very low, and much lower than those who choose to commit suicide that way.

There's a strong "stay away from train tracks" education whilst growing up.

Those who grew up in the 70s/80s had the benefit of some utterly horrific public information safety films such as https://player.bfi.org.uk/free/film/watch-the-finishing-line... (well, that one was never used in the end, but it sets the tone...)

More horror here: https://artofthemovies.co.uk/blogs/original-movie-posters/sc...


Metros may have electrified third rail, but the ones next to DB train tracks are all with a top covered third rail. Usualy power deliviery is via catenaries.


There was a study where participants had been consuming 10kiu per day for years without any toxicity.


How did he manage to bypass 2fa?


Most likely victims did not use 2FA.

In the hypothetical that they did and he were a strong hacker, he could possibly cook up a man in the middle attack - victim provides username, password, and 2FA. Man in the middle uses them to login on behalf of the victim, saves a copy of "remember this computer" type cookies, passes it all back to the victim transparently. That would be a lot harder to implement than a basic username/password phishing site however.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: