The attack involves relaying the signal next to the car. Essentially mimicking the key fob being close to the car.

For what I know you can not clone the key, nor can you record the signal and replay it whenever you want access. It's a one time thing to drive away to your nearest chop-shop/hideout.

Adding to this,

My late mid 2014 MBP has the kernal_task heavy write issue. I has written over 15TB the last 61 days. The new nvme disk I installed two months ago is already at 2% wear:

  Available Spare:                    100%
  Available Spare Threshold:          10%
  Percentage Used:                    2%
  Data Units Read:                    45,859,839 [23.4 TB]
  Data Units Written:                 44,541,716 [22.8 TB]
  Host Read Commands:                 296,573,912
  Host Write Commands:                218,840,299
  Controller Busy Time:               6,954
  Power Cycles:                       138
  Power On Hours:                     1,662

A quick Google directed me at:

  - Spotlight indexing packages folders (npm, pip etc). Add those to the "privacy" tab in the spotlight settings to skip indexing.
  - The battery and or logic board may be failing.

Let's hope so. Though the price might be a hurdle.

The price per base station is quite high right now. Estimates range from $500 - $2500 (based on teardown)[1].

1 https://www.reddit.com/r/spacex/comments/kwkep4/tsp_181_star...

Tesla mentioned using iron in the lower end electric vehicles [1]. Though I don't know if that is the safe composition you are mentioning.

[1] https://youtu.be/l6T9xIeZTds?t=4221

Since the article is in Dutch, here's my summary:

The Amsterdam municipality is demanding a startup to stop developing an app that can be used to prevent parking fines.

The app uses a dash cam to detect and notify users of a "scanauto" near their vehicle. These municipality cars use an automated camera system to detect license plates and fine owners who are not paying the parking fees. There is a 5 minute grace period between scanning and the requirement for a person to start paying for parking.

A user may use the notification from the app to start paying the parking fee during this time preventing a fine.

Other resources:

* [Dutch] Company crowd funding page: https://www.parkeerwekker.nl/

How can you tell from the small image?

I clicked through and the ebay link mentions: "Built-in protection circuit PCM for prevent over charging or over discharging."

The second-last pic in the article - there's a couple of 6-pin chips on the board.

While not actively developing infrastructure myself, I've always like the concept presented in the Hystrix package: https://github.com/Netflix/Hystrix

Even though it seems it is no longer maintained, the circuit breakers, fail over modes and all that are well documented.

And I don't know why Hystrix hasn't been adopted by a wide audience yet. It seems like a necessity in the micro service landscape.

I have always preferred the library approach myself, but it seems like people are converging on "sidecar" proxies to connect up their microservices. Istio and Linkerd are the big ones. Istio uses Envoy which you can use without a whole "service mesh" to add things like circuit breaking, load balancing, rate limiting, etc.

I was considering an ask HN on just this. Having an effort from makers and professionals to come up with designs for mechanical ventilators when things get dire.

Now I understand jerry rigging medical devices is not advisable. But a pandemic like this may get to the point where DIY solutions may offer the solution.

I heard from a general practitioner that mechanical ventilators also have fine pressure control. Which would make the whole system a lot more complex. So given that I figured the concept was to flawed. But the design by MIT doesn't have these fancy ventilator function either. So it seems a cheap, available, basic ventilator would still be valuable.

Scrape off rust, replace chips that have been shorted.

Does depend on chips being available and some knowledge on how to diagnose the damages (e.g.: board schematics).

Here's an example of new age Macbook pro's dying from little water ingress (design oversight). And a combination of knowledge and a simple chip can fix your nearly write off Macbook. https://www.youtube.com/watch?v=jahtu1_idVU

Manual work like that should be more expensive than buying new.

I would be very surprised if Rossman charged more for that repair than the cost of a new Macbook.

Apple loves to say that their products are so expensive and complicated that manual repairs just aren't worth doing. But observably, in the real world, even with all of the crap Apple puts in front of repair shops to slow them down, that isn't true. Third-party repairpeople still manage to regularly beat Apple's prices.

"should be"? I can see how it's more expensive now. But I think that as a collective having things repaired is preferred.

For most manufactures the incentives now is to minimize repairability. Increasing the repair cost.

Having some regulation in place to limit repairability prevention may tip the scale a bit towards repairing.

I come across one site every two weeks or so. Luckily on the Reddit forums people usually copy or quote the article.

It's a bit of a nuisance. But overall, I feel this GDPR is doing more good than harm.