skysight-inc/HackerNews huggingface dataset:
A couple months ago I posted the "Implementer's guide to WebSockets" that I wrote, but it seemingly got shadowbanned. [1]

I wrote the guide with example code for people wanting to know how to implement the complete WS13 protocol from scratch, so you can try it out, fiddle around and modify it to your needs.

The guide is more in-depth and assumes that the reader is willing to read the RFC when they're stuck :)

[1] https://cookie.engineer/weblog/articles/implementers-guide-t...
Whether or not it has legs, at least this is an interesting idea.
EPNS (Ethereum Push Notification Service) is now live on the Ethereum mainnet
So it's only a coup if it's "aimed at stopping the constitutional process of formalizing a lawful election"? Why is the "constitutional process of" passing bills not protected?

responding to your edits:

>That's is quite literally what differentiates a coup from the others: A coup uses force and threat to unlawfully take control of the government.

But using force to prevent the legislature from functioning when they're not certifying elections is fine?

>Normal protests outside the Capitol are about influencing the legislative process, which is a completely different function of Congress. But even then, it would be unlawful to influence the legislative process by threat or use of force.

I'm specifically talking about protests that involve denying access to the legislature, not just a bunch of people protesting in the free speech zone.
How the grass leaf got its stripes
Being the copyright owner of a piece of OSS doesn't give you control over every location where that software is hosted. For example, the developers of Python can't update the Python package in Debian's apt repo, Debian decides when to pull in new versions. (And if they want to add custom patches.) This doesn't mean Debian is declaring ownership of Python, they're simply distributing it in accordance with the license.

Just because NPM allows developers to self-publish doesn't mean that's a guaranteed perpetual right, and it doesn't mean MIT-licensed packages can't be published on NPM against the developer's wishes.

Licensing code under the MIT license (or any common FOSS license really) is the wrong move if you want to control where your software is distributed, and by who.
Any subscription based password manager is holding your passwords hostage. Not sure why this is news.
it was a dry run. if you look at the column of ex army rangers proceeding single file up the steps, you see a very well trained militia. they didn't bring guns because the invasion of the capitol was a propaganda / psychological operation. to show marginal and sympathetic right wingers that this was all real, and happening, and to elicit a response from the government.

guns would have upped the ante on the core organizers and resulted in their decimation at the hands of local federal forces. This was just the beginning. from the angry anti government comments in this thread, their effort looks to be succeeding.
Quantity of death should have no impact on whether something is terror or not. 10 people died at Astroworld, that was obviously not a terror attack. If the Boston bombings had merely injured people instead of killed them--or even if it had miraculously failed and hurt no one--we would obviously still call that a terror attack. No one is going to be scared to visit the Capitol on January 6, 2022 or 2023, unlike how people were afraid to go to las vegas or the Boston marathon after the attacks.
The general idea of money that is hard to debase has nothing to do with bitcoin.
Not every town has fancy restaurants. Most places in America probably don’t have anything much “fancier” than a chain like Outback.
Yes, but the real question always is:

Who will make a decision as to what is considered frivolous.

Not to search very far, I consider trucks in US for non-contractor use to be frivolous, but I don't go around telling people those need to be banned.
Atlanta Braves | Analytics Engineer | Full-time | REMOTE

Baseball Development Analytics is devoted to using advanced technologies and big data to deliver insights into how our players can become better athletes and develop skills that will make them better players.

The BDA Analytics Engineer will be responsible for developing and maintaining pipelines to ingest, clean and integrate multiple sources of baseball data to assist in training and developing players. They will be a member of a remote-first team, collaborating with other members of BDA and the rest of the Braves organization. The position will report to Assistant Director, Baseball Development Analytics.

https://atlantabravesmlb.wd5.myworkdayjobs.com/en-US/Atlanta...
Reasons: Overuse of OOP, Devops, CD, Microservices, Java, Javascript, nodejs, github, webserivces etc.

Every of these things bring multiple tools, frameworks, design patterns, convention and standards, which are all hyped for a short time until everything breaks down under the additional layer of unmanagable complexity until the next hyped toolset is introduced promising to solve all underlying problem, but finally adding another next layer of complexity.

Later you can't can find anyone who can maintain codebase developed using a framework hyped five years ago.

Example for large, old, good, maintainable codebase suported by a large number of developers in the world: ABAP (Sorry, no github, no open source. And sorry again: Imperative language).

And the silver medal goes to............................: SQL.
PoW really is the tragedy of the commons epitomized. The only way it could be more on the nose is if mining literally required a random human being to die.
Apple does an awful lot of this as well, working to make things harder for businesses supported by ads and easier for walled gardens.
Good! Now if only the EU would mandate sideloading...
The author is using recursive queries to query authoritative servers, such as the "H" root.1 The whole point of querying authoritative servers directly, versus simply querying a third party DNS cache, (one would think) is to use authoritative nameservers because they are authoritative, not recursive (and they are not subject to TTL issues).

Authoritative servers are not supposed to accept recursive queries (RD bit is 1), they will just ignore the RD bit, and caches are not supposed to accept nonrecursive queries (RD bit is 0). Unfortunately one can find people on the internet who use DNS caches to provide "authoritative" answers. Regardless of the intent of the person using such a configuration (e.g., it could be intended to deceive or it could be merely for "convenience"), AFAICT that is not how DNS was intended to be configured.

For example, djbdns' dnscache properly rejects nonrecursive queries. Unfortunately, large public DNS caches run by third parties like 1.1.1.1, 9.9.9.9 or 208.67.222.222 will accept them. By contrast, 8.8.8.8 will not.

1. There is also the issue of using domainnames for nameservers instead of IP addresses. Doing so means the stub resolver has to do recursive queries to find the IP address of the nameserver. Thus the whole process of using nonrecursive "authoritative servers" actually becomes reliant on a recursive cache. For many folks, that means one that is run by a third party. The cache effectively becomes the source of "authority".

Here is how an example of how to find/check nameservers servers using only authoritative servers (no caches) with a stub resolver such as dig/drill/kdig/dnsq/dq:

#!/bin/sh
test $# = 1||exec echo usage: $0 domainname
# which is the fastest stub resolver. for me dig is much slower than the others. test this yourself
# uncomment the stub resolver to use
#DIG="dig +norecurse";
#DIG="drill -ord";
#DIG="kdig +norecurse";
#DNSQ="dnsq";
#DNSQ="dq -a";
if test "$DIG";then
ns=$($DIG $1 @198.41.0.4 ns|tr '\11' '\40'|sed -n '/ NS /{s/.* //;p;q;}');
nsip=$($DIG $ns @198.41.0.4 a|tr '\11' '\40'|sed -n '/ A /{s/.* //;p;q;}');
$DIG $1 @$nsip ns|tr '\11' '\40'|sed -n '/./{/AUTHORITY SECTION/,/^$/{/ NS /{s/.* //;p;};};}';
exit;
fi;
if test "$DNSQ";then
ns=$($DNSQ ns $1 198.41.0.4|sed -n '/ NS /{s/.* //;p;q;}');
nsip=$($DNSQ a $ns 198.41.0.4|sed -n '/ A /{s/.* //;p;q;}');
$DNSQ ns $1 $nsip|sed -n '/^authority:/{/ NS /{s/.* //;p;};}';
else sed -n '/^ *#DIG/p;/^ *#DNSQ/p;/^ *# uncomment/p' $0;
fi
exit;

198.41.0.4 is the address for the "A" root which I have memorised
People on the internet claim it is impractical to memorise IP addresses
I have found this is not true and knowing some of these numbers can be very useful when troubleshooting. YMMV
Another one I have memorised is 192.5.6.30 which is the "A" com/net nameserver
I can usually remember a 199.19.x.x org nameserver, too, such as 199.19.53.1
It's called "commoditization". Since programming is now a commodity, the barrier to entry had to be lowered in order to pump up the numbers. Growth at all costs!

There is still rock-solid engineering to be found, usually in domains where the stakes are high (for example, fintech), but anything web-related is best kept away from if one is allergic to bullshit.
Jony Ive fancies himself a wizard of design. Well, he dropped the ball when he decided to go with white text on a light green background. This is called low-contrast visibility and reduces accessibility for those with visual impairments.

Jony and Apple could have left a switch setting for black letters instead, but no, the Apple way is read white letters on a mid-tone gradient.

My last iPhone, I never upgraded it from iOS 6 because I didn't agree with this design direction, and I have to say it's a breath of fresh air using Android because you don't have to deal with a single guy making all the decisions for you.
Sure, every country on earth keeps their ethnic minorities in a barbed wire facility where they can't leave and are kept under watch by armed guards. Yes, very normal. Nothing to see here. Ignore the DOZENS of facilities with tens of thousands of inmates who have stories of forced sterilization.
Honestly, most (decent) older programmers I've worked with are dramatically more productive than most (decent) younger programmers I've worked with. Both in terms of functioning systems and in terms of lines of code.

They waste less time writing unnecessary duplicates. They waste less time writing, fixing, and troubleshooting bugs. Their code tends to work when it goes out the door, rather than requiring multiple round trips. And when they want to brute force something, they break out a small code generator / write a small tool and blow past multiple younger eng-years worth in terms of LoC... and that's before accounting for them having written the tens of thousands of lines of foundational code that the others are working within.

---

edit: since the parent is more focused on pace than productivity... it applies to pace too. they're often spending far more (too much) time in meetings and mentorship and whatnot comparatively, so day-to-day pace can seem slower, but if they get a chance to focus they tend to be miles faster in every single way. Hundreds+ of working lines of code in a day is totally reasonable if that's what the problem calls for. It's why you see older engs disappearing for a week and building git. Or unix. Far from small projects by literally any measure.
> Not very clear at all, IMHO. Would you prefer that iMessage conversations didn't "interlink" with SMS recipients? Is that a better outcome?

Possible non-monopolistic solutions:

- an open standard for phone-number linked messaging.

- Allow any messaging app to assume imessage’s role and send/receive sms messages instead of the imessage app.

- separate imessage and sms into separate apps. As you pointed out, this is probably the worst option since nobody really wants this experience.

As for regulation:

“All general-purpose communications platforms with over 10mil users must allow and enable open access to 3rd party client developers and inter-platform communications gateways” - problem solved
Just that if that's your definition of domestic terrorism there's been a whole lot of it this year.
Looks interesting. The server would need to support receiving audio as a Chromecast device to effectively replace Google Home Speaker Groups.
There's also the failure of the Windows phone. So Microsoft bought Nokia, and are now subservient to Android.
Humans, as of now (and as far as I'm aware, being outside the AI labs at the big tech companies and DARPA) have agency, and so are in a unique position to take advantage of the uniform interface of REST/the web in a flexible manner. I wrote an article about this on the intercooler.js blog, entitled "HATEOAS is for Humans":

https://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.h...

The idea that metadata can be provided and utilized in a similar manner doesn't strike me as realistic. If it is code consuming the metadata, the flexibility of the uniform interface is wasted. If it is a human consuming the metadata, they want something nice like HTML.

For code, why not just a structured and standardized JSON API?

This appears to be what we have settled on, and I don't see any big advantage extending REST-ful web concepts on top of it. The machines just ignore all that meta-data crap.
Maybe Minecraft if you can have the savvyness to whitelist? If you just run a Minecraft server on the internet eventually folks will find it and mess stuff up. But if you curate who has access somewhat it can be a pretty fun meeting place online.

Edit: reading the rest of your comment I see that this doesn't exactly meet your 'voice and video' specifications. Apologies.
These threads truly put to test the typical HN claims about site and comment quality.

I’d argue that they’re off topic solely off of the description in the guidelines, but things have shifted so that the widest interpretations of the “on-topic” criteria are what determine that.
The semantic web failed to become widely popular because:

1. Graph databases on top of triple stores are a lot less scalable than relational databases or key-value stores, and this is how semantic data is meant to be stored/queried.

2. Data is valuable. Handing out data for free in a machine-consumable way is both expensive (machines can request data much more quickly than a human) and a recipe for copycats. The incentives just aren't there.

TBL's Solid project is about trying to separate semantic data providers from the presentation layer and opening up the possibility of payment from these data providers to try to improve the incentives around semantic data sharing.
It's not going to end until companies realise the waste or there are enough developers to satisfy demand.

Right now developers are in demand, they can charge a premium and they need to justify a career by filling their resume with accomplishments.

OSS (unmaintained or overengineered is fine) is unfortunately one of these.

This problem would be greatly diminished if we had small companies delivering value and getting paid based on that - thriving or ceasing to exists if needed. Instead big corps lead the way and pay politicians to complicate regulations and keep the status quo.

The bigger the corp the more it resembles a government: inefficient, full of useless layers and completely detached from actual performance.

Most engineers will live all their career in a place where their input doesn't influence much the success of the company and they will be awarded plenty of time to dedicate to new non-innovations.
See the post above this one. Lastpass allows me to deploy enterprise then link you can link personal that I can’t access. The user gets a single sign on to work and personal. It’s nice.

There was something else that BW wasn’t interested in doing for enterprise. I think that came down to recovery. They weren’t willing to trade some security feature on commercial accounts for a required IT feature. I wish it would have worked out with them, I’d switch from LP in a second if they solved those issues.

They were very upfront to me that their focus was consumer first.
Fond memories of watching that show.
Poisoning the water supply to increase the margin on bottled water is a valid business plan. Banning that is a good answer, and neither authoritarian nor fascist.
> How many messaging systems has Google had over the years?

About 20: https://arstechnica.com/gadgets/2021/08/a-decade-and-a-half-...
It can be, only for Android.
I'm really glad you mentioned PixiJS - that would be a very compelling use case for me! I formerly built a lot of casual 2D / 2.5D games in AIR. Pixi is my favorite screen graph library now by far.

The biggest thing I think the JS/canvas/WebGL ecosystem is really lacking, sorry to say, is the ability to compile to .ipa and .apk, with something like AIR Native Extensions (which worked along the lines of Phonegap plugins to centralize access to Android and iOS APIs in a common library). Cordova is dead and there's no replacement. And Cordova was never really meant for writing games. Something like this with WebGL support that just opened a full screen phone app running PixiJS - even with just minimal connectivity APIs - would be a great option for quickly building indie games.
The Restaurant Industry Has Always Treated Sick Workers with No Remorse
> AMD basically released this card 3 times now but this time they scrubbed the whole encoding feature set.

Do you not see the difference between GCN, RDNA, and RDNA 2?

At a minimum, this RDNA 2 6500 XT has raytracing cores that the two previous versions do not have. I'd assume that most video gamers care more about the raytracing feature (especially as more and more games are using it) than H265 encoding.

Remember: Raytracing instructions were invented on RDNA2. The 5500 doesn't have it, and the 480 doesn't have it.

-------

I mean, seriously. Would you rather have the existence of this card? Or the non-existence? If you want something faster, that's why the 6800 exists. This 6500 XT is for people who want a barely-gaming ready card at the cheapest possible price. If that's not your use case, then don't buy the card.

But every now and then, I build a computer for a child who doesn't play many video games, or for some uncle/aunt who doesn't know much about computers. I never like the idea of going iGPU only, because these people inevitably find at least one weird game that they like to play. So I like to put in a $100 to $200-class card in there. Not expensive enough to break the budget, but high enough that it'd perform decently on 10-year-old games and maybe a few indie-games.
> I wouldn't want an adversary to know when or with what severity I am commanding my nuclear force.

Usually (when the primary potential enemy is an opposing superpower held in check via MAD), you either want exactly that (as a palpable thread signal to get the other side to back down in an escalating crisis, or as the palpable absence of such a signal when you are just doing routine exercises) or MAD has completely failed and we’re all going to die.
That's a great perspective, but are those peeps writing the unused frameworks just wasting their time to solve a question nobody has asked?

Take the D language, it's basically a poor man's Java, with a shoddy garbage collector and aspirations at being C/C++... Is that the work of heroes or the misguided?
I can't decide to use Rust at my current job, but there are a lot of people on HN for the last ten years telling me that I'm doing it wrong with memory-unsafe programming languages. I still think this is interesting and useful information. Perhaps if I'm making a new company or starting a project, I might choose Rust if it makes sense for me.

A way that I look at Newport's writing is, he's making claims that most organizations are leaving money on the table by not adopting better work methods. I can't unilaterally go Newport-style at my current job. But this is a forum with lots of entrepreneurial people on it, and maybe someone would like to test his theory and smoke the competition by starting a company that values Deep Work/Slow Work/etc.
There are plenty of other wasteful activities that should be limited as well.

Classic whataboutism. First of all your entire comparison makes no sense, you have to compare alternatives for use. What's the alternative to a dryer. Using a line and hanging your clothes. Fair enough, what about in the winter in New York? A ventless dryer? Doesn't use substantially less energy. And so forth.

For every conceivable use case there exists alternatives that use orders of magnitude less energy. NFTs, sending money, federated computing, you name it, something already exists.

The only reason blockchain is a thing is because cryptocurrencies are booming in terms of how much they're sold for. The end.
Just because terrorism is stochastic doesn't mean it shouldn't be addressed. The mustache twirling villains don't exist and if they do they're not breaking laws, just adjusting mindshare.
Can a Neural Network Ace an MIT Math Exam?
You haven't tried getting rid of iMessage after embracing it: it's a nightmare.

It's like a zombie dog that will follow you whatever you do, and will keep eating messages sent to you again and again. There's an ecosystem of tutorials online to go the right step to minimize the effect (e.g. https://www.cnet.com/tech/services-and-software/three-steps-...)

That doesn't look like a "Apple did no wrong" situation from any angle we look at it.
> Graph databases are necessary to implement semantic web databases.

This just isn't true, on multiple levels. RDF is an interoperability standard that does not per se depend on a 'graph-like' data model - you can very much expose plain old relational data via RDF, and this is quite intended. Additionally, modern general-purpose RDBMS's support graph-focused data models quite well, despite being built on 'relational' principles - there's no need for special tech when working with general-purpose graph models, unless you're doing some sort of heavy-duty network analytics.
It might depend on the person.

When I was 14 with a Minidisc I had around 15 discs I’d regularly listen to. Couldn’t afford any more.

Later I expanded to a ~300 CD collection which I also put on my iPod.

Now I have access to a gazillion songs, but my Apple Music “library” is still less than 500 albums.

I spend 95% of my listening time with those 500 albums. I have never asked for or sought any “suggestion” from the Apple Music app.

However in case there’s something new I want to listen to (I read a review, I heard a song on TV I’m interested in) I have it right there, legally in perfect quality. Don’t need to buy a CD and rip it to iTunes and send it to my iPod or worse, record it in real-time to a Minidisc.

So I’m still not convinced I’m currently “missing out” on anything from the 90’s/00’s.
Mainstream went from C, to C++, to Java, to JavaScript.

If you have written GUIs in C/Win, C++/Qt, Java/whatever, and JS/React (or Vue) you should have an idea of what went wrong. That's just GUIs.

Bad code is always going to happen, when you make stuff will you regret some choices. That's a given. But at what cost you can refactor your way out depends a lot on the language you have used.

Now there are languages that make it harder to create a mess that is hard to refactor yourself out of. They are languages to, you could say, optimize for refactoring by using strong typing. Rust, Haskell, Elm, OCaml/ReasonML/Rescript, Kotlin to some extend.

But non of them are mainstream.

The IDE assistance I got with refactoring C++/Qt in 2001 is still miles ahead with what I get with JS/React (or Vue) 2022.

I recently did a Elm app on an automatically generated GraphQL API on a PG db with Hasura. I could auto generate typesafe bindings to the GraphQL schema in Elm. This was the first time I felt C++/Qt (or Ruby/Rails) kind of next-level powerful again. Type safety from db schema, through the API, to my frontend/UX code in strongly typed Elm.

So I think it is improving, but not so much in mainstream languages.
Also up in places that haven't been actively curbing their police forces...