adql

Did the author of the feature missed Perl or something ?

Perl does that with few thing, like regexp captures. It's kinda sorta neat for writing shell oneliners but that's about it. But then concise and intelligent design wasn't ever Ruby's forte.

I'm sure that someone running around city as a pac-man have plenty of free time, job or no job

Keeping multi month ones secret is even bigger risk to security if workarounds exist.

Yeah, you'd have to actually do your fucking job.

It's not up to one that did the fuck up to decide when people affected by the fuckup gets to know it happened.

If vulnerability is actively exploited (and not just some theoretical) then it should be entirely fair that government gets to know it as the government might be one being attacked by it unknowingly.

It's not disclosing it to public. It's making the companies disclose it to:

* their actual users

* the government

You know, the government that a ton of info about every citizen ? Yeah they should probably know.

It seems like "security experts" are really PR experts that don't want their big company to not be able to control the information about the vulnerabilities

If it can be controlled via RS485 you might be able to add some smarts to it, like lowering charge level if weather is supposed to be good next few days.

There are but you just won't be able to use all that water if you have more than a few panels.

Like if you need enough water for shower you might just need heat of like... one or two solar panel sized heaters, anything extra means water will be permanently hot and so any benefits from cooling would be minimal unless you had some heat dump to pump the excess heat out. So more cost

There is probably some use for heating house in the spring/autumn, but system that can put the heat from panels either to heat the water or heat the house is additional extra complexity and cost.

>Something I remember is that MP3 spends a disproportionate amount of storage in order to encode frequencies > 16 Khz. This may explain why in some tests, it performs worse in mid-high bitrates (160/192 Kbps), although I don't know the technical details.

I wonder if just straight out filtering them would result in better 160Kbps MP3s, it's not like most people can hear them...

> OPUS with the voip profile and fit tons of content to listen to offline on whatever a humble storage your portable device has left.

I'm glad you're saving that old 64MB player from landfill but the size of podcasts isn't a problem from even budget phone perspective.

I think you're spot on, there just needs to be enough demand for manufacturers to compete on it.

But the fragmentation does work against it. If some company does it it would be limited to their camera app and their format.

Would be interesting if some company just decided to put c-mount on their phone so you could use actual proper lens...

See but you don't necessarily want full range logarithmic.

If your darkest pixel is halfway down the ADC range, on linear you're throwing away one bit, on logarithmic you're throwing out way more bits. Just using higher bit linear ADC then converting it to logarithmic in post-processing seems more sensible. Hell you could even go signal magic and merge few photos with different shutter speed together to get most detail.

Also proper log-to-in converter like AD8307 costs like $20 so I'd assume doing that woudl bring the sensor price way up if you needed to have a bunch of them.

And the light. Good lighting can compensate for not so great sensor

> I just want an IPv4/IPv6 proxy that does nothing other than delay, rate-limit, and/or drop packets.

Built-in into linux kernel, althought it's per interface unless you get dirty with traffic shaping tools.

Also you probably dont want proxy as support for proxy servers can be pretty iffy across software stack.

> Your loopback adapter has a latency of 30 microseconds, but that same web-to-database connection might traverse multiple switches, routers, firewalls, and load balancers and have a latency of over 1,000 microseconds (1ms) in production. That's thirty times worse, and I'm not even talking about zone-redundant deployments, regional-to-region failover, or any such thing!

Reminds me of a time when COVID hit and the suddenly-remote developers were suprised the time to start of their application went from 5 to 30 minutes (they connected their app to DB server on dev environment to not carry big-ass database with them)...

> Ditto with web apps, where every developer mistakenly believes that their Angular or React monstrosity is "performant"... because it is... on their own machine. With loopback networking. Try that over a 3G connection... in rural India. Not Indiana. India.

And that reminds me of this time frontend developers loading 700MB of data to load the site and not noticing that, but sending ticket to ops "server is a bit slow, could you give it more cores?". Said developers were working in office that had direct connection to data center 500m away with sub-ms latency and plenty of bandwidth.

I had many times pondered traffic shaping frontend devs connection to like 10Mbit after that... maybe 56kbit for repeat offenders.

...okay ? What's the use case where data shrinks ?

The data that will be "not removed" will just be used by new data.

Only real use case is "we've loaded way too many data, removed it, and want to recover that space because we will never need it", and that is not enough to matter, as usually database have its own filesystem and most filesystems can't be shrunk online so any shrinking needs downtime

I feel you're looking at twitter from 5-10 years ago and pretend it was exactly like that pre-Elon.

Twitter months pre-Elon was pretty hard on steering the public discussion away from things Twitter didn't want

I don't think you need to explain to people here what batteries do...

> 1 thing I found lacking: discussion of optimal power point tracking. If ignored (PV panel -> load directly) then depending on the load's characteristics, it can pull the solar panel into very sub-optimal power generation.

The discussion: Buy MPPT controller

End of discussion

> That is an advantage of heaving batteries in the system: they can serve as a predictable / constant load, which a charge controller uses to have the solar panel operate at near-maximum output.

Well the single disadvantage of batteries is cost, everything else is an advantage so there is not much else to discuss here too.

Safety-wise it's better option.

Breaking vs just rolling without working brakes.

And I really do not like trend of making brakes drive-by-wire instead of mechanical just to (presumably) save few pennies...

Microgrids are probably too small (we want economies of scale here), but it would make a whole lot of sense to move some of the storage near the generation when more and more energy gets shifted to solar.

Something like a big battery pack at every substation to handle the local loads when solar is down and help with peaks

> Probably not worth it and I'd expect 3 days to be overkill. But a community that was double our size will have a cost of about 25k per unit for 1.5 days of power - which doesn't sound too bad to me.

If you're not looking to go completely off-grid, I think you want to double it again. At basic level, battery pack is there to soak solar power during a day and give it off when the solar is down.

16 hours is enough to cover most or all of that..

I think the model could work if the local community basically "sold" the battery storage capacity to the users.

Pay few cents for kWh to store it for 24 hours, anything in excess can be sold back to residents at slightly lower than market price, producing some money for maintenance and upgrades.

adding NVMe emulated storage would be one

...the use case of "our architecture's idiotic limitations made it hit hypervisor limitations" ?

Same thing was said about Spectre-like bugs

As you do when you connect to any website ?

Do you know how DNS works ?

You as for a record, you get answer. You ask for IP adddress of archive.today, you get that IP

Then you connect to that IP

If your DNS doesn't leak client IP, the browser connecting to server IP will leak it.

It's entirely irrelevant protection that does nothing but makes competing on cdn harder.

It's entirely smokescreen. Yes your DNS doesn't "leak" your IP... but server will immediately get the IP of the client on first try of connecting it.

User will navigate to the site and show their own IP anyway. You achieved basically zero increase in privacy while making any competitor have problems with any of their users that use 1.1.1.1

And any malicious client that tries to leak data via DNS can just ask for DNS record like my-ip-is-7.8.9.0.example.com and completely go around that privacy "enhancement".

Sorry but the "privacy" here looks like smokescreen to stifle competition.

Right but then working slow looks like archive.is issue but is ultimately caused by cloudflare.

CF is bascically saying "we can know your IP but not the site you are trying to resolve" (that will know your IP anyway once you navigate there).

ZFS people can just change license that was explicity written to be GPL hostile to something non-retarded

Sure buddy, see ya monday