AdamJacobMuller

Same here. I (proudly) had my account there banned for posting the AACS key.

Went to reddit and was not unhappy there for many years, but, aside from some targeted subreddits (/r/beagle!) I rarely spend any time on reddit anymore. The new reddit changes just feel user-hostile and they are aggressively pushing users away from old.reddit.com, it feels like a matter of time before they announce that they are killing old reddit.

Perhaps we are getting old but I also find happiness is inversely proportional to my time spent on social media.

I broadly agree with what you're saying, but, that's not the issue here.

They don't even have a dedicated status/outage page, afaik.

The website being down is a more classic problem. The outage probably increased traffic to their website by 1000x if not more and the infrastructure for the website simply couldn't cope.

Good lesson on keeping your status infrastructure simple and on something which is highly scalable.

Having a CDN where the main page of their site was 99% cached globally would have probably mitigated this issue.

There also must be some seriously robust out-of-band systems in place here.

I volunteer.

I wonder what they do for out of band on satellites.

It's not like you can have a tech go out and reboot it or reinstall windows.

I just started doing this with my car, mostly to add a camera/temp monitoring for when I leave my dog in the kennel in the car (she's well watched over, please don't fret over it).

I'm hooking it up via starlink specifically so it works in remote areas with no cell coverage too.

Monitoring and proxying everything via an RPI as well. Victron DC-DC inverter to keep the bluetti battery pack charged with bluetooth relay boards so we can turn loads (camera/starlink/others) on/off programmatically (it only turns the starlink on when there's no good/known wifi for example).

Fun project, combines software dev (which I'm fairly good at) with hardware work (which I'm less) and my dogs (which I'm a big fan of).

Perhaps plausible until you mention that they hired a team to build it.

There's no way, even if it was a single-digit number of people team that they would remain silent. If it was just Elon/Thiel I could perhaps believe it.

Also keep in mind that there were some very desperate years for Elon where his companies were extremely close to bankruptcy, wouldn't he have tapped into that bitcoin if he had access to it?

Google. https://status.cloud.google.com/regional/americas

In fairness a good number of them seem to live in Alaska or other places where solar is effectively pointless and totally useless for months of the year.

> mountain hermits, rednecks

These guys love their off-grid and solar and batteries tbh.

At this point I wonder if the environmental impact from a lithium battery fire would eclipse the impact from a worst case scenario at a modern nuclear power plant.

There is far far more in terms of containment in the nuke plant, but, the stuff inside is much more dangerous and longer lasting.

I would perhaps argue that juniper's behavior is the preferable one.

Remember the definition of this "drop the message I think is broken" not inherently "drop the broken message," it's entirely plausible that the message is fine but you have a bug which makes you THINK it's a broken message.

There is also a huge difference between considering it a broken message and a broken session, which is what Arista did.

Diminishing returns at some point, but, I think the counterpoint to this is companies who are doing a single huge manual deployment every month (or less) which is scheduled into a 4-hour outage window where many if not all services will be down for this period.

I do agree there isn't a lot of delta between a company doing 2 or 10 deploys a day and a company doing 1,200, but, there's a huge engineering gap between companies who do approximately .03 deploys per day and those doing multiple.

Just pick better brands for your receiver.

I have an Anthem pre and an LG TV, both of which are blocked from accessing the internet, and I have none of these issues.

> Tens of thousands protested around her office

Germany has a population of 84 million people. 10,000 should not be able to dictate a policy decision of this magnitude, regardless of how loud they are.

> Nuclear is complicated (and mostly fear driven)

The politics of nuclear are complicated, the science (more engineering) of nuclear are complicated, the imperative is clear and simple. You are correct that it's mostly fear driven, but stoked by "green" advocacy organizations and/or manipulated by people with a stake in the continued use of fossil fuels (and largely the latter funding the former).

True leadership would stand up to both of these pressures, making people understand that the voice of 10,000 (or even 100,000) people can not dictate policy alone and educating people on the reality of nuclear power, while also fixing some of the real issues with nuclear power (an aging power plant fleet and an inability economically build better replacements).

Merkel totally flopped on energy policy.

> We will provide a preliminary report on or before 2025-04-21.

Bunch of engineers just got their easter weekend ruined. Sucks.

Maybe?

I wouldn't assume that the bug doesn't bypass CAA checking.

Very important question to answer.

Sure, gmail.com might be excluded, but its still a massive hole for a few reasons.

This would affect ANY email provider who offers public email addresses. While I agree gmail.com is probably excluded (and maybe this doesn't bypass CAA -- maybe it does) there's a whole additional surface of anyone who has an email at any big enterprise getting a certificate for their domain.

Even if I work at google.com, therefore have a google.com email, I should absolutely not be able to get a certificate for google.com just by getting an email at that company.

I doubt it's even /that hard/ to buy an email account at a big company like that in the underground world, it seems like they are valuable generally and any company with 200k employees is going to have some leaks. This massively increases the attack surface of a simple leaked email account (which might otherwise have very little or no access).

Crazy crazy oversight that has huge implications and is so easy to carry out that I would not be surprised if this was actually exploited by bad actors.

Probably should hire more than 1 IT person, and, don't skimp on the generators and battery backups for the electric fences.

I'm not sure why "WAF has false positives" makes it useless, nor would I say this is anywhere near the scale of "breaking the internet" and I'm not even fan of the concept of WAFs in general.

There are wireless options which operate in the 900mhz or lower bands, depending on what your use case is.

433Mhz LORA, for example.

> It seems like an unnecessarily ambiguous term.

Agree, and, I don't even understand why it's in there in the first place (it should just not be) but that's a job for the legislature to resolve, not the courts.

Understood. I mention that distinction only because I find many people (not you) who say that "X law doesn't apply because if it did, it would be bad" vs directing your ire at the actual laws, which are poorly written and the legislators who are negligent in fixing those laws.

Courts should decide based on the law, not based on what is "good".

> And I don't think I disagree with the court on schema vs. file layouts either.

I disagree that the law should prohibit disclosing "file layouts" but it's pretty clear that the law does block that, and I fundamentally agree with you that schemas are directly analogous to file layouts and thus restricted.

There are no details because nobody can find the monkey. It's now a cloud of ash.

They might be able to, but, if they are effectively saying "our product is broken and you can't use it until you do X" they could be responsible for massive contractual liabilities.

Very contrary to my experience.

I've been using InReach and the InReach APIs for a few years now.

They were both very reasonably priced (they cost nothing above my InReach subscription price), very easy to get access to (I emailed them and got access to API docs and the APIs within a day or three) and extremely well thought out and reliable (very robust callback based event/point reporting system, with retries on their side if your code breaks or is flakey, their web page has a great debug interface to see what happens if your webhook fails) and their support was top-notch (if not super fast).

I had a weird bug with their webhooks when I started implementation, where every event would come in twice, once with the timestamp of the event truncated to an integer of whole seconds. You could see from the user-agent that the one with the truncated timestamp was a few versions older of their software. Wrapped that analysis up in an email to them and about 12 hours later saw it get fixed and about 12 hours after that got an email back from AN ACTUAL ENGINEER who thanked me for the description, explained why and how it happened and explained their fix.

Granted, the InReach and definitely the InReach Professional API, are more of a professional product and less pure consumer, but, Garmin definitely knows how to do this.

Developing a cheaper to produce product, even if that was done off-book and you could keep it secret, would need some level of different production methods (different ingredients, different machines or something which makes it cheaper) and some amount of testing which just selling the original product doesn't require.

Why?