skysight-inc/HackerNews huggingface dataset:
That's very unfair. The education was free for all, there was significant investment in education, 90% of schools in my rather ancient city were built during Soviet time, not before, not after. Same for university campuses and hospitals. That systemic investment into education along with state-wide industrialisation eventually paid-off. There were wide-spread programs how for example factory worker can get a higher education while still being able to provide for his family.

Invest in a small elite and let the rest starve was more of a motto of Russian Empire, where most of people couldn't read, yet there were some technological achievements nevertheless.
I can’t speak for all companies but at the place I worked at, there was a monorepo. You’d create a small, self contained change off the main branch and put it up for review. All such proposed changes would have tests run on them, so the reviewer could get a sense of the quality of changes. “Looks good, please fix that test” was a comment I’ve seen more than once. After approval, it’ll land on main and be in prod within an hour or two.

For larger features, these changes could be stacked in a list. After each change in the list had been approved, they’d be landed on main as an all or nothing.
My question was rhetorically stylized. I meant the best way between two opposing alternatives, i.e., between suppressing and embracing these technologies as tools in any of those fields you mention.
Logos, drawn from memory by regular people
Pretty amazing that this is what gets downvoted in this site.
In general, bypassing electronic keys is in no way harder than picking locks, it's just a different skill set.

Here are some common bypass methods that work on many real world electronic locks deployed in the wild.

https://www.youtube.com/watch?v=gbn3JtoFdPg

https://www.youtube.com/watch?v=KHvfwpnPwwU

https://www.youtube.com/watch?v=hQTz1OmmHYo
Some detail..

Alert (AA21-265A)
Conti Ransomware

https://us-cert.cisa.gov/ncas/alerts/aa21-265a
Why? Colder-than-average winter last year, warmer-than-average summer this year. Demand is holding steady, or even increasing, and Texas shut down supply during their freeze. https://www.msn.com/en-us/money/markets/why-the-natural-gas-...
For TLS we've had to drag everybody along, kicking and screaming. You call this "widespread and unprecedented success" but the reality is that later this week you're going to see even more outrage and despair from people who didn't like being centralized and so, of course, they're screwed because the price of their "freedom" is the eternal vigilance they couldn't be bothered with.

draft-moriarty-tls-oldversions-diediedie (now RFC 8996) only exists because of this. Moxie doesn't need to worry about security problems with a protocol he shipped last century but for TLS we had to actually document that people should stop using that - because of course they are anyway.

In the Web PKI we have in practice even more centralization, in principle it would be possible to operate a public CA that simply isn't trusted by Mozilla, Apple, Microsoft or Google, but in practice you need all of them to have a viable service. The de facto situation is that you need logging with Google (and any other service, but Google is mandatory) and you need a sign-off from Mozilla, or you are dead in the water.

Now, I think the Web PKI is arguably the only global PKI with something approaching public oversight and it's a huge success. But it's not decentralized in the way you mean, not at all.
In the case of late Soviet Union, one should not discount their inept economics: they've seriously tried to stop inflation at 0% and never increase prices despite growing incomes.

It has eventually lead to more and more goods' production stop being profitable and require subsidies. Which are then bound to have quotes.

It's not an easy task of planning anything where your populace wants both cars and shoes, but you have budget for only one item and have to choose.

Bloated defence budgets and large foreign-help funds did not help, sure.
Keep going, next sentence from JSON.org: "It is easy for humans to read and write. It is easy for machines to parse and generate. "

Non-quoted keys is easier to read and write by humans, trailing commas are easier for a machine to write, single quotes can make it easier for a human to read or write. Comments help humans read and write.

I remember when it was javascript object notation and that stuff was allowed because thats what javascript allows and felt simple and effective for both human and machine, then it became strict json, what a step backwards.
Leo Editor is a very twisted project. On one side it has very useful ideas, a small but vibrant community, and a very active development...and on the other side it's one of the most user-hostile projects I've ever seen. Not on purpose, though, but purely because of how the project works and grows. There is no dedication to polish it for users, or polish anything at all. There is always an urge to go after the newest hype of the week and wreaking the app with all kind of half-finished garbage.

I've used Leo since around 2015, at which the project was 18 years old, not sure how old the actual implementation was at that point. But the interesting part even back then was how few in this app actually worked, and how many errors it had. The amount of data loss I had in the beginning was interesting. Notable are also all the "creative" poor solutions for certain features. And till this day I will never understand why the file-menu does not follow the established culture, and instead is all according to "gut-feelings".

That said, it has become a bit better in the last years, at least the data losses have been mostly fixed, and some creative solutions have been improved. But I've seen in the 5 years I used Leo many new people coming and going, and I don't think that will ever change. The project itself is much its own greatest obstacle for success, IMHO.
I have a physical copy of this with 5.25" floppies and everything. It's one of my prized possessions :D
How much does that matter to us?

Who's going to sue the rest of the developers who keep working on the open version we'd rather use?
That's not a good heuristic IMO; it boils down to evaluating every item in terms of what a toddler could do with it. There are situations in which it makes sense, but you can't build a civilization like that. The correct way is to keep toddlers / "least senior developers" away from powerful/dangerous things, until they grow up to the point they can be taught to use them responsibly.
Besides the base rate effect did you not see the article already posted in this thread with the many problems with that paper?

https://www.theregister.com/2019/03/05/ai_gaydar/
It's going to be highly non-trivial when most of your supply chain (any item maker in the world) is not on the same plan, but instead offers wares at market rate.
Please see my answer above. I really hope it makes you reconsider that opinion. Most of us are just regular Joe’s looking to make a good life and have an impact.
Yes, probably. Closing many reactors has been decided and close dates have been set, but so far few have been closed. And there's enough other pipeline capacity, technically speaking, except that the British probably disagree. But limited capacity into Britain does not cause a global problem.
Uh neither of those even suggest what it does while Tesla's says it does something it doesn't do
Using the size to trigger compression vs no-op is clever, but doesn't help when you have different compression methods that you want to use.

For example, you be using this as an archive format for a game, and you may want to store the texture data using a different compression method than the ai scripts or the audio data. At that point, you definitely need another piece of data to clue you in. A tag field is useful then, though I've also seen filename/file extension-based methods as well.
Oh some people would have problems with that, not every adult looks like one and stuff.
Putting diplomatic pressure to stop relying on Russian gas, after Russia invaded a neighbor, is not sabotage.
Show HN: Segment and Clean Data cheaper & Faster with our no-code Platform
Denanse is a no-code Cloud Data Science platform that allows businesses and organizations to understand patterns in their data or find irregularities and clean their data by leveraging machine learning to segment, gain insights on customer or service delivery across a multitude of service points, cheaper, faster and easier in minutes instead of months

Request a Demo today at www.denanse.com
Thanks! There are several techniques that can be combined to ensure no tracking takes place (not ready to share all the details yet), so technologically it's feasible. Forcing publishers to give back funds would probably be difficult, but it would be possible to halt paying out of new funds for websites that violate the terms.

In general the idea is to take a cooperative approach though, publishers need a strong monetary incentive to not track users. I'm thinking about other ways to help publishers monetize websites in a privacy-friendly way, advertisements (without tracking of specific users and without retargeting etc.) would be another option but I'd prefer to find different solution. I know that this won't work for every publisher, but we need to start somewhere.
> UK National Space Strategy

Please be a Space Force
it is supposed to be blank, its that way on my physical copy
Suppose you are at some node. Here are two questions you might ask:

1. How did I get here?
2. Where will I go next?

In the first program, those questions are pretty easy to answer. Node D has two entry points and node A has two exit points, and in all other cases there is only one possible answer. If you are at nodes B or C, you know exactly how you got there and exactly where you will go next. If you are at node A, you just came from D, and if you are at node D then you will go to node A next.

But in the second program, three of the four nodes have both two entry points and two exit points. If you are at node C, how did you get there? You could have gone the A-B-D-C route, or you could have come directly from A. And where will you go next? Maybe you will go to A, or maybe you will go to D, and from there...possibly back to C? Or maybe on to A.

The difficulty in answering these basic questions is what makes the second program spaghetti.
Telling Alice and Bob apart visually because of their individual facial features, and possibly using that to uniquely identify them, is one thing.

Being convinced you can deduce Bob's character traits e.g. determine that Bob must have criminal tendencies based on the shape of his nose, is something very different.

This paper is about the later. About people doing CS research becoming convinced the later is possible, because their statistics dousing rod has found a correlation in their data set. And the very bad consequences that can follow from this.

You might want to at least read the abstract of the paper.
This is what cryptocurrencies are good for: Protecting and helping the absolute worst of humanity.
Pigeon-guided missiles (2010)
> I detest it so much that sometimes it makes me wonder if I even want to continue in the programming space

Hugs. I'm sure we've all suffered this Kafkaesque torture. But it still sucks.

Have you heard of the CIA (nee OSS) book on Simple Sabotage Field Manual? http://www.simplesabotage.com

It predates Brazil, Office Space, Dilbert, etc. After reading this book, and observing management, it's hard to imagine it's not all deliberate. There's just something inherently evil in bureaucracy.

> ...you could make the argument "You Are Doing It Wrong™"

Ages ago my company's study group tackled Applying Use Cases: A Practical Guide. https://www.amazon.com/Applying-Use-Cases-Practical-Guide/dp... After all the monkey motion with UML, schemes, design patterns, etc, this book was like a clarion blasting away ignorance and ambiguity.

It was so clear. Do the use cases. Then directly derive architect from those use cases. Voila! Impossible to fuck up.

However. Young me learned a very valuable lesson.

Nothing is so obvious and virtuous and good that some whackadoodles cannot, will not comprehend it.

But why?

Obstinance? Actual confusion? Inability to suspend disbelief? White knuckled desperate grasp on prior beliefs? Fear? Moral and philosophical opposition? Refusal to concede control (power)?

I have no idea why.

Whatever the root cause, I've experienced these impasses so many times, I've simply given up.

I eventually learned to do whatever it takes to publicly appease the tyrannical gods of confusion, then do any actual work as able on the down low.
its not very accurate, easy to fool and requires facebook to build an archive of pictures of children to build models against....
Fwiw I've been using Signal as my primary communications channel along with email for the past few years. There's an outage once a year or so, but I can live with that. It just works--for voice calls, video calls, chat, groups, etc.

The real question here isn't about which system is technologically superior (though HN gravitates to that question), it's which one is technologically superior taking into account network effects. Briar and Session may be great, and I wish everyone used them, but at present at least where I live it'd be very tough going. Getting people to use Signal isn't all that hard, the network is pretty robust in my communities (university city).
Thanks :)

Yes, I also think that BPM detection would be amazing and we are likely going to implement it in a future version.

Scale detection does also sound like an interesting feature.

However, I can't think of many use cases for key detection since (at least for me) it's quite common to just transpose a lick or some chords as necessary (e.g. joining them together with a different lick or melody or chord progression which I had maybe recorded on another day in another key). So when I'm searching for elements to use in a song, I don't find myself checking the key of each of those elements often or even searching them by key.

Still, I'd be interested to know what use cases you see for key detection :)
Is there a similar database of durability/longevity/repairability based on a car brand/model?
Updates are mandatory in Home edition. Sure you can brute-force your way around it but that hardly counts as disabling it.
Have you read the actual paper? That figure is at best inflated, and their methodology is riddled with confounds, including but not limited to the role of social networking profile pictures as dating signals, intentional signaling such as grooming and makeup, and factors like the the socio-economic status and locale of the people being classified, which can be more predictive of declared sexual orientation than anything resulting from physiological features.

Oh right, it's probably worthwhile to note that since there are considerable reasons in many parts of the world to hide one's sexual orientation, and this study's design only conditions on reported sexual orientation on social media, the results are intrinsically skewed just by being from a population of out gay people

Also, bear in mind that if we take Wikipedia's reported rate of homosexuality in the general human population, for which 9% would be... pretty generous (The "Demographics of sexual orientation" article lists several statistics and I can't find a world aggregate, but e.g. San Francisco is 15%), a null-classifier that always guesses "straight" would be just as accurate. If the population levels were lower, more accurate

Bottom line, that study isn't very convincing
Thanks for that idea! The same thing exists in Germany and if there was a way to draw from that money it would be awesome of course, but I'm not sure if that's realistic.
I worked on a Tensorflow feature in 2018. There was no branching involved. Fork the main repo, build the feature on your child repo, make sure all unit tests pass and then send a pull request to the main/master of the parent repo. Typically someone reviews the code, you incorporate code review comments, pass all unit tests, CI-CD pass, PR approved. That's it. Your code is in the next production cycle.

So yes, you work locally on a fork of the repo but not the main/master repo. I'd surprised if all devs have access to push to main/master.

I think having branches leads to a lot of merging issues. Because technically, the branch will then be used by multiple devs. So it's like dealing with multiple masters, kind of.

Personally, I prefer the TF approach. Oh I forgot to mention, the release tags are branches I think, perhaps read only branches.
The gatekeepers are the ones with the people skills:

https://www.youtube.com/watch?v=hNuu9CpdjIo
you just described 99.99% of software projects. There is no magic bullets. Keep the iteration going and don't overengineer.
Does this really warrant a fork? Couldn't better font rendering be merged into Lite? It's an interesting and quite new text editor. Getting traction for a new editor is hard, and having multiple forks seems like it could make it even harder.
I think it's more complicated than that, and if we're going to call nations on "invading other countries", or meddling in countries internal affairs, we would not be going for US LNG either.

Edit: And I think the EU is capable of putting pressure on Russia by itself, as they/we did. The US pressure is purely self serving and for their own economic wins. Which is fine I guess, I just would like it if we were not so sensitive to it here in the EU. It would save us citizens a lot of money right now.

Edit 2: the Russians would like it too: https://www.rt.com/business/476844-eu-russia-us-sanctions/
Monitoring Windows Hosts with NSClient++: Service Checks Using NRPE and API
Indian state cuts internet to prevent cheating in exam
Play 2 Earn: A New Trend on the Crypto Market
You know what? I am pretty happy about dishonest political smear campaigns being suppressed.
Do not forget corruption. The inflexible hierarchies of totalitarian regimes create networks of personal loyalties and secret infighting that use institutions and public resources into either weapons or sources of self-enrichment without the Transperancy and accountability of NGO-s and independent courts.
I mostly agree. It does depend who set up Jira and why. I’m a developer and have full admin access. I know exactly the kinds of tooling required for smooth integration with the rest of the business. Jira is the one product everyone involved agrees on. (If reluctantly.)

It is a fuck-ton of work to set Jira up so it gets out of the way, but it has all of the customization I need to serve most of everyone’s needs.

If anyone so much as thinks about enforcing workflows on our scrum board, they are going to hear my polite, but firm, rejection of such meddling. It’s our board and we let other people see it so they don’t have to bug us with requests for status updates.

Jira isn’t a hard no for me because I’ve been an admin for it at both this job and my previous one. Let my team manage our stuff, and I’ll happily set up Jira to keep everyone else’s grimy paws off my team.
Honestly nah. Not likely.

My site is already ad free and invasive tracking free so I have no real reason to join and I don't believe anyone donates money like that. Not in high enough numbers to be worth noticing anyway. You might get the odd nerd that's like "hmmmm well acktuallllly, I .." but they've donated like a fiver across the year

I wouldn't sign up as a user either if I'm honest. I'd just go read some other blog if it was paywalled and wouldn't notice a donate link if it wasn't

I do like the idea as an idea, I just don't think the world will do anything with it. This idea plus a better funding model than donations and we're at a maybe but even then I dunno if I could be arsed. That sounds like a lot of squeeze for minimal juice
That the public at large is generally less sophisticated/esoteric in its consumption of the depth enjoyed by enthusiasts & experts of any particular various area is exactly my point.
That's a long time from pr to release.
Ah, ya in our code no one can agree on what sold means so we just trial and error for which one seems to work in each circumstance. Or sometimes we need both so we'll have..

doStuff({soldFromSys1, soldFromSys2, soldType, price, priceType, priceTypeIdKey, customer})

¯\_(ツ)_/¯
It is clearer if you think of it as partial pictures of 24 boys, 12 on the inside and 12 on the outside. In either position, each picture on the inside lines up with one on the outside, and vice-versa (each position is a bijection.) In position B, each of the pairs form a picture of one boy, leading us to count 12. The same is true for position A, except for the one case where each part-picture is well more than 50% (and, in particular, there are two complete heads.) Consequently, this cannot be seen as a picture of one boy, and we count it as two.

In this view, the answer to your question is 'one of each pair, except in one case in position A only.'
Funny, they put bank robbers in prison but when I lock someone in my basement, suddenly I'm the "bad guy"!
HTOP says plex uses 100M
how did you get off the BP meds?
Parental supervision only works if the parent cares enough to even monitor digital usage. Instagram kids is quite possibly the worst idea for society I've seen in a while. The correlation between social media use and mental health issues, dropping grades, etc, in kids that are getting younger and younger, is stunning in my (admittedly anecdotal) experience. I hope this is legislated against, heavily.

Seriously, I'm seeing kids that are as young as 12 years old, spending hours on TikTok or the Instagram explore page, IN CLASS. It's just a terrible, terrible thing to see.
SAFe is beautiful in that it is the ultimate expression of Enterprise Agile Cargoculting: all pretenses of agility are lost, there are ten different levels of decision making, and all responsibility is diffused in a confused mess of worker bees running around under an all-powerful and all-seeing LPM

> Individual teams can use whatever they want to manage themselves (Kanban, Lean, Scrum, etc…up to the team)

Except that they can't, because they will need to align on PI dates based on sprint durations, publish their burndown statistics and various other measures, and there's no way the poor soul who is reponsible for collating that will go into several different tools

> Estimations planning and commitments for each quarter are done by developers exclusively, including coordinating across teams

No they're not, they're done by the product owners, the system architects, the release train engineers (shhh... don't call them project managers), the product managers etc

> Releases can happen at any point

In my experience, releases can only happen at the end of a program increment, or maybe at the end of each sprint because until then nobody has integrated everything together

> A strong and continuously improving CI/CD pipeline is an expectation.

Fair enough, until the "innovation sprint" becomes the "bugfix spring" and all those good resolutions fly out of the window

> I really wish more people knew about SAFe.

So do I, just like I wish more people knew about colorectal cancer

> It’s constantly improving and refining the experience and from what I have seen, if there is a better way to do things SAFe will become it.

SAFe is constantly evolving, because that's the easiest way to keep the money coming in. It's as if PADI had found a way to change diving equipment every 2 years and ask everyone to recertify

Sorry for the tone, but I still have PTSD
I think because you were a developer, so you have that appreciation. I've always preferred working with PM's who were actual Developers. It just makes your life easier.
Hi all, I'm the author - I'll be here to answer any questions you have!