skysight-inc/HackerNews huggingface dataset:
It's interesting that the prompt here pretty much immediately became a Dr. Who game. It looks like there has been a Dr. Who Text adventure game before but it was made before Jack Harkness and Torchwood. I wonder if there is some fan made text adventure that was part of the training data. Probably would be best for Open AI that it doesn't just spit out copywrited characters unprompted too.
What is Creatine? Understanding its Benefits and Side Effects
My mistake, left over from the ShareLaTeX -> Overleaf transition. Updated.
https://archive.ph/Bcr7z
Thanks for sharing! And sorry again for being harsh, I'm keen on reading some more shares about actual strategies in engineering tooling or others that you worked on to keep things chugging along. The focus on metrics I think is very under-appreciated in our industry and the more we can standardize to compare velocity and easily identify companies that don't give a shit about developer experience and velocity, the better in my opinion.

I would say that I believe it's a much happier life the less you think about how good you or your colleagues are and the more you think about the systems and the tools you develop. I really meant what I said about impostor syndrome, I'd be curious what answers you'd get from your engineering team regarding that, if so far you've focused a lot of your internal messaging / culture on "being good", you might find some opportunities for honest feedback and sharing which might get a more tight-knit empowered team, which does wonders for velocity.
Microsoft also decided to wipe my entire inbox because I didn't log into my hotmail account all the time.

This was the first time an email company this big pulled some shit like this in the internet era.

All my correspondence from my high school years to my mid-twenties were gone, including cherished back-and-forths with people that were now deceased. It felt like someone came and burned down my house while I was on vacation.

Just thinking about it continues to paralyze me with rage.
But imagine that we could compute BB(n) for any n, even if we need to use a different algorithm for each n. Then, we could build the mapping n -> BB(n). But the existence of this mapping is forbidden by the unsolvability of the Halting Problem, isn't it?
Because that’s how screen readers know the image is decorative. It literally is/improves accessibility.
Both the links are me trying to not link paywalled news stories (or Matt Levine columns) even if they have friendlier URLs.
tried installing it on iPhone and set the HomeBase - keeps on crashing.. :(
If you have more than 2 levels of nested null-checks I would wager you are doing something fishy. You should probably go with mapstruct or similar libs (which are absolutely cool and a must for data conversions).
Look, if you want to draw from a unit circle, you could enclose the unit circle inside a square. If the center of the unit circle is the origin, it should be clear from some middle school geometry that such a square has upper left cartesian coordinates at (-1,1), bottom right at (1,-1). So its a square of side two. Now you can sample from this square by calling the rand() function twice in any programming language, scaling & translating. So def foo() { -1 + 2*rand() } will do the trick in c/c++/scala/python/whatnot ( I've scaled by two and translated by minus one). So you have your two random variables. Pair them up & that's your tuple (x,y). Now if you make 100 such tuples, not all the tuples will lie inside the unit circle. So you have to toss out the ones that don't. So your drawing isn't 100% efficient. How efficient is it ? Well if you toss out say 21 of those 100, your sampler is 79% efficient. Now where the fuck does the 21 come from ? Well, if you use some high school geometry, unit circle has area pi and that enclosing square has area 4, so pi/4 is approximately 79%, so 100-79 is 21 and so on...So one can construct more efficient samplers for the unit circle by not being so foolish. We should stop enclosing circles in squares & listen to Marsaglia. He died a decade back but before his death he solved the above problem, among others, so we don't waste 21% of our energy. That said, most programs I've seen in banking, data science etc are written by programmers, not statisticians. So they happily use an if statement & reject x% of the samples, so they are super-inefficient. Drawing can be efficient if the statistician codes it up. But that fucker wants to use R, so given the choice between some diehard R fucker & python programmer who can mess around with kubernetes & terraform in their spare time, hapless manager will pick the python programmer everytime, so that's what makes the drawing inefficient. /s tag, but not really. Just speaking from bitter personal experience :)
And it's very easy for an author of an opinion piece such as this to overlook something or over extrapolate something or assume that medieval drawings are accurate. In the case of this article, most of what the author has cited is information about the British Isles and then extrapolated that information to cover all of Europe even though regional differences almost certainly existed and things likely changed over time as well. It's not like the world was just static for 600+ years.
IIRC there are copies around 300 CE and possibly tiny fragments earlier. Regardless it doesn't add much credence IMO.

Book of Mormon was written during Smith's lifetime. I still don't believe he talked to angels or actually got divine revelation from golden plates.
That seems to be the chicken-and-egg problem here: the current problem is endless repetitions of "none of the existing options are good enough, let us build a new option". The call above is "just pick one and everyone work together to make it better", but we're back to "none of the existing options are good enough".
Many people have noted his behavior seems very similar to someone in a manic episode. While this isn't bulletproof evidence and shouldn't be taken as such, I think it's worth something. There's definitely something off about him, that doesn't mean he has no responsibility but I think it's telling the reaction
I used to run one of the biggest territories in the world for one of the biggest digital music distributors in the world.

This is a very blunt estimator based on questionable data and questionable assumptions about the listeners.
In the proof you just provided, you have a step "remove ones which do not halt". By which process do you do that? By the halting-problem, you can't actually make that selection. This ties back into the fact that BB(n) is not computable for all n. I guess what I'm looking for is a proof that the number exists without violating the halting problem. Intuitively, we feel BB(n) should exist because there are finite turing machines with n states. But I'm not sure how to express that rigorously. Or maybe relying on a solution to the halting problem doesn't matter in terms of a proof.
Nice observation. Unless you’re missing something that seems to kind of shoot down the main point.

The post and it’s analysis are still interesting, but it should probably be updated else a lot of people might take away this key point into their memory as they think about computability.
Meta Lets Brands Search Facebook and Instagram for Stolen Content
its not about you. Its about him. He can say that he is 2m, 100kg, but in the end he is a 1.60m, 120kg chubby hobbit and we are never going to know. Those anecdotes have 0 value, specially coming from a HN user, who decided to get a socket puppet to post. It is just noise.
The First Unleaded Aviation Fuel Has Been Finally Approved by the FAA
For real, even if they don't go back to previous highs they're vastly underpriced right now.
There is little to no time spent in this article on how photopea is monetized. I even went to the product itself to find out but couldn’t, at least on mobile. Is there some subscription? What do you pay for? Genuinely asking since I used it a few times and never noticed any payment nagging.
How would you expect a language as low-level as Zig is to support colorless async? It pretty much requires some kind of green threads.
Right, roguelikes in a lot of ways are similar to ye old arcade and console games that were short on content but were very challenging; the 'content' was effectively that you had to die a whole lot and reset back to the beginning of the game, gradually getting further each time as you got better.

Contra for the NES would be an excellent example of this. The whole game lasts less than an hour for even a moderately-paced run, but it's quite difficult if you're not used to that specific type of game, so in practice it'll take much longer than that for most people to beat it, as they have to restart multiple times. Same deal for Super Mario Bros 1.

Roguelikes are the same kind of loop, but with the improvement that the levels are somewhat different each time. They're still usually similar enough in style/theme/enemies that skills carry over from run to run, but you at least can't just brute force memorize everything. You have to Git Gud or you'll be stuck forever.
While I support pay transparency on principle, I have never seen it work. In practise, no two employees are ever equal. Even those with the same years of experience, the same qualifications, and the same roles. One might be happy to work late. The other might be happy to pick up the phone on weekends. One might prefer working alone. The other might play better with colleagues. One might offer to take on more projects. The other might not, but they have better attention to detail. The differences go on ad infinitum. There is no "objective" way to determine the market value of each of these two employees. The best we can do is let each business make subjective judgments of each employee. We know this is far from perfect, but it could be more fair than paying two very different people the same wages just because they studied the same thing at university and worked in the industry for the same length of time. One of them will be contributing more to the business bottom line - sometimes significantly so - and they probably know it. They'll leave if they're paid the same as their lesser-performing colleague.
That could harm the experience for assistive tech users more than no alt tag
"Globus Cruciger" is a badass name for an indie game
First paragraph seems like a giant strawman. Not sure this is worth the bits it is stored on.
How does this compare with Yesod?
Intel poised for layoffs amid growing doubts about turnaround plan
photopea is one of the best examples of a web application imo. Its a full featured image editing software just running in your browser. No sign up or login required and you can just upload and quickly work off a local file for your computer. You just fire it up and start working.
You can view a map here of how much advance warning people with ShakeAlert-enabled phones (like Pixel) got before the earthquake:

https://earthquake.usgs.gov/earthquakes/eventpage/nc73799091...

Santa Clara had 2 seconds of advance warning, and Sunnyvale had 4 seconds. San Francisco got 18 seconds of warning, though was outside the "ground motion" zone.
Shin: A shell in every text input on your system
Is there any actual proof that Turbopack is 10x faster than Vite at anything? I can't find any benchmark showing it.
ClockworkPi also do kits for a device called DevTerm. I have one, I like it a lot. Keyboard is... not great. But you can make your own expansion boards.

https://www.clockworkpi.com/devterm
You can receive anything... sending is another issue.

This is discussing passive radar, where you use another emitter, like a FM station or 20 to be transmitters, and your "radar" just sits and listens for the bounces off other objects.
It seems to be an ongoing tradition as well, I would go read the previous release notes just for those bits.

https://www.google.com/search?q=inurl%3Ahttps%3A%2F%2Fwww.py...
> Unfortunately securing this attack vector is costly - in the sense of annoying the user with prompts and access grants.

You're making assumptions about what the implementation would be. There are many ways the UX could be unobtrusive. Besides, I'm not even proposing that the solution should be to restrict access to the clipboard. I'm just saying that there should be a secure channel between apps provided by the OS that can be used for these purposes. Designing and implementing that would be costly, sure, but I'm not an OS designer, and merely speaking what I would like to see as a user.

> But in practice, this attack vector is not exploited.

Of course it is[1]. It's not even an exploit, but an abuse of a glaringly insecure OS feature.

> If you are targeted, it's much more likely that a specific attack against the password manager is used

Again, why are you minimizing this clearly easy to abuse OS feature by comparing it to much more sophisticated exploits? Yes, there are other attack vectors. This thread is specifically about how the clipboard is trivially abused.

[1]: https://news.ycombinator.com/item?id=33330035
Aside from the technical challenges of running a system with such a massive amount of data:

translations (left to right text and layout: https://sy-sy.facebook.com/), different laws depending on jurisdiction; for example privacy/moderation/takedowns, taxes/payment/invoices if you are selling anything, accessibility

If you ever start a company and you have the long-term goal to offer your service in multiple countries I would advise you to launch in at least 2 countries, preferably supporting different languages.
This is not the case, optimizing compilers were quite far along by the 16MB era. RISC relied on them, GCC was widely adopted due to optimizations, etc.
Unless you're being paid by customers with specific needs, or targeting some weird platform, my expectation would be that libraries don't support old .NET versions an instant longer than Microsoft does.

So .NET 6 support can be dropped in late 2024, and I don't think that kind of thing even requires a major version bump. The old framework is dead.
It has been said that mobile wikipedia is more user friendly on any platform, basically a more modern user interface than the standard desktop interface. Thus having benefit to everyone.
Thanks for your feedback. We'll introduce an in-between plan to solve this problem.
I really want to write up a long response to this... I used to be closely adjacent to this field, and I do ML work in other domains. ML is mostly irrelevant for this, though.

Here's the short version:

We're good at predicting where. We're still not good at when.

Understanding what segments of a fault zone have built up the most elastic strain is something we're really quite good at these days. Given historical earthquake data, GPS measurements of deformation, and knowledge of the geometry and makeup of the subsurface, we can reasonably accurately model what segments of a fault are most likely to fail next. No ML needed or wanted.

The issue with the "when" is what the precursor signals are.

The precursor signals we're most likely to be able to reliably measure involve drilling down and putting sensors on both sides of the fault zone and measuring the sonic velocity across the fault zone repeatedly. As rocks or even a fault gouge begin to fail, they have to dilate slightly so that grains can rotate into position to slip (bad explanation, sorry). This dilation causes a drop in sonic velocity. Stresses on the rock mass as a whole also have velocity signals. Lab experiments have observed this fairly reliably. We've actually set things up to measure this in the field as well -- look up SAFOD. There were some likely precursor signals (a bit contentious, but it's fair to say there were interesting signals in the data). However, this type of instrumentation just isn't practical to deploy at scale.

Other possible precursor signals involve hydrologic changes (e.g. well waters rising / changes in pore pressure) or Radon spikes, both due to the same dilation. Again, though, these are local effects and difficult to deploy a system to measure. (e.g. you need a deep borehole for the hydrologic changes, and the radon spikes are most reliably observed at depth as well)

There is one more controversial category that is easily observable: ionospheric perturbations. GPS data is sensitive to the ionosphere, and one of the things you need to do in geodetic GPS station operations is correct for changes in the ionosphere. We tend to have tons of geodetic GPS stations deployed along fault zones. Folks have noticed some very interesting ionospheric perturbations before very large earthquakes. There have been a lot of papers published on this, but it's still not too widely accepted, last I checked. The proposed mechanism (piezoelectric effect and/or dislocation glide/creep building up charge) and the observed magnitude of change don't match. It also has only been documented as a precursor around very major earthquakes (which are rare) and only in retrospect.

At any rate, tons of data don't help if it's all noise. The data that we think should have the most signal is _really_ hard to get. Things are still in the "promising, but a long ways off" state when it comes to predicting "when", and seismologists are _very_ careful to avoid doing work that could be taken as predictions due to past PR SNAFUs.
Arguably everyone in the US who owns or constructs an SDR is a felon, by virtue of violating the Electronic Communications Privacy Act of 1986 [1,2]. Certainly everyone who sells one.

AFAIK this misguided law has never been repealed, despite being rendered obsolete by the demise of the old 800 MHz AMPS standard. No 800 MHz-capable SDRs I'm aware of make even the most casual attempt at blocking coverage of that range.

So, yes, it's legal to build a radar -- certainly a passive one -- but given that most SDRs cover the ECPA-prohibited frequency range, it would be hard to build a radar with off-the-shelf equipment without breaking other laws.

1: https://en.wikipedia.org/wiki/Electronic_Communications_Priv...

2: https://forums.radioreference.com/threads/cellular-blocked-s...
Not all comment replies are disagreements.
This is cool but it's not quite a radar yet. He saw an increase in signal strenghth when a plane overflew his position and reflected some of the signal.

Modern SAM systems are said to have the capability to track targets passively, for example by using reflected DVB-T transmissions. This is very important because combat aircraft have radar warning receivers, and it's best to not tell the enemy you're engaging him so that he can use countermeasures or perform evasive manoeuvres. Also SEAD/DEAD (suppression/destruction of enemy air defenses) is near impossible unless you can first locate the enemy air defense radars, which becomes a lot harder if you cannot simply home in on strong RF emitters.
> Looks like blitz is tRPC + next auth?

From what I understand Blitz is their own implementation of tRPC, their own Auth system, Prisma and Typescript support. Blitz is also more of a toolkit that wraps around NextJS currently, but later on Remix, Svelte and Vue.

In future (probably in '23 and post 1.0) some things that may be coming are:

- backend functionality ala NestJS

- form component library

- permissions (rbac) library

- file upload library

- and a bunch of other stuff I'm forgetting right now.
I'd also say the average person has no intuitive sense for earthquake magnitudes and giving a somewhat precise number wouldn't affect their behavior the way a broad category warning like mild, moderate, severe, and catastrophic would.

I suppose the people getting these notifications really just want to know if they should scramble for safety immediately.
Slightly off. That was on Oct 17, 1989.
Yeah, it really pains me that Sitecore is doubling down on them as the main FE framework.
Perhaps you need larger and larger sets of axioms as k increases.

This is fascinating to me, because Turing machines can in principle be manifested as physical objects. It feels like you shouldn’t need axioms if you have the thing sitting in front of you, but on the other hand how else are you supposed to prove something doesn’t halt?

Still, if you have two axiomatic systems that disagree, what does that mean? Surely you can just run the machine in question for a certain number of steps to determine which system is right.
Wait, so reporting bias in CVEs makes my proposed experiment bad, but your assertion about 70% of CVEs okay? Surely all the memory safety bugs that show up in the next 10 years will make this no contest...

Onto latent bugs: part of the idea of latent bugs is that they are latent, as in we don't know what they are yet. I am just pretty darn sure that we haven't found all the bugs in computer software, or even all the possible types of bugs. Spectre didn't show up until 2018, and it was a totally new type of bug.

I am pretty convinced, after working on huge-scale systems that get fuzzed really well by their clients, that we have found less than half of the exploitable bugs in Linux (and other similar systems). I'm not suggesting that Rust will hurt here, just that there's no evidence that it will. They will probably show up in C and C++ code too, but you never know.

By the way, one class of vulnerability that Rust code tends to introduce when compared to C++ code is supply chain attacks. Cargo/NPM/Pip are attack surfaces. So far, the worst version of this that I have heard about in Cargo was that several packages started printing some harmless politically-motivated text on startup.

Also, let's get this straight: I am saying that the claim "Rust reduces exploitable bugs" has not been proven yet. Let's stick to that, shall we?
Well, while you are developing a language, in particular a system programming language like zig, having to write your compiler in zig is a great way to learn first hand what your users are complaining about. Normally if you dogfood your own creations, you experience them maybe an hour a day, but the compiler will be the number one tool when working on zig.
>A "heavy tweeter" is defined as someone who logs in to Twitter six or seven days a week and tweets about three to four times a week, the document said.

I wouldn't call that notably "heavy" tweeting...
> there are people to chat with on IRC.
> If the question is "Are there still people that use IRC?", then "Yes.".

That's a reasonable interpretation of the question. Even so, a lot of IRC communities have moved to Discord and such to lower the barrier to entry in participation.

The underlying question is more likely "Are the people I would chat with still using IRC?" which can only be answered if you know who the people you want to chat with are.
Each pod should have a clear leader.
We have an engineering manager and a product manager co-lead each pod.

So, 2 leaders is "a clear leader"? How does that work? Sounds contradictory?
I recently wrote a VS Code plugin to use GPT-3 for text completions and editing of text using instructions [1]. The main intention was scientific writing, but I didn‘t find it particularly useful until now, unfortunately.

[1] https://github.com/davnn/assistant
ClickHouse is almost ubiquitous for web analytics services.

For example, here is news from today about Splitbee: https://news.ycombinator.com/item?id=33334104 No surprise it is using ClickHouse: https://splitbee.io/blog/new-pricing
dupe: https://news.ycombinator.com/item?id=33333695
I think it when it starts having a broad impact on the way we live, like the internet and smartphones did.
Spotify Wants to Get into Audiobooks but Says Apple Is in the Way
Penalizing links algorithmically this way could be fodder for antitrust cases?
Have you used TypeScript? Not only is it better type system than Kotlin, it has great IDE support in VSCode, AND there’s a language server so you can get IDE support in Emacs/vim.
The Crude, ‘Completely Nuts’ Charm of Conker’s Bad Fur Day
Doomworld forums are a good place to find the current doom community folks.
Lip reading always requires inference, though. Maybe tonal languages are more difficult as a general matter, but I imagine this particular context is highly amenable to reliable inference.