skysight-inc/HackerNews huggingface dataset:
People don't even seem to understand that AI is inside of a computer. It's not real.

The whole argument with AI safety seems to be about how AI can say some "harmful misinformation". Ok. I can say harmful misinformation too, and I'm a real person with feelings that can be expressed to other people.

"AI safety" takes a view that people are inherently stupid, that people have no ability for complex thought and critical thinking.

To me this seems like AI companies such as OpenAI want to stop open-source and monopolize AI where you have to have a government certification to create AI models. Plus a bit of paranoia from the totalitarian liberals who only want consensus rather than debate.

At least there are valid concerns for training models on copyrighted works. Maybe we should focus much more on that rather than on "the AI said something that I don't like".
> You've moved the goalposts here quite a bit from "nobody from the [peanut gallery] has ever, in the history of science, come up with an idea worth pursuing" to "their ideas have never resulted in a new scientific discovery"

I haven't moved the goalposts at all. "Worth pursuing" means "results in a new scientific discovery". That's what you are claiming: that listening to the peanut gallery will give us some new scientific discoveries. I'm simply pointing out that it never has up to now.

> Why assume that physic abilities which seem to defy everything we know would be dependent on fundamental forces?

Because everything is dependent on fundamental forces. That's why they're called fundamental. Again, read the Carroll article referenced elsewhere in this discussion.

> If the US government already had a mountain of prior scientific evidence showing that psychic abilities were non-existent or ineffective they wouldn't have poured such massive amounts of money into that research.

Bad example. The US government, like all governments, does lots of things that are stupid and guaranteed to fail.

> a scientist exploring a topic outside of his area of expertise.

It wasn't outside his area of expertise. Many scientists in the course of their work gain expertise outside the narrow area in which they are credentialed.

It is also not impossible for a person with no scientific credentials to become an expert in a scientific field. But if they do that, they are no longer a member of the "peanut gallery". They are a working scientist. A historical example is Michael Faraday, who never had any scientific credentials at all, but made himself an expert in electricity and magnetism by intense study and experimentation.
Suno VOL-1: Generative Music with Vocals
JumpCloud breach traced back to North Korean state hackers
Larry Page struggling with web dev in 1996
Rosé Pine Theme
I went to DO's site due to your comment and I don't see anywhere where I can just get a server. Do you mean a VPS/Droplet? (I'm looking under Products and Solutions.)
> The CPU will randomly speed up or slow down

constant_tsc has been a thing for more than a decade

> execute instructions out of order, and even speculatively execute

rdtscp serialises

> Not to mention that it'll have a dozen different clocks - which are not guaranteed to be in sync.

synchronised_tsc has been a think for about 6 years now
I'm a fan of the Unihertz Jelly 2. It's great for 'detoxing' from smartphone usage because it is still able to provide useful everyday functions like Google Maps, but is so small that it's infuriating to use for mindless scrolling/entertainment purposes.
Yeah! Make it useless like it has been done to GPT-3.5 and GPT-4 now. Make any other generative models useless as well by adding watermarks (or embedding noise into generated audio). The big tech will have its own models "for research purposes" which are really useful, and all others will simply consume what will be left for them, assured that this is the best they can have.
Looks to me like a vendor specific language with limited capabilities compared to others. Just use Pulumi TypeScript (self hosted).
I'm not affiliated with Pulumi, it's just that unjustified vendor lock-in infuriates me.
Maybe the evolutionary biologist is so next level that they want humans to die out so other animals evolve.
Scaling with common sense #2: Being future ready.(2021)
Or cdktf

> This is a bold statement I know. But I do not believe that infrastructure as code can ever get significantly simpler in its current form

Everything can be made easier to use. Pick the subset of functionality you care about and package it up as a library or module for other teams to use. This was how I paid the bills for years.
My understanding is that it was causing support problems, because people were Googling for solutions to problems with their apps (because of the Heroku diaspora, we have a lot of first-time Docker users), finding old stale threads on our forum that looked related, and then reviving them.

I think we can just `noindex` the category instead of making it private?
> One plants, the other harvests.

This sentiment was so elegantly expressed and struck a chord. Thank you for that.
Nitpicking: planning should not take a lot of effort, it should boil down to "pick the top of the backlog up to estimated capacity".

So the problem you have is perhaps with grooming/estimations. Those have more value if the product owner is not part of the team, and if you work on new developments, as they help prioritize deliverables (we can do X with N effort or Y with 3N).

I personally like sprints as they provide checkpoints, but they should not be treated as deadlines.

It your workflow is just "do this then do that" with no feedback loop related to what you'll work on, then estimations are not useful and sprints are also less useful.
The exports are not yet controlled or optimised enough so, for now hand coded is still the way to go. Unity’s export is unusable, Godot can be OK for nothing mission critical.
Ask HN: First technical hires, what worked and what didn't?
I'm a first time founder. The smallest company I've worked full-time at was ~70 people when I started, though I did intern at startups with <10 people early in my software engineering career. I'm looking for anecdotal advice about how to make things work at the earliest stages, particularly on the technical front.

Would love to hear from founding engineers, early technical hires, and technical founders. What decisions had the most impact on your experience? How did you choose what problems to tackle first? How did you pick tools? What expectations did non-technical team members set? What would you do differently? In short, what worked and what didn't?

(And yes, I'm hiring founding engineers in SF. More info in profile if you're curious.)
You can't fit a manual override to these systems any more than you can a person.
Making the wolf the shepherd. What could possibly go wrong.
Not a great summary from my perspective. Here's what I got out of it:

- Their free tier support depended on noticing message board activity and they didn't.

- Those experiencing outages were seeing the result of deploying in a non-HA configuration. Opinions differ as to whether they were properly aware that they were in that state.

- They had an unusually long outage for one particular server.

- Those points combined resulted in many people experiencing an unexplained prolonged outage.

- Their dashboard shows only regional and service outages, not individual servers being down. People did not realize this and so assumed it was a lie.

- Some silliness with Discourse tags caused people to think they were trying to hide the problems.

In short, bad luck, some bad procedures from a customer management POV, possibly some bad documentation resulted in a lot of smoke but not a lot of fire.
Tannins (and sulfates) are found in all sorts of food. But it's way easier to take the intellectual shortcut and say "it's probably X", instead of "it's probably really complicated and there are a number of factors involved". Some people want simple answers, no matter how complicated the problem is, or how wrong the answer is.
This day and age we can make our own inflation.
We are all free to pay as much or as little for wallet as we would like.
So we all shop by price, quality, or availability.
What is so incredible with successful multiple decade-spanning careers like the one Tony Bennett had is that you must continuously reinvent yourself and adapt to remain relevant. All while not straying too far from your self as to not alienate fans.

He did all of that and so much more.
The disease is frontotemporal dementia (FTD). Genetic FTD is caused by mutations in genes C9ORF72, MAPT, or GRN. These can be inherited, and are dominant.
A great reminder what databases are easy, everyone can do them. It is reliable secure high performance databases which are hard. Make sure you chose provider which has proper experience in this space
I don't think a smartphone has anything to do with their results.

Ignoring your spouse tends to lead to dissatisfaction. Doesn't matter if you do it with a phone or a newspaper or a book
Check out the Unihertz Jelly 2.
I did the same thing, only my program pretended to be a DOS-based Novell Netware login screen.

It was just a simple QBASIC program (that's all that was available on the Computer Room machines) running under my own login, which would write usernames and passwords to a text file in my user directory. I figured that I'd harvest a few passwords until someone got frustrated enough to call for the IT admin, at which point he would try to log in and reboot the PC when it failed, apparently "fixing" the problem and erasing any evidence of my dastardly crime.

I was right, and for a few glorious days I got away with it... until one particular arsehole picked on my best friend during recess, and I used his stolen credentials to log into his account and trash his files.

Long story short, I ended up getting expelled, which by a curious confluence of events put me on an unorthodox path that completely changed my life. Funny how things turn out.
Sergey Brin is back at Google to help advance its AI efforts
Strict WIP limits do not address the fundamental problem sprints attack: that of strategic execution flexibility. This need for flexibility is driven from higher above the developer, at the strategic (business model) level. Done poorly, sprinting usually devolves into micro-water fall. I think this is simply because that is what project and product management knows. Done well, sprinting does aid at the developer level. They are focused on a task and completion gives them a sense of accomplishment.

Sprints are a huge disruption to the established order of project and product execution. They are an artificial time block competing against real world priorities. Companies that do agile sprint execution well have created an environment where planning above the developers is in sync with "time boxed development". Achieving that varies widely. This, in my opinion, is an area ripe for innovative thinking.
That makes intuitive sense. Now, what's an "expression"?
Thanks! I could definitely see the value in that. Once we make it possible to fetch content dynamically it should be easy to fetch Markdown from a repo and render it anywhere on the page. Or it might be simpler to keep SvelteKit/Astro for that since it does it so well and just use Primo for the non-blog pages, which is currently possible.
Some of the ideas here remind me of OAM: https://oam.dev/

OAM has a model of components (things like containerized workloads, databases, queues), traits (scaling behavior, ingress) and in the latest draft, policies that apply across the entire application (high availability, security policy).

It's all a little disjointed and seems to have lost steam. KubeVela is powering along, but it's the only implementation, and IMO it's highly opinionated about how you do deploys and works well for Alibaba and perhaps not for others. But it has some interesting ideas.
Brain Drain and Capital Issues Plague India's Tech Industry
When is anything ever certain? The first shuttle flights flew with only two people who had ejection seats, clearly NASA wasn't certain of success.

I've been watching MIT 16.885J recently, it's a lecture series from 2005 about the space shuttle with lectures given about numerous shuttle subsystems by people who actually worked on them, administrators and lead engineers. Several of them have expressed reservations about the systems in the shuttles. Fear that the hydraulic system was a ticking timebomb that should be replaced with electromechanic systems, recounting an early fear that the Colombia breakup had been caused by a landing gear explosion, etc. These guys weren't certain of much, everybody knew it was a risky project.

https://www.youtube.com/playlist?list=PL35721A60B7B57386
The flipside of course is that they HAVE to be discrete. My issue with sprints is that they arbitrarily reduce the solution space - instead of asking "what's the right way to do this?", you ask "how much can we hack out in 2 weeks to show progress?". By putting a time/complexity limit on the work you choose to address, you are de facto ignoring any potentially high-impact work that doesn't fit into your sprint structure.

Performance optimization, bug fixes, architectural changes, dependency/infrastructure updates, developer tooling, database health, etc are rarely, if ever, prioritized in a sprint-centric workflow. Yet we know these things to be absolutely vital to the success of software.
Igor Girkin Detained in Russia After Wagner 'Tip-Off'
How long does the battery on something like that last?

I'm thinking of something like that and an iPad mini to tether when I need to actually use a screen, the mini would be too big to just keep in my pocket and pull out so I'll only use it for banking, maps, etc.
> Let me give you an example - let's say you are building a road, which happens to travel through multiple jurisdictions. Now in one jurisdiction, there may be a rule that requires one set of employee benefits and different benefits in other jurisdictions.

> Now, which one should the contractor follow?

What do you mean by "benefits"?

Generally what are usually considered benefits in employment are things like health insurance, life insurance, paid time off, retirement plans, life insurance, and similar.

What jurisdiction's law controls those would generally be the jurisdiction(s) that the employer legally resides in. A city regulation with requirements or restrictions on say employee health insurance plans would only apply to businesses that reside in that city.

The city regulations that an employer from another location doing a contracting job in the city would have to worry about would be regulations that affect how the actual job must be done.

For example here in Washington different counties have different regulations on how deep underground water lines must be, because different counties have different frost lines and so a depth that would work fine in one country would might be a pending burst pipe in another.
it's not even the non-js experience, it's just that your js throws a bunch of big fat errors because your subresource integrity is totally invalid and plyr isn't allowed to load

edit: oops it's localCDN's fault... still i think a static landing page requiring JS is kind of weird, what prevents you from putting `title` in the html and then renaming the attribute in javascript?
That depends on the desired features. E.g. if you have a tag cloud displayed in the sidebar on each page, author list, etc., any change to any post could potentially mean all pages have to be rebuilt. Or if you have different ways to display items (full, thumbnail), different ways of sorting them, and maybe even variable pagination (i.e. "show me page 7 with 15 items per page"), and it can very easily become unfeasible to statically generate all possible permutations. In the context of "systems that allow newbies to get results" this may not be as important, even there you might want to have little neat things like displaying relative dates. Dynamic doesn't have to mean user input, it just means dynamic. And then there's search, in case you want/need to handle that yourself.

A probably very naive solution to that I came up with and experimented with is keeping track of all things that go into a page, and tag the cache of it with them, so I could invalidate all cached items that refer to a thing that was just changed (where that thing can be anything, a tag, the site title, whatever), but I ended up scrapping in favor of caching everything for 1 hour no questions asked, because it was just total overkill for my use case.
> I would probably appreciate those comments if I ever need to read branchless code, SIMD code, or similar performance-sensitve witchcraft.

I've done this before in production code. One of my only exceptions to my policy against leaving in commented-out code has been things liking leaving the unoptimized serial code commented out at the top of a section of some hand-vectorized code full of SIMD intrinsic. It clearly showed the intended "what", but was also useful to keep around as a baseline for performance testing and reference code to compare against for debugging.
Nice to see you here.

I once wrote up a more layman's explanation of the Sartre stunt on reddit, as simply as I could try to make it, including why his more modern excuses for it don't hold up either. It references your article. Hopefully anybody can follow along, even if they're not too technical:

https://www.reddit.com/r/bsv/comments/yax6ak/bsvers_right_no...

https://www.reddit.com/r/bsv/comments/yax6ak/bsvers_right_no...

Also, this Twitter thread by WizSec was very good, about how the double hash in Bitcoin vs OpenSSL provided the opportunity to perform the trick. I notice now it's also a response to you, which I didn't remember when I went to dig it up again to post it here. :P

https://nitter.net/wizsecurity/status/1571639561352269825#m

https://nitter.net/wizsecurity/status/1571640691972870152#m

>Ditto, any of us could make any number of similar fakes. It's not only not proof that he's Satoshi, it's evidence that he isn't, since he faked it and lied about it.

>Hidden under all that obfuscation and padding ("when you have nothing, you put more") is just a simple trick:

>Standard ECDSA signatures hash the message once, but Bitcoin does it twice. You can use standard tools like OpenSSL to validate a Bitcoin signature, such as Satoshi's transaction to @halfin, as long as you perform an extra step of manually hashing the message once first.

>Wright took this transaction data hashed-once and then lied by explicitly asserting it's the hash of his Sartre text. Passing this hash along with the Satoshi signature to OpenSSL will confirm it's a valid signature. But it's not his signature and it's not of the Sartre text.

>ECDSA signatures are worthless if you don't validate them all the way from the original message, which OpenSSL normally does for you. But the extra hash in Bitcoin signatures gave Wright an opportunity to perform this trivial trick of simply substituting a different hash digest.

>People like @ryancdotorg already debunked Wright's Sartre nonsense IMMEDIATELY after it was posted in 2016, and Wright is now trying to make excuses for it by saying he's just "misunderstood". Please. The intended meaning is crystal clear and the post is intrinsically fraudulent.
No, they give management predictive approaches to estimation and that's what their purpose is.
Yes, I think that's exactly right: the definition of utility needs to be expanded.
With duchamgpt-v2.3 you can generate as many images of banana and banana-esq items affixed to surfaces as you can imagine, or, rather, not imagine.
This is literally the same cause as "child dementia", which was reportedly called this due to similar symptoms, despite the cause is different, a genetic anomaly that causes accumulation of protein in nerve tissue and the brain. Well, it was thought to be different, but I guess not.
Just stop pushing these theories. You're way off.

> I don't believe 100% that this is how the world works enough to bet my own money, but I am going to tell hundreds of students every year this is how the world works

This is a fundamental misunderstanding of what a good professor does. If the economist acts in this way, they have failed as a teacher, not as an expert in economics. Likewise I think you have a fundamental misunderstanding of economics as a science - it's not one, and it sounds like the economist was making a quip at the predictive weakness of the field overall.

> The biologist story is subtler.

No, it's not. You're just having to push harder to keep it afloat.

> One could argue that failure to become a parent signals that you deeply, fundamentally, don't get biology

One would be wildly wrong to make that argument. Once again, I think this shows a deep lack of understanding on your part of the field itself and what it means to study a field. And also what it means to have a child as a human, honestly.

> economists and biologists vs financial advisors and engineers is that we expect the later to have skin in the game but for some reason allow the former to not have to

Is this not obvious? You're reaching very hard to dig at researchers in a way that indicates you don't know what research actually is. Or maybe you're defensive of the work you do? I shouldn't speculate too hard here or I risk also being this wrong.
They would need the warm body to explain the cold hard math anyways
This reeks of ass-covering so we everyone can later say "We are sorry. We tried." followed by some more innocuous PR lingo

Great for voters to sleep better at night. Useless for actually "managing AI risks"

Not that those risks can seriously be managed long-term, IMHO. The prisoner's dilemma between nation states and corporations ensures someone will defect.
What does yourself out there mean? Basically that you have to work it like a job. You need to go out when to don’t feel like it, go do activities that maybe aren’t super interesting but have the right demographic. You also you have to sell yourself. It’s like working a sales position, you need to be starting conversations with strangers even though it feels weird, you need to be asking for numbers and following up dating is just another form of work. Read, do research, improve your product and try again, and again and again x1000.
Also lower your standards in the beginning. if you are 22 and never been in a relationship you need to start somewhere and that would be with less beautiful women. Then if you keep practicing and building up skills you can date more attractive women.