skysight-inc/HackerNews huggingface dataset:
Mine was a PEM31DF2WW. The control panel layout looks slightly different but the segment display looks identical to yours.

The board that I replaced is a Midea MD1001LSE EMLAA5G-S3-K VER17. Not an exact match to the OP but in the same family.
There’s absolutely no employment requirement outside of any PR deals that IE may impose on Apple to satisfy their citizens. The tax evasion scheme they used does not necessitate any real humans in any jurisdictions - it’s almost literally just documentation.
Why I always wear my seatbelt in an airplane when on the ground unless it's actually at the gate.
That's a point that far too few people in the remote sensing industry understand!!

Put another way, try measuring the width of small objects in the scene. You'll find there's a minimum width things will appear regardless of how small they actually are. Small, high-contrast objects will be visible, but will be wider than they actually are. Measuring the width of small bright objects is one way of estimating the spatial resolution (i.e. FWHM of the PSF) of optical imagery.

And with that said, those fenceposts are not that thin. They're likely on the order of 10cm. It's widely assumed from regulations/etc that "spy" sats can get below 10cm spatial resolution. In the US, commercial sats are not allowed to collect imagery better than 10cm spatial resolution. At the 10cm resolution point, things like atmospheric lensing due to temperature variations become major issues and need to be corrected for (e.g. that "shimmer" you see above the pavement on a hot day). That type of tech gets tightly regulated very quickly even in the US's current "let private industry image how they want" regulatory environment (used to be more restrictive not long ago).

So that imagery is likely somewhere on the order of 5cm to 10cm resolution in its native form. Which is pretty nuts. It's crazy what the NGA can do!
Not having the outputs tied into the code is actually preferable if the ultimate goal is reproducible science. Code should be code, documentation should be documentation, and outputs should be outputs. Having multiple copies of important code in non-version controlled files is not a good practice. Having documentation dispersed with questionable organization in unsearchable files is not good a practice. Having outputs without run information and timestamps is not a good practice. Its easy to fall in to those traps with Jupyter notebooks. It might speed up initial set up and experimentation, but I've been working academic labs long enough to see the downstream effects.
> MNCs in Europe?

Why would you expect them to pay corporate taxes on all the income they make outside of the US? Would hardly make much sense...
I'll take the out of date comments. They provide a red flag that either the original author was confused, or the behavior changed over time. At least then you can do code archeology to piece together descriptions of what the original intent was, and how it changed using the commit history and figure out where things went off the rails, and thus determine how to actually fix it rather than patch over it even worse.

The problem with unit test as documentation is that over time they end up reflecting the same misconceptions that the code has. Someone does a refactor, misunderstands how the original code works, and "fixes" the unit tests to pass. Now you have tests that lie just like comments can lie.
I wasn't being sarcastic, if that's what you mean. (And I'm not a professional programmer, so my coworkers don't write code.)

To me, the suggestion seems so incredibly bad that it leaves me wondering about the headspace of someone who would suggest that. Is it somehow less bad than it seems?
That was poor wording on my part—I should have used the subjunctive mood and written '… if the latter were objectively superior …'.
I misread you (having been triggered by things other people have been saying about the topic).

My mistake, but it was not intended rhetorically.
For a crossword, which shards pretty trivially, while already having a database team to deal with that side of things? Large orgs move slowly so there are many reasons why you couldn't write something over the weekend and deploy it that quickly, but the challenges at that level are bureaucratic, not technical.
Law enforcement is also about going after whistleblowers, journalists, or, in most countries, just ordinary citizens the current people in power don't like, even if no crime was committed.
You also might find a similar feature arriving in that product.. soon.
Perhaps the company is otherwise all in on Microsoft's ecosystem. Perhaps they use Outlook, Word, Excel and similar apps where the Linux version doesn't exist and the Mac version is an afterthought. So IT forces everyone to have a Windows system, and then give only the developers a separate Linux machine.
> A senior engineer writes comments that explain why the code isn't written in another way.

And C-level engineers write a comment "X hours have been wasted on refactoring this code. Should you decide following the example of your priors, please increment this counter."

Sometimes, even what appears to be an utter hack job actually is the best you're gonna get.
Not really. The idea is to split work into separate stages which are reviewed separately, but as a whole.

In the example: "small refactor 25LOC -> new API 500LOC -> migrate API users 50LOC"

Making a PR of the small refactor will probably garner comments about "why is this necessary".

Opening two PRs at the same time is clutter as GitHub presents them as separate.

As well, sometimes CI won't pass on one of the stages meaning it can't be a separate PR, but it would still be useful in the code review to see it as a separate stage.
I recently listened to this great episode of "This American Life" [1] which talked about this very subject. It was released in June 2023 which might be ancient history in terms of AI. But it discusses whether LLMs are just parrots and is a nice episode intended for general audiences so it is pretty enjoyable. But experts are interviewed so it also seems authoritative.

[1] https://www.thisamericanlife.org/803/greetings-people-of-ear...
Structural deviations drive an uncanny valley of physical places [pdf]
you're ignoring the 20% VAT on those 3bn sales, which provided 600m tax revenue. Why is it so important that they paid 7m in corporate tax instead of any other amount?
Their business apparently has high cost of sales (like stores, personnel etc.), where by the way also taxes occur, e.g. for wages...

So I suggest to think twice if you want to paint the picture that Starbucks does not contribute it's fair share to taxes in the UK.
They never fully committed to ev or they intentionally ignored the development. Otherwise you would see low price Japanese ev flooding the market instead of the Chinese ev
FexEx and UPS receive immunity as carriers in exchange for several things. Minimum standards around recordkeeping and knowing their customers is one. Assisting the government with law enforcement (tracking down customers, scanning packages, etc.) is another.

Juries aren't stupid, they're not going to buy it when the courier says, "I just saw this online ad for deliveries on the dark web. Sure, it paid way more than normal delivery jobs but that's not cause for suspicion, right?"

And that's exactly what a tor node is doing: delivering content from the dark web. As far as I'm concerned, Germany is being very generous in its decision to let these operators continue to operate despite knowing full well that they are enabling criminal activity.
Not the person you are replying to, but I would say that:

- The code 'tells you' what it does

- The comment for the code tells you what the author intended it to do.

The gap between the two is where bugs can be found.
It is my firm belief that everybody should have one of those $10 FX2 boards in their drawer, either for debugging some electronics board stuff (arduino and up), or just for learning about digital signalling. $10 and Pulseview is all you need!
Latex is great in this case, because the equations are all written out clearly.

If you want to understand diffusion, it's a little difficult to avoid math.
Surely not the entire economy, though I’ll generally concede your point… just today I saw two women exchange the output of ones chickens for the output of the other ones knitting needles.
Two ways this is useful:

- It is possible that the airgapped system still has a publicly viewable screen displaying harmless information. But you use this technique to leak secret information from the system.

- If the authors established that 2m is the maximum distance that you can reliably leak information this way, then that is in principle useful information for someone designing the security system. No audio recording software allowed within 2m of the screen!
In this article I learned that _start_ is the equivalent of _open_ (from Mac). I didn’t know _start_ before.
yes, that used to go to newspaper and overhead costs that don’t scale like newspaper

the current structure mandates that other teams have to advocate for themselves, and we’ll find out whats worth what
For those who are using MariaDB in a business context: does this make you more or less likely to choose it for your next project?

I don't know anything about K1, so all I have is confusion (and a sudden urge to switch entirely to postgres).
Why don't lawyers just do this stuff? Then minor legal threats are not a concern.

Alternatively, why don't we become lawyers, too?
I haven't tried Gorilla Tag, but given I can't stand still with the headset on in the Quest lobby I have my reservations.
Maybe, "the time when expected value is the lowest"?

The BC 6/49 lottery (6 balls 1-49, one bonus ball) for example has 53% of the common "prize pool" split amongst all 4-ball matchers, so if you're not hitting the jackpot you get less cash out of a high-demand drawing.

And given the prize pool is something like 18% of net receipts... yeah EV is still well in the negatives.
Not the OP and not the maintainer, but an open core example product that I love (and pay for at some companies) is MUI: https://mui.com/pricing/

They're a React UI framework with many free and some paid components.
I did some work for a place that had 30 year retention requirements for lots of data. (And indefinite for others)

Iirc, the goal was to turnover to new tape media every 8-10 years.
Native bitemporal tables: https://mariadb.com/resources/blog/temporal-tables-part-5/
I bought a bunch of zigbee light switches years ago. A couple of them have failed and I replaced them with dumb switches. For my use case I found I was rarely using them as anything other than dumb switches anyway.
If you are having trouble getting 10TB of disk space from IT, you have bad IT. Not saying that's uncommon or anything, but 10TB fits on one external hard drive for $300 from Best Buy, or less than $1000/mo using EBS on AWS if you need some better guarantees and are all-in on the cloud.
Bruner's "Stand on Zanzibar"from the 60s and "The Shockwave Rider" from the 70s predicted a lot of social trends. Most millennials and younger won't be able to stand them though because of the different cultural norms of those eras embedded into the books
Most of those products are very simple...
You are correct, but this only applies because:

> Unlike the UK, the US levies capital gains tax on proceeds from the sale of a main residence.

I understand why it can feel unfair but by definition this is not "double taxing". The gains on the house were not taxed by the UK which is why he had to pay US taxes.
Hah… I just realised that all of the pieces are now there for a “Windows” distro that uses the Linux kernel instead of the NT kernel.
My reason has been relative simplicity. PostgreSQL comes off as much more complex (though whether that is actually true is probably dependent on what you're doing with it).

I'm also not working with super-high-performance production-critical loads, though, so grain of salt and all that.
Show HN: Forms with OpenPGP
I'm Pal, the creator of an open source form/survey platform. It's written in Rust and Svelte and it's all on GitHub: https://github.com/palform/palform.

My aim is to do something similar to how Proton encrypted emails: keep it simple and user-friendly, so that basically everyone can switch to it from Google/Typeform.

Of course, there's some compromises. You can't really do integrations, since the server doesn't have the raw responses to send anywhere. But there's still tons of use cases where Palform's features suffice.

The encryption is powered by the amazing Sequoia PGP library and simply uses OpenPGP. I know it's not a perfect protocol, but it's been around for ages and audited several times. Users need to be able to trust Palform, and a DIY obscure cryptographic system would make that hard. Plus, this way you can import + export your keys and everything stays interoperable. It even has webhooks, so your servers can store PGP keys and you can decrypt the form responses yourself.
I think I have a solution: countries (governments) could publish lists of forbidden addresses; you could be allowed to safely run you Tor exit node as long as those addresses are blocked. Of course, not ideal, but could make a lot of people more willing to run exit nodes.

It wouldn't fix the "someone used my exit node to send a bomb treat" case though.
Without squashing it's hard for me to commit as small and often as I would like.

Some things I want out of the final series of commits:

1) everything builds. If I need to revert something or roll back a commit, the resulting point of the codebase is valid and functional and has all passing tests.

2) features are logically grouped and consistent - kinda similar to the first, but it's not just that I want the build to pass, I don't want, say, module A to be not yet ready for feature flag X but module B to expect the feature flag to work. In the original article, this is to say that I want the three commits listed, but not one halfway through the "migrate API users" step.

But when I'm developing I do want to commit halfway through steps. I might commit 50 lines of changes that I'm confident in and then try the next 50 lines and decide I want to throw them away and try a different way. I might just want to push a central copy of what I've got at the end of the day in case my laptop breaks overnight (it's rare, but happens!). I might want to push something WIP for a coworker to take an initial look at with no intent of it being ready to land.

But I don't want any of those inconsistent/not-buildable/not-runnable states to be in the permanent history. It fucks with things like git bisect and git blame.
In the blog there's a video of what looks like cars moving around, but the lighting is constantly changing. How does that work?

It looks like a timelapse but then there are cars doing normal car things.

https://www.youtube.com/watch?v=cwDjJqtx_og
A system where the whole populace votes on everything isn't the only kind of democracy. The US is a representative democracy.
A function generally tells you what it does three times: once in the doc comment, once in the function name, and once in the body.
Dude, seriously? You’re acting like Apple was clueless here. This entire controversy is about Ireland and Apple colluding for over a decade to avoid paying corporate taxes anywhere else in the EU. Nobody involved was ignorant of the potential illegality, rather that was deliberately the point.
I have learned to enjoy narrating my struggles in the comments, probably to excess; but it certainly makes it much easier to pick up a task again after I leave it alone for a week or two.

People rarely touch what I write, but if they do, and they want to strip the comments out, thats totally fine with me, just don't ask me how it works after you do :P
They don't know all the data that's being hashed, though. They know everything that's in the map, but not all the keys they're trying to lookup.
> Do you think that defense is going to keep the courier out of prison?

Yes. That happens every day.

> It sounds like Germany is treating Tor operators as common carriers,

That's probably because they basically are common carriers. And the service isn't particularly designed for illegal activity, even it can be useful for that. It's especially not designed for activities that tend to be illegal in the "free world".

> in most countries the node operators are probably not met with such leniency.

The Tor network has been running for about 20 years. There are on the order of thousands of relays. Unlike users, relay operators aren't anonymous; there's a public list of their IP addresses. The relays are all over most of Europe, especially Western Europe, and the Americas, especially the US and Canada, with a not-insignificant number of them in other countries.

So far as I know, nobody's ever been arrested, let alone convicted, for running a Tor relay. If they have, it's been in the sort of country where you also get arrested for running a newspaper. That may change soon, but it's still the case so far. Oh, and a good chunk of the funding for development (but not relay operation) comes from the US government.

You say "leniency", I say "not being an authoritarian hellhole".
Some time after an LLM programs its own successor, without bugs. I won't be holding my breath.
Yes, I can agree that an armed raid or the threat thereof is definitely an undue burden.

> it's clear all you're doing is running software. (Side note: I'm surprised how often attitudes on this site are at odds with the "hacker" part of "Hacker News".)

I do not view software as amoral. It's a tool, and like any tool it is an extension of myself. Software that I run is acting on my behalf, and what my software is designed to do is something that I should be held morally accountable for.

I'm not sure when the hacker ethos came to mean that "just running software" absolved you from having to account for the damage your software causes, but if that's what the hacker ethos is about then yes, you can count me out.
> Parent commenter said Linux shouldn't have <X>

I said no such thing! You've completely missed the point.
That seems like a reasonable way to use jupyter notebooks since you have an actual plan to move beyond it when necessary. My issue is mostly with the way its misused, often by people who are arguably at the top of the field.
For a legacy system originally built on MySQL back before Postgres was so strong.
"Im a scientologist and I dont even know about a bet with Campbell. Nor do I know anybody who read any of Hubbard scifi books"
> or write your own bafflingly complex ORM

Oftentimes, the reason for that is that 20 years ago stuff like Doctrine, Liquibase or whatever just didn't exist. You know, the time when PHP developers shipped straight mysql_query calls with direct interpolation of $_GET, and most "enterprise" Java application came with a ton of SQL scripts and a dedicated multi page UPGRADE file explaining in which order you had to run the schema migrations, reboot systems, run manual migration scripts and whatnot to get an upgrade done. Some times, upgrades could literally take days.

Naturally, people invented their own stuff to make stuff just suck a little bit less, and it got more and more used in a company, only ever extended in functionality... the dreaded "corpname-utils" JAR dependency (if you're really unlucky, the JAR having been semi-restored from a half-broken decompile because the sources got lost along the way) or util.php that just got copied over from project to project. And that's how you end up in 2024, still maintaining some ORM that has its origins in Perl code written in the 90s by someone deceased in the '00s. (Yes, I've been there, although not that bad)
Having the outputs recorded alongside specific versions of the code can actually be very valuable.

But since most uses of Jupyter notebooks I've seen don't version control them much at all, it's not as useful in practice often.
In addition to the flaws that you point out:

1. Putin invaded the first time, even if he hid it behind "little green men". Putin invaded a second time, even though he claimed it was "just training exercises" right up to the moment that Russian troops crossed the border. Why would anyone sane expect that Russia would be satisfied with the "relatively modest" concessions Putin demanded? It would have been another "peace in our time". And just like last time, the time of peace would not have been long.

2. The GP talks about violations of the Minsk Accords, as if only one side was violating them. That is... a very highly biased view of events.
We could have the best of both worlds if comments could be easily hidden, or better yet, just additional meta-data on rich text code. But nope, we can't get away from ascii.
No. That's not true. It does not do that. I've reinstalled Windows 11 several times to resolve issues or try these kinds of things out. It has never offered to download an AMD driver for me. This is false.
I knew someone who ran a Tor exit node from his research lab workstation at Brigham Young University (BYU), a conservative religious school with an extreme institutional phobia of porn. He ended up in a "special interview" with his graduate advisor. I don't know if he fully groked at the time just how close he came to getting expelled.
Scenario: LEOs knock on your door and take everything connected to the internet. Why? Your home was running an exit node. Who? Your 12 year old.

Yeah yeah “parents should know” but given the rash of shootings by young people, fuck that argument.
Now you're just being childish and lazy :)
> That, and the name ("lite").

It's SQLite like a mineral. Pyrite, for instance.

SQL-ite, not SQ-lite.
Hah, this is me :)

Half the time I start by just writing comments explaining what I'm about to try and do, then I go back and add comments about how things did not go as expected, and what I had to do to get it to actually work. Super helpful 5 weeks later when I have to actually see it again.
They’re both great systems but there are a few differences primarily in small ways for most applications:

Maria supports partitioning, Postgres (as of my last knowledge) does not.

Unstructured data is more flexible in Maria natively, but Postgres can support it in a variety of ways.

You can find lists and lists of head to head comparisons out there which will highlight all of the niche differences that each brings over the other.

Ultimately either will work just fine for 99% of use cases.
Yeah that’s how I feel. I feel like the iPhone 7 could handle all the daily use cases just fine. Every phone after is cool but doesn’t accomplish anything
This is almost exactly how I think about it too - a good repeatable mental model is "infinite upside / near-zero downside".

These massively asymmetric choices occur elsewhere in life, e.g. "asking them out on a date"; "asking for a raise", and are good to look out for.
I just got my GPRS radio license and this was a really strange phenomenon to encounter. Apparently the FCC doesn't allow actual encrypted comms in this part of the spectrum, so the "privacy" codes, like you said, are really more just convenience codes, more noise cancelation than anything for privacy or security.

It was weird trying to explain this to my family, too. Basically just had to tell them "Nothing you say is private, and you should all say my call sign at the end of each transmission." We all felt like dorks, but it was super convenient in a place with no cell service.
this is from the guy who said climate change is "mostly beneficial" and has an interview with jordan peterson

lol
Ithkuil to the rescue? https://en.wikipedia.org/wiki/Ithkuil
We’re using gaming GPUs to do this. (Kinda). And the next gen asic like stuff is even more specialised.

Really don’t see why he thinks brute force is going away. I mean human brains have billions of neurons too after all.
I think what you're quickly discovering is that no one is falling for a Russian shill.