sciurus

For background on this, see https://arstechnica.com/tech-policy/2019/12/justices-debate-...

If you're intrigued by tracking satellites and their transmissions more generally, check out https://satnogs.org/

This is neat.

https://www.duckbillgroup.com/aws-super-simple-storage-calcu... is a way to show "how much more expensive is X than S3"?

Actually, it is still true. Electroloysis split up Firefox into multiple processes, but not every site gets its own process. Work is underway to change this and achieve full site isolation in https://wiki.mozilla.org/Project_Fission.

(Disclosure: I work for Mozilla, but not on this)

In contrast, in the Atlanta and Nashville focused tech slack teams I'm a part of almost every day I see more developers announcing they've been laid off. My last two employers have had massive layoffs that included developers.

My previous two employers, Lonely Planet and Eventbrite.

https://www.protocol.com/eventbrite-major-layoffs-coronaviru...

https://www.booksandpublishing.com.au/articles/2020/04/09/14...

I think this criticism is misdirected.

First, you mentioned memcached, but the article doesn't cover that at all. Perhaps you meant to say elasticache?

Second, I think the closing section at https://docs.keydb.dev/blog/2020/04/15/blog-post/#how-are-ke... does a reasonable job of answering the "fundamental differences of each technology and the trade offs". If it's not more in depth, that's mostly because it's comparing Redis with two forks of the codebase that haven't diverged that much.

This is why Eventbrite has stopped issuing advanced payouts to venues. Given the increased risk, they need to keep the money on hand for potential refunds. I wonder if Ticketmaster has done something similar.

https://www.eventbrite.com/blog/advanced-payouts-changes-rel...

One thing that gives me some confidence in NextDNS is that they have joined Mozilla's Trusted Recursive Resolver program.

Choosing it within Firefox's setting won't enable any of the filtering the article mentions, though. You need a custom config for that.

https://blog.mozilla.org/blog/2019/12/17/firefox-announces-n...

https://wiki.mozilla.org/Security/DOH-resolver-policy

This is generally harder to pull off though unless you do things like force all DB access to go through stored procedures.

And then you're really still pursuing the same strategy described above, except for your stored procedures instead of your app code.

Please provide a way for people to reach you without commenting here.

Just take an hour to watch the 2014 SRECon keynote from Ben Treynor.

https://www.usenix.org/conference/srecon14/technical-session...

I think postfix would perform horrifically on EFS, which has absymal latency and is terrible for workloads with lots of random i/o.

Although the initial public notice of an issue can take longer than I'd like, I don't think GCP hides or downplays their incidents the same way AWS does.

https://status.cloud.google.com/summary has 20 entries for March.

Loadhttps://console.cloud.google.com/support/cases;tab=knownissu... and look at the known issues tab there. This is updated much faster than the public status page.

As I've heard that joke, it's the engineer who suggests measuring displacement and the physicist who wants to assume the cow is a sphere. The joke is that physicist's models oversimplify reality.

https://en.m.wikipedia.org/wiki/Spherical_cow

Big drops in ad revenue are affecting companies big and small.

https://www.vox.com/recode/2020/3/24/21192311/coronavirus-pa...

Thanos doesn't have production support for local storage either. The only stable storage providers for it are google, amazon, and azure's object stores.

https://thanos.io/storage.md/

Interestingly, it looks like Cortex's support for local storage and object stores comes from using Thanos's storage engine. So once it's production ready in Thanos it will probably be production-ready in Cortex shortly thereafter.

https://cortexmetrics.io/docs/operations/blocks-storage/

I think for Cortex your safest storage options now are Bigtable, DynamoDB, or Cassandra.

This is an evaluation of performance on bands used for satellite communications, i.e. VHF and above.

If anyone is looking for an SDR primarily for HF and below, I think the Airspy HF+ Discovery is considered the best affordable option right now. If you want a good general-coverage SDR, I'd recommend one of the SDRplay products like the one they reviewed or the cheaper RSP1A.

LISA.

https://www.usenix.org/conferences/byname/5

But is that caused by contention between netflix traffic and your online classes providers traffic, or is it just a capacity issue with your online classes provider's infrastructure?

My employer, Mozilla, is reimbursing employees up to $1,000 towards equipment for working from home [0], childcare, etc. The guidance has been for employees to be reasonable and for those approving expenses to be flexible.

[0] The roughly half of the company that works from home already got to expense setting up their home office when they were hired, so this mainly helps the people who were working from a company office.

Another directory of receivers, all based on the KiwiSDR Wide-band SDR + GPS cape for the BeagleBone Black, is

http://rx.linkfanel.net/ (map version)

http://kiwisdr.com/public/ (list version)

That matches up with the mid to senior range you'll see for FAANG at https://www.levels.fyi/

It was a detection system, but it operated on frequencies that already in use by shortwave broadcast stations (much more prevalent then than now), amateur radio operators, etc and interfered with them.

You can get more details on how it and similar systems work at https://en.m.wikipedia.org/wiki/Over-the-horizon_radar

What errors are you seeing? Perhaps your IT department is the cause. The certs look fine.

https://www.ssllabs.com/ssltest/analyze.html?d=www.donttouch...

https://www.ssllabs.com/ssltest/analyze.html?d=lzdmsmujepoc2...

Is this intended to become AWS's version of GCP's Container-Optimized OS?

https://cloud.google.com/container-optimized-os

How often do you have data that is

1) important enough to display on a dashboard 2) not important enough to record so you can track it over time

?

Yes, I follow Android's prompt to report the crashes.

I don't see them listed in about:crashes though, so I'm unsure how to follow up about them.

Right. I'm saying the library should set a default timeout by default, which you could then change if needed.

Of course, whatever it chose would inevitably be wrong for many scenarios, it would be less wrong than defaulting to waiting forever.