skysight-inc/HackerNews huggingface dataset:
Yeah I spent a couple of years in the US Army, albeit a long time ago. There were many rules and directives, a lot it was incredibly picky with minuscule impact and soon forgotten. There was an art to divining what was really important and what wasn't.

In medicine today it's sort of similar, a lot of rules are propagated by bureaucratic minds. Sometimes it's just annoying, other times a big headache. On rare occasions such rules actually makes sense.

The problem with rules like the one I cited is the risk that it will be enforced. This can happen in institutional settings like large clinics, a health care system or government agency.

No set of rules or guidelines will be airtight and completely defensible. Yes, we're duty bound to act on the basis of reason and good judgement. However when rules are generated that are out of touch with reality there's a risk that regulatory entities, insurers, etc., will pick up that ball and run with it.

Impediments to practicing according to one's best medical judgement are ubiquitous. One is insurance company rules requiring preauthorization for medications, even many generics. Can't tell you how many hours me and staff have spent knocking this around. Of course delayed treatment affects patient well-being. Ironically 95% of the time the meds I intended to prescribe were eventually approved anyway. Having to play the game accomplished nothing of value for anyone.

You ask "What central authority...?" Of course, central authorities don't know the best solutions, often enough not even passable solutions to problems. Too many rules are as dangerous as not enough rules. I believe developing rules via "bottom-up" methodologies would produce rule sets with minimum necessary restriction and conceivably could even be productivity enhancing.

I'll be quiet very soon, but I'm reminded of a patient encounter. A man was in my office talking about conflicts at work re: a micromanaging supervisor. It was a group of PhD-level software engineers. I was thinking, do these people even need "supervision"? Shouldn't they be trusted? Trustworthy professionals can be relied on to do their jobs. Sure, keep an eye on work quality, allow the track records to speak for themselves.
You have to admit that is more work though, and devs on a limited size team like the gnome developers have to draw the line at some point.
I think people used to use bulletin boards and classified ads. And what stops you from using personal networks now?
Looks nice, but the advertisements make it almost unusable on mobile. Although they don't always seem to show up
This article was wrong in the first sentence, of the first response, the first question.

Not only is Ukraine not being 'mopped' up they are on the counter offensive causing massive damage to Russia.
I didn't say that labels don't use TikTok, so you're disagreeing with nothing. What I said, was that labels don't have any legitimate value in a TikTok era, because there's nothing that they can do which an independent artist can't do on their own.

> Also, labels have so much infrastructure for marketing, merch, booking shows etc.

No, they actually really, genuinely don't. They use the exact same channels that independent musicians do. Booking agencies, merch providers, publicists -- all of them are hirable by anyone, not just labels. Everything you think that labels do, they hire someone else to do that, and then tell you that they need to keep ownership of your music to recoup those costs. That is how the music industry has worked for a hundred years, and if you disagree with that, then go read literally any book on the subject.
Just like programmers should have to run their apps on 10 year old computers and feel the pain, so should designers have to try their work on 10 year old monitors.
“In-app purchases” are kind of common in desktop apps. They have a basic free version which constantly nags you to buy a subscription or the premium license which then unlocks more features. And lots of desktop apps have ads.

I agree otherwise about supply and demand.
We suspected this as well. She is lactose intolerant and has IBS, this can cause complications with the efficacy of the pill.

We weren't making it easy for the contraceptive either. I mean, several times a day, every day, for years... One of them was bound to get through eventually anyway.

I've understood that this kind of contraceptive makes only conception extremely difficult, not impossible. She was still ovulated (tested), and had regular periods.

It was extremely easy for us to conceive our second child. Now we have two pretty kids!

But we have to be really, really, really careful, lest we have yet another...
Postico is a really solid piece of software. Very user friendly and approachable, it's a tool I use every day for working with databases. Solidly recommended.
When I was in grad school working on semiconductor process equipment I actually had this thought, but I was concerned about the unknown health implications of consuming food treated with plasmas of various chemical species... and graduating. In another universe, pressure cookers evolved into plasma cookers
Funner facts; HDL is not protective. It correlates negatively with poor glucose control. That is, people with low HDL have impaired glucose control, but raising HDL doesn’t bring any benefit.

LDL concentration isn’t meaningful at an individual level. LDL particle counts however are. Lots of small LDL particles are way more atherogenic than a few large particles, given a constant density.
9% onchain is much greater than I thought! I’m actually impressed

But I bet a large breakdown of that is spammier NFTs that use string concatenation and svg rendering such as MLOOT

Also of the HTTPS I bet much of that is Pinata or Cloudflare which are just pinning services for IPFS

In any case I’m actually impressed by these numbers and expect them to further improve away from HTTPS
And Flooz.
> As I mentioned before, Canonical and Red Hat have money and could afford proper designers.

They do employ designers, including for GNOME. You might not like their designs. But to call them anything but proper is pretty mean spirited.
SPoTKD: IoT protocol for cryptography using self-powered timekeeping devices
If this is what software engineering turns into, put a bullet through my head please.
A case study in early-stage startup execution
Bad money (like inflationary fiat currency) creates the need to use other assets to preserve wealth, which creates bubbles in those assets.

Bitcoin advocates say good money (Bitcoin) will return the value of all other assets to their utility value because the best passive store of value will be the money itself (which due to a fixed supply would be deflationary).

In that world, people would rather sell assets they don't use to accumulate bitcoin (or money x) because only useful activities will produce more yield than the money itself. This frees up housing, land, precious metals,... and all other resources that are artificially scarce due to hoarding for wealth preservation.

I've heard people estimate, under a Bitcoin standard, the actual utility value of a house would be approximately 5-10% of current prices.
Malthus is the butt-joke of economics, so much it became a rite of passage to mock him. Marx's Capital and Henry George's Poverty and Progress dedicate some time to his humiliation.
> When you read quality writing like you'd find at Nature, Aeon/Psyche etc, which values the ideas for themselves rather than for what outrageously speculative headline can be squeezed out of them for "the man on the street", you can see a huge difference in the way it's being communicated. And you're right - it's not as successful, because the good stuff isn't negative-emotionally triggering (unless the worst kinds of tabloids get their hands on it).

To be clear, to anyone reading, I guess that the approach used in Nature, which values ideas for themselves, would be more successful with the general public; it's just not used.
I think we really need to limit how many one can own. Start taxing very very very heavily for anything beyond a second home for individuals and and anything beyond another number based on statistics for a company. Also add attitional tax for every two months a property is owned but no one is living in it or using it for business. This should cut down on hording and incentivize companies and people to get rid of any property that is just lying there waiting for prices to go up.
These articles are almost always over my head. I know that coffee has LOTS of chemicals in it besides caffiene, do you know of any in particular thought to benefit the heart, immune system, etc?
Ah I did get confused. I have Luke's book from 1990 still!
As a member of the Security community, it's disappointing to hear that this is the perception on the table, because our community can and should do much better than that. In my experience and goals, the best Info/AppSec/SecEng teams put people before processes, build guardrails instead of walls, and demonstrate first hand what they want to see engineering teams doing. If you're open to it, I'd like to offer perspective on why some of the perceptively dumb things that sec teams do, do.

Those automated tools are better than ever. Manual code reviews are very important, but automated tools at this point can stand in for "over the fence" pre-production code reviews, as long as periodic reviews occur. In particularly sensitive contexts, especially finance, code is always signed off on by security before release when it can have impact on anything important. It's all about risk management.

Additionally, the cloud and SaaS is nothing like it was a decade ago. Security is now more focused on compliance due to the nature of building software today. You used to maybe provision a handful of nodes on EC2, use an autoscaling group if you were super fancy, and probably integrate into a handful of third party APIs. Every business is different, but that was the core of running a workload. Now, I can delegate specific responsibilities to third parties and reduce both people and operating costs. But with that comes massive risk since you just transferred an internal business function to a third party you have no control over. The most common approach to that risk is through process: vendor reviews, compliance and cloud posture security management.

And then there's DevOps who ends up being ad-hoc security way too often with no relevant background (or interest).

All that to say, good, compassionate security teams do exist.
photography is nice... while still being a tech-hobby, you get outside. It takes some time to learn the principles and is still fun, when you advance. Besides that it can help you improve your tech projects, because the self created pictures and movies can be used on websites, etc.

You could start with a very cheap used camera (e.g. the Sony A6000 about 300 bucks including lenses), and if you like it, upgrade to more professional ones.
> Playing this game of cat and mouse will add so much red tape that nobody will want to use that package manager anymore.

Of course. But your comment still reads as "we can't make it perfect, so might as well not try at all". I think there can still be value in limiting the blast radius.

Your while(1), if present, is likely to be intentionally malicious. But I've seen many naïve libraries implement "accidentally quadratic" algorithms, which is basically a disguised while(1), but unintentional.

The point is that the end result of `rm -rf /` is painful. It doesn't matter if someone managed to maliciously sneak that into your supply chain, or if it rises from some funky corner case of some package whose only goal is to bring world peace. So being able to prevent some leftpad lib from accessing the file system at all makes a lot of sense.
Sounds like Chesterton's fence¹.

[1] https://en.wikipedia.org/wiki/Wikipedia:Chesterton's_fence
There are tools in between a heavy word processor and a very dumb text editor. Can you even undo more than one character now? I mean, sure, for quick little edits, Ok. But don't tell me you'd write a book in notepad.

And spell checking is a good thing.
You're trying to twist this into a scenario of absolutes, as if there's an on/off switch at which point independent artists make 100% of the money and labels don't exist anymore. That's clearly not what I said, and it's rather inflammatory of you to suggest that it is.
Google "contributes" whatever they are paying to Mozilla every year. The reason Mozilla exists is to maintain "plausible deniability" in terms of anti-trust for the other browser "vendors", which used to be IE, but is now Chrome(-ium).
I think most people that regularly drink coffee, tea, soda have a caffiene addiction. Parting ways with it often induces pretty hefty headaches for a while and people are best served by weaning them selves off of it. 3 cups a day -> 2cups a day for week or two -> 1 cup a day for a week or two -> cup of tea -> 1 gallon water a day.
Do you have a source that the binder is currently being used as a fuel source? I'm missing where that's implied by the OP.
As with most harmful speech classifiers (even classic models) this most likely won't catch the more passive aggressive remarks. Those worded innocently but imply something terrible. I've had a 100% success rate getting these sorts of models to tell me asking someone to "kindly end their own life" is not rude, toxic or harmful.
So on desktop applications, I assume you prefer all your functions to be on toolbars, and you have similar disdain whenever you encounter a File menu? I guess if there's a lot of functions, you probably need some tabs on your toolbar- so the Office Ribbon interface is idyllic I assume?
Here is my personal introduction into hugo:
https://pilabor.com/blog/2021/05/building-a-blog-with-hugo/

The site itself has been created exactly like this.
Stories like this make me wonder if increased jerkiness is an unfortunate side effect of increased intelligence.

You need to be able to recognise the individual and put yourself in their shoes and imagine what would annoy the target and then execute your plan.
You really wouldn't want to use any of these algorithms on doubles (certainly not in the general case).

Think of NaNs, infinities, operands that are vastly different in magnitude (e.g. try calculating (1e10 + 1e-10 - 1e10)) and so on.
When possible, I first visit the place without a camera and strive to immerse completely. I then visit it again and take pictures. Not using the camera the first time - and having to think about how I'll take the pictures when revisiting - provides a lot of opportunity to appreciate and reflect on the sight in question. With places I can only visit once, I try to take as little pictures as possible, and instead embrace living in the moment to let my mind and heart preserve the memories.

I've learnt this one from my other half: she rarely takes pictures because focusing on pictures detracts from actually living in the place. She takes pictures as a sort of "index" for where we've been: a quick of us together with the location in the background, maybe one or two snaps of beautiful sights, and so on. It's pretty rudimentary, because ultimately, the vivid memories are preserved within us rather than the photographs.

Though I won't deny that the fear of not capturing everything can get to me at times, thus I end up taking one too many snaps. I think that's a fear many people deal with when they take an inexplicable amount of photographs of the same thing!
ISO is essentially a collection of national standards bodies that are often under government or semi-government authority.
> you don't know anything about how language or your brain works

It seems there is a proclivity here to make claims that one could not possibly know are true while committing an astounding three fallacies simultaneously, the ad hominem, the argument from authority, and the straw man. Congratulations on your fallacious hat-trick. Your argument here is invalid thrice.
I have heard of IPFS's bad performance quite often and as you point out it is weird because I know that isn't specific to distributed storage in general. How much of this is implementation specific though? Would it be possible for there to be a IPFS implementation that solves most of these performance problems? Since the protocol itself is so similar to bittorrent it would surprise me if it is protocol inherent, but I am not sure.
Oh, I didn't realize you were talking about not using your SSH keypair as the SSH CA keypair. Well, that's kinda expected. The SSH CA keypair is the single point of failure in this case, which sounds worse than it is but it's okay to have such a thing because of the benefits, so it should be protected and isolated.
I'm not very familiar with how Node dependencies work, but isn't this just reshuffling the same card deck?

If package M is malicious, what difference does it make if it's required directly by your app, or through a sub-dependency chain, like A -> B -> C -> M?

If you have an approach that allows you to vet all your direct dependencies, why wouldn't that allow you to vet sub-dependencies as well?
I agree, but it's not a trade-off; it's not one or the other. You can have excellent, engaging writing that values the topic deeply. I would say that the dumbed-down presentation I describe makes for worse reading; that's what I had a hard time reading. What I read in Nature, in my example, is much more enjoyable to read.

I remember well-written history much better than the dryly written.
Transgenderism is the treatment to dysphoria. Dysphoria is a condition that is just as demonstrably provable as depression or any other mental illness.

If you were to wake up tomorrow in the wrong body you would also have dysphoria, and you would also try to treat that.

Humans are not some machines of perfect logical emotions and reasoning - you are no exception. On the contrary, it's narcissistic and selfish to think everyone has to be you, someone whom doesn't have dysphoria. That you are somehow the arbiter of what gender is. From what source is your knowledge based?

I used to think things were defined in books and by experts, turns out we know jack about humans, all we can really know is by experiencing them, and I can tell you first hand dysphoria is enough for good people to kill themselves. So, think on why that is, and look to the truth for an answer.
This is a really interesting topic but I'm offput by the verbosity of this essay. For example:

> And whatever our credences here, we should be clear-eyed about the fact that helping or harming an infinite number of people would be an extremely big deal. Saving a hundred lives, for example, is a deeply significant act. But saving a thousand lives is even more so; a million, even more so; and so on. For any finite number of lives, though, saving an infinite number would save more than that. So saving an infinite number of lives matters at least as much as saving any finite number – and very plausibly, it matters more (see Beckstead and Thomas (2021) for more).

Is it really necessary to have a whole paragraph explaining that saving infinite lives would be a big deal? I don't think a single person would believe otherwise, which means this paragraph is zero entropy. Most philosophical essays seem to have a similar issue.
Remove that annoying sticky header with this js snippet pasted in your url bar:

javascript:(function()%7B(function () %7Bvar i%2C elements %3D document.querySelectorAll('body *')%3Bfor (i %3D 0%3B i < elements.length%3B i%2B%2B) %7Bif (getComputedStyle(elements%5Bi%5D).position %3D%3D%3D 'fixed') %7Belements%5Bi%5D.parentNode.removeChild(elements%5Bi%5D)%3B%7D%7D%7D)()%7D)()
Vote with your wallet, not your ad blocker (2015)
The negative comments seem to assume an open loop development strategy where if copilot fails to give the 100% correct result it is a fail. Rather, even if it is wrong it can get you close and if not close it can give you ideas. You have to close the loop and use your own intelligence as well.

For example I can't draw faces but I can recognize a badly drawn face. If I ask an AI: Please draw me a 35 year old man with receding hair and crooked teeth I can quickly validate the result is fit for purpose. If it is not what I want I can modify the query. I then learn quickly how to prompt the AI to give me what I want.

In the example you give we can assume that the AI has produced a plausible option even if wrong. For example a scenario may be:

# User: Write a comment "Convert the date to the current local for printing"
# Copilot: generates the method 'toLocaleString'
# User: Mouse hover over the method to get the documentation for the 'toLocaleString' method
# User: See that the method produces the wrong output. We realize we don't want the date
# User: Modify the comment to "Convert the date to the current local for printing time only"
# Copilot: generates the method 'toLocaleTimeString'
# User: Yes this is the one I want. Moves on

The key point is you have to know what you want and be able to recognize a correct result. Validating a correct result is often easier than coming up with the correct result. You have multiple strategies to validate the result.

Testcases,
compilation,
code review,
documentation,
IDE intellisense

This obviously gets harder the larger the amount of code copilot is being asked to generate. But good software engineering practises still stand. Try to keep your functions and modules small and to the point.
It looks great, but as much as I like mac-native apps, I use Mac for work, and Linux at home. TablePlus is cross platform, and much better for my needs.
I see chili dogs come in at {0.3,0.2,0.75}, but now I'm curious what {0.5,0.5,0.5} in the SSS space would look like. Something like niangpi, perhaps? Cold starchy noodles with chunks of wheat gluten (bread), served in a soupy sauce of chilli, vinegar, etc.

https://en.wikipedia.org/wiki/Linxia_Hui_Autonomous_Prefectu...
I think designer's easily forget that trends exist, and what people want is a mix of what's useful but also new and popular.
Every time I see an article about cooking, my first instinct is how I can code this information so machines can cook it for me.

But there's still so many unsolved problems at the moment, especially around object recognition. Maybe in a few decades.

Once that's solved, I imagine there will be a lot of engineers tinkering at home with their robots, sharing code for say cooking the perfect steak, the best coffee, and a general recommendation engine that can predict what you'll probably like.

Can't wait. I don't get excited about cooking, but coding cooking machines gets me going.
US charges four Russian hackers over cyber-attacks on global energy sector
Yeah I have sometimes thought about trying to make a IPFS implementation myself to test this theory.
Built by who? There were no humans back then.
The vast majority of atheists are agnostic atheists by Flint's definition. https://en.wikipedia.org/wiki/Agnostic_atheism

Many outright reject specific gods of mainstream religions with known logical contradictions but do not claim to know for certain that there is no teapot between Earth's and Mars's orbit or that there is no supernatural deity at all, only that both are unlikely.
16-year-old living with his mom is Lapsus$ mastermind behind Microsoft hack
Respectfully, I disagree that the UI is awful. It's minimal and plain, yes; but it's also fast, lightweight, and information-dense. The UI conveys that this is a site for power users, at least in comparison with the average web watering hole.
What are your opinions on DBeaver? https://dbeaver.io/
What's the use case? I see a sibling commenter mentioned puppeteer which I'm aware is essentially Chrome. Are you too referring to running puppeteer in Lambda? If so, what is the purpose?
The comments. I don't even read the article most times. To me, it's the topic for discussion.