skrtskrt

You only need the Native Americans, the US share of transatlantic slave trade, Bangladesh, Indonesia, and Iraq for the US to be well clear of the Nazis.

This doesn’t even touch the Guatemalan genocide, US backing of the Rwandan genocide perpetrators, the white terror, Pinochet, the Khmer Rouge, Afghanistan, or Israel.

How about the US massacring more civilians around the world than any empire since Ghengis Khan?

They must have machines that are not app-enabled right?

I sort of understand why their consumer machines would have that crap but I imagine that plenty of commercial places buying a $20k+ machine for a cafe that's supposed to run for 40 years would not accept having an app involved in maintenance.

Wrong again. Not only have I worked on DigitalOcean’s S3 implementation but I currently work on an open source product that targets S3 spec and can be used with any cloud provider and any other spec-compliant drop-in, like Garage.

It's not new that push notifications should be presumed to be insecure, with their content passing through - and probably persisted - outside the app sandbox and anything in control of in-app encryption.

Apple should have fixed this long ago (not that you can trust a closed system), but Signal should also have strong guardrails & warnings around allowing message content in push notifications.

That's because "progressive" urban politics is generally not progressive at all and dominated by the upper middle those that benefit or think they benefits from squeezing the working class out of their neighborhoods.

California also passed a ton of laws that effectively upzoned the state in various ways. Minnesota did the same thing a few years back.

This seems like the only real path - you cannot beat out these skeezy local homeowners and landlords at the corrupt local politics game. You need statewide politicians who have political ambitions to build off of solving these problems.

You’re wrong. “Implementing the S3 API” means the spec, not an Amazon product.

Red Boat fish sauce, Lee Kum Kee Oyster Sauce, and Pearl River Bridge light soy sauce - all standard stuff. I use just a little ground pork for that flavor, and I’ve found a little chicken stock and dash of white pepper really help as well

I think in many dishes you can add quite a lot, but it blends and cooks in with other ingredients so that the "fish sauce flavor" does not jump out as such.

I make mapo tofu with 1 tsp each of fish sauce, oyster sauce and light soy sauce. I don't think anyone would think it tastes like fish or oyster sauce in any way, but it doesn't taste right at all without them. The same goes for many other dishes.

There's a difference between S3 API spec and what Amazon does with S3 - for isntance, the new CAS capabilities with Amazon are not part of the spec.

Ceph certainly implements the full API spec, though it may lag behind some changes. It's mostly a question of engineering time available to the projects to keep up with changes.

Yeah I do not think there are any serious transit advocates that put time into advocating for e-scooters. They are worse and more dangerous than bikes and e-bikes in every possible way.

And any bike lane infrastructure would benefit e-scooters anyway, so riding them in the road at 30mph below the flow of traffic is a sad hill to die on.

I assumed comment is referring to people that advocate for transit as “anti-personal mobility”, they are counting cars as the only “personal mobility” which is beyond laughable.

It already exists, it’s their Bring Your Own Cloud offering.

It’s to retain customers that grew big enough on Grafana Cloud to justify having their own in-house team run the tools instead. So Grafana offers them a pricing where the Grafana engineers operate the platform within the customer’s cloud account. Very large customers get to keep not having to operate and build/hire for the expertise, and save some money.

Sure some companies are big enough to make it worth it and still want to run their own OSS observability stack, but it’s generally not going to be popular with executive decision-makers, so it likely will remain rare. And if they do run it, Grafana still benefits from their contributions to AGPL code.

On the low-spending end, OSS users not buying cloud would not really be a serious revenue concern. They just don’t spend enough. You use cloud if tou have super broad product usage, so you don’t have to run and maintain Grafana, Mimir, Loki, Tempo, Pyroscope, k6, etc. all yourself. If you don’t want or need all that, you run Loki+Grafana yourself and enjoy.

“Anti-personal mobility” is beyond absurd, absolute loony-bin stuff.

“Anti-personal mobility advocates” do not exist. Transit advocates exist, and improvements in transit also massively benefit those who need to or prefer to drive.

At this point S3 is an API spec more than a particular system. Plenty of things only work against the S3 API spec since the implementations have become such popular and relatively cheap and performant storage systems. It gives a nice limited surface area that doesn't allow you to do things that can get too complex or can vary too much across filesystems, etc.

You must be lost.

AI as advanced fuzz-testing is ridiculously helpful though - hardly any bug you can in this sort of advanced system is a specification logic bug. It's low-level security-based stuff, finding ways to DDOS a local process, or work around OS-level security restrictions, etc.

Yeah I would certainly only recommend a hotswap model, even if someone isn't into keyswitches that much, they still probably have a preferred feel that they want to go for.

A Keychron has always been a great introduction for friends that want a good home desk setup without too much fuss.

I have stuck with the System76 Launch keyboard but I basically always consider Keychron first when looking.

AGPLv3 includes that “distribution” includes essentially communicating with the service over the network, as opposed to the GPL concept of like, sending a shrink wrapped binary that someone downloads and runs themselves.

So basically they are worried that they have no way of avoiding one or more of their tens of thousands of engineers “distributing” it to customers by including it in some sort of publicly accessible service. AFAIK there’s no settled case regarding what level of network communication qualifies - like if I run a CRUD app on Postgres and Postgres was AGPL, am I distributing Postgres?

Now the second part is that you only have to give out your changes to the AGPL software to those that it was “distributed” to. Most people aren’t changing it! If anything they’re just running a control plane in front of it…

but it goes back to the corporate legal perspective of “better safe than sorry” - we can’t guarantee that one of our engineers, isn’t changing it in some way that would expose company internals, then triggering a condition where they have to distribute those private changes publicly.

In reality most $Evilcorp have policies against AGPLv3, which is why projects can make moneh selling a less-restricted enterprise license for the same code.

Does not seem like they specified whether it was browser or desktop teams, but either way it asked him to install an actual system package which you should never do anyway.

The relevant part is:

* they scheduled a meeting with me to connect. the meeting was on ms teams. the meeting had what seemed to be a group of people that were involved.

* the meeting said something on my system was out of date. i installed the missing item as i presumed it was something to do with teams, and this was the RAT.

While this is somewhat true, the point of being a registered carrier is that most countries regulate that registered carriers must peer with each other at much lower costs. It is nearly-impossible to get "direct routes" everywhere, mostly because of the logistics of signing all those agreements.

But you will generally be much better off with an actual registered carrier because they have better access to direct agreements with regulated pricing.

nope!

As a general rule I install none of these web conferencing things on my machine. Either the browser version works fine, as Google Meet, Zoom, Teams and even WebEx all do, or this is not a meeting I need to be on.

Starting with > Twilio charges around $0.05–0.06 per SMS round-trip

Well - use an dedicated telecom API provider that doesn't squeeze you on pricing uselessly: https://telnyx.com/pricing/messaging

Twilio is the DataDog / Microsoft of telecom APIs. The only reason you buy them is because it's the biggest name, or you have already integrated them so deeply that you're unwilling to rip it out. Their price structure also has a huge floor because they're not a carrier so they have to buy everything from real carriers.

Telnyx is actually a registered carrier so other carriers are forced by law to peer with them at lower prices.

There are other low-cost SMS API providers but AFAIK none are actual carriers and they maintain the cost by only doing messaging and relying on enormous volume to make up for tiny margins - their profitability and therefore longevity are tenuous IMO.

Prometheus index format is also a big-endian binary file - haven’t found any reference to why it was chosen.

grid-scale batteries are accelerating more rapidly than anyone thought a few years, it’s not really seen as an unsolvable problem anymore

Every major high-throughput database now runs as microservices, not sure why people still act like things just grind to a halt when the network is involved.