skysight-inc/HackerNews huggingface dataset:
Unfortunately it didn't draw any attention when I submitted it here, but I found this Twitter analysis of the impact of deplatforming ISIS quite interesting.

https://twitter.com/AmarAmarasingam/status/13481478677399756...
> And that "free software" licences especially the viral ones exemplified by GPL/AGPL are also still relevant in 2021, and having chosen one of those would have given Elastic.co what they claim to be demanding... (I think I agree there too.)

I think we agree up until this point, at which you fall into a trap. This is the same trap I was trying to avoid by giving my SSPL scenario above.

A copyleft license like GPLv3 does not prevent a business from operating a SAAS business.

AGPL would apply, but it only triggers upon modification. So as long as Amazon doesn't modify Elasticsearch itself, they don't have to publish anything (because there's nothing to publish), and if they do modify, they have to share just those changes. Which is very fair to me from a copyleft perspective.

Now SSPL tries to go further and say for merely using the software in a certain way, you must release not just any changes to the software itself but also everything around the software. That is what makes the SSPL neither open source nor free. (I guess I don't actually know how "free" is defined, so I can only say for certain that it's not open source, but I don't think SSPL even counts as copyleft)
There are countless different flavors of Petri nets. The edges can be weighted, meaning that a transition can get more than one token from a given input place to fire, and can put more than one token in a output place when it fires.

About the choosing which edges they follow: You don't. In standard Petri nets firing is concurrent: If tokens can be used by more than one transition at the same time, they will non-deterministically go one way or another. You can actually refine this situation by extending your formalism, e.g. to timed nets.

I am not an expert of neural nets, but I'd guess they are more similar to signal flow graphs. These are related to Petri nets tho, but in a very deep and complicated way that I have no chance of explaining here right now. Check out the work of Sobocinski, Piedeleu and Zanasi about additive relations if you are interested in this!
Pleasantly surprised to know Tucows is a thriving internet company.

Nostalgia overload. I remember downloading so much stuff from tucows.
Do you work with blind developers on building this at all? I know that HN has had a few big threads discussing the workflow for blind programmers, I would feel like this could potentially be a part of it? Assuming stutter could be interpreted to another language?
Thanks for the fix! I also changed the title of my blog to remove "VR".

Too bad Twitter still doesnt have editable tweets :/
I know this isn't going to help, but:

When I use Open Source (capitalized) I am arguing for Libre software with the values Stallman is talking about. The point of disagreement I have with Stallman is this -- Stallman argues that using the 'wrong' word to describe Libre software risks corrupting the movement. I argue that using a generally accepted word to describe the movement, and culturally reinforcing the common understanding of that word as a subset of Libre (ie, not just giving up saying "Open Source can mean whatever the Mongo devs want it to") is valuable enough to override those concerns.

Stallman goes on to argue that the Open Source movement doesn't care about Libre software, and we should not align with that movement. I argue that a very large contingent of the Open Source community does care about Libre software, and it is worth advocating to the remainder of the community that Open Source software is Libre software and that the real ideals of Open Source beyond just source availability can not exist without the ideals of Libre software.

Stallman and I disagree about whether or not we should use the term Open Source to describe Libre software, but we don't disagree about what Libre software is. Even Stallman admits that aside from some minor differences, the official OSI definition is mostly in alignment with Libre software. What Stallman is really disagreeing with is with the PR strategy. And the reason I'm not going to try and separate those terms is because I explicitly disagree with him that his strategy in this specific case is helpful, and because I and many other people in the community want to continue to fight for the idea that Open Source needs to be Libre.

Part of the reason we use Open Source to describe Libre software is because we don't believe that Mongo or Elasticsearch have the right to decide for us what Open Source means, and we're not willing to drop the issue, give up all of the good will and public recognition we've built around the term, and just go use something else that the public doesn't recognize. Because if we do, and we have any success at all, then pretty soon proprietary companies will start to co-opt that term too.

I don't see any indication that confusion over what the OSI meant by the term 'Open Source' is the reason why Mongo felt emboldened to write a new license that took away user freedoms. Mongo didn't argue that Open Source was different from Libre, they attacked the very spirit of both movements by implying that their focus on 'sustainability' and 'fairness' was somehow fixing flaws in the OSI/GNU definitions and making their software even more free. If we were all using the term Libre instead, nothing about Mongo's PR strategy with the SSPL would have changed, they would have still claimed that their license was reinforcing the 'spirit' of Libre software.
Agreed. Much less of a Mensa syndrome going on.

I remember at the peak of the 2016 post-election meltdown the SSC subreddit hosted a sort of "ask Trump supporters anything" thread. Despite the absolute insanity of the time and only a minuscule fraction of the sub's readership supporting Trump, the conversation was interesting, calm and uniformly civil.

There were a few Social Justice types that used to comment there too; again, all very civil, although there was sometimes the sense that they were regarded as an interesting zoo exhibit.
We don't assume guilt until proven innocent
tangentially, your point about meaningful shades/colors breaking the design for non-color-blind people situationally is a great example of the need to always keep accessibility in mind
I am guessing it is very location specific.
I work in this space, and it’s always interesting to see how others are solving similar problems—and exciting! Classical methods (under the auspices of “SPC”, alluded to in this post) are very outdated, but also, very ingrained in manufacturing circles.

I’m disappointed to see this only applied to a “toy” example...the real value is proven (or not, as is often the case) when the “rubber meets the road” and is applied to real problems on the factory floor. A POC like this is a nice demo, a fun exercise, but a long way from “productionized and used by real manufacturers.” The lack of a real example suggest to me this hasn’t actually been used in the field...

I’m also curious how one would communicate a very technical/abstract model like this to existing practitioners of eg Six Sigma. My experience has been there is a lot of friction in introducing new methods in such an old-school setting: not only do old habits die hard, but quality engineers are often hired explicitly to do particular six sigma analyses. The difficulty is in convincing a client that these methods (a) can be useful and reliable in the context of traditional methods, and (b) aren’t intended to replace their role. I’ve seen the most traction w methods that connect directly to established SPC procedures, while also pushing the limits of these known and _interpretable_ techniques.
This seems like a bad faith and easily broken argument. Point me to a single call to violence from Trump. Even Twitter’s own blog post about his ban couldn’t name a single example. Meanwhile the amount of economic damage and deaths from BLM related riots is much much greater than the recent Capitol riot. Based on what the standards for “incitement are, everything relating to BLM should be deplatformed. The fact that it isn’t is telling and a clear indication of double standards.
This is a common misconception. If the amount you invested is small enough that it doesn't matter, or that you can easily replace it, then the downside risk doesn't matter anyway.

If you wait long enough (and you should be investing for 10+ years from now) doing things that hurt growth doesn't risk you losing money, it guarantees it. And diversification hurts growth because of transaction costs.

Still, probably better to buy SPY.
I get nervous just thinking about the amperage necessary to add 300 miles of range in 10 minutes.
That's why I said write down the passcode and keep it with the device. The device itself isn't important because you're not keeping anything on it. Bitwarden encrypts everything itself. To my knowledge, once you enable biometrics in bitwarden, you will not need to use the master passphrase.
Japan’s 20 billion subsidy seems very low for the entire industry. I also don’t know if Toyota’s serious about mass production infrastructure needed to ship EVs (seriously).

Tesla is serious, and they are having trouble ramping up. These companies are not as serious, so how do they ever expect to ramp up when things get super serious?

Will wait and see, but these companies are in jeopardy of getting dusted unless they start shipping something this year, like the Ford Mach E.
:D I know especially John is very interested in finding an application of this stuff to solve modelling problems for climate change etc, but yes, this is not the content of this work ^_^
Are you saying that most software engineering jobs in your experience are about integrating existing projects rather than building anything interesting?
It's exactly the reality of modern fighter jets.

You're describing training flights, not combat missions. It is very common for aircraft to fly missions that are hundreds of miles long, most of which is over enemy territory. I used to sit in CDC on a CVN and watch the missions every day during Operation Southern Watch, which wasn't even really war -- but those pilots were flying over enemy territory for many hours every day.

Same thing in Afghanistan and Iraq, every flight was essentially over enemy territory for its entire duration -- surveillance, strike, and transport. You really don't want to bail out of an aircraft in the tribal areas if there's any way to get it home.

Modern aircraft are extremely reliable, they don't break often. Modern ejection seats are extremely reliable, they don't fail often. And yet, everything I posted above is exactly correct.
Why we chose Apache Superset as our data exploration platform
>So... you admit that the people who created the GPL decided their license wasn't sufficient to cover a certain usecase and revised it to cover it. But you think it's unfair to call this a "gap" that ES is now trying to close?

The gap in that case was that the GPL was not sufficient to ensure that software remain free software when companies started using SaaS for software that previously would have been run locally. SaaS was in effect a workaround for the GPL's distribution requirement (enabling companies to avoid giving the software's users the freedoms associated with free software), so the AGPL was created for software that was meant to run on a server.

This is different: the point of contention here is not that Elastic's software was being made proprietary (they could have easily used the AGPL if that was their concern, the AGPLv3 predates the first Elasticsearch release by three years) but that Amazon is using their software to compete with them. That's something that's pretty fundamental to both free software:

>The freedom to run the program as you wish, for any purpose (freedom 0).

...and open source:

>The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

Freedom 0 is a feature, not a bug! It may be a "gap" in Elastic's business model, but it's certainly not a gap in FOSS licenses - the freedom to use the software as you wish is a pretty core value of free software.

Now that said, I do think that taking FOSS and making it proprietary certainly does violate the spirit of free software. Amazon doesn't seem to have done that here, though - their fork is under the Apache 2 license.
Show HN: Curated 1:1 Clubhouse Matches
you can still have a shared base Image for your teammates, then use that base image to create a new image just for your .vimrc etc.
For a dead system with it's main disk mounted on a living one, on which the service is not registered, is it that easy?

I've never tried.

I like service files, but the rest not so much.
Personally, I think that meeting people has gotten a lot harder during COVID. For support networks, stasis is a good thing.
$50/hr for Ukrainian/Russian dev on upwork is reasonable. Ofc they make less since upwork takes a cut.
That’s quite a strawman you’re boxing with.
libpurple (the thing behind Adium/Pidgin) has plugins for a lot of the major messaging networks today.
Question then becomes: can YOU sell that work to 10,000? and how many can make what is sold?

I worked at a startup, became amazed at the sales crew’s ability to find buyers. I could make the app (and Co. could find few willing & capable to), but in no way could find anyone to fork over that much for it.
Sort of, it was/is built in to Chakra (the JS engine in IE9+, old Edge, and the original UWP WebView based on those browser engines) and hasn't been ported to the new Chromium-based Edge or the WebView2 based on it.

There's also a separate NodeRT projection for generating Node/Electron modules: https://github.com/NodeRT/NodeRT
There's no ads on patreon and it's more or less the same service as substack
Can anyone recommend reading about UX design for these kinds of combined digital/physical interfaces.
The place I work runs a heterogeneous erlang cluster (cluster-as-service-mesh), I assume the best way to deal with this is to mark off that module, or the specific cluster exports, to be ignored.

I imagine this tool also has a hard time identifying function invocations via erlang:apply
We found website testing inside a Docker container to be tough, so we still run Cypress on a native machine, but our web process is still ran within the Docker container. In CI, we use the default Cypress GitHub action which runs on the CI native system, and all of our servers are spun up with docker-compose. Source: https://github.com/NeonLaw/codebase/blob/development/.github...
But what percentage of Facebook activity was used for it within getting moderated vs what percentage of parler activity?
Agreed. This is quite insightful bit from kbenson. It explains well the mystery I was wondering for a while: why company wrote the code in the first place cannot compete successfully against others who supposedly have less expertise and has to rely on license change to defend their moat.

Software matures, and the expertise transfers to many other people while it matures. That shared expertise enters into public common for good. Natural and beautiful.
I would generally agree with this sentiment.
It's a fluoride-ion battery. Here's a 2018 article on that.[1]

[1] https://techxplore.com/news/2018-12-battery-concept-based-fl...
You always need something to live outside of your main disk encryption.

Now you have the choice to use grub for this or linux itself.

In either case both can be modified to do arbitrary things and corrupt later stages.

To prevent this you use secure boot, and if you want to do it right a custom platform key.

So now you either pack the Linux kernel initramfs etc into a single blob and sign it or do something similar with grub.

In both cases you should have a similar secure system.

But in my experience GRUB's functionalities in this area are not very nice to use and lead to slow boot.

On the other hand directly booting the signed linux blob without a bootloader is fast and smooth, but exposes what is in you initramfs, which normally doesn't matter.
as an addition to do this, we've found it easier to spin up the same exact environment for CI/CD.
I might have been downvoted for my views, but I note that Parler's preliminary injunction has been dismissed — of course the judge understands contract law and Amazon's AUP much better than the HN downvoters.

https://arstechnica.com/tech-policy/2021/01/judge-rejects-pa...
Recommended listening: https://a16z.com/2019/10/21/free-software-and-open-source-bu...
Different usage of reactionary.
SQL and VT100 have rather different capabilities.
> As a rule of thumb, WSL 2 accessing host (NTFS) files is about 5 times slower than WSL 1 accessing those same files.

https://vxlabs.com/2019/12/06/wsl2-io-measurements/
I wouldn’t be surprised to hear that it was originally designed to live in the bottom bezel of the screen, but that got cut due to aesthetic concerns. Seems like a more natural functional fit.
So thats about 5% of the total. Largest ones reach nearly 24k. Loosing a few is negligible.
Humans aren't rational. Anyone who claims they are, doesn't understand enough about the human condition to offer you any advice that you should care about.
This shakes me deep. Web 3.0 can't come soon enough.
maybe the best implicit punchline.

The rant about the joke was the joke.
I mean Twitter just removed Trump after the capitol riot and rest assured we're all asking why he got to stay up for the last 4 years too.

I don't think it's about being in the opposite political party. Facebook's users are more conservative than liberal. Twitter is constant screaming of all political affiliations. YouTube is famous for being the place where our relatives fall down the right-wing conspiracy rabbit hole. The thing that paints a target on your back is your platform being a landing pad for the people banned from other social networks and basically nothing else. I don't care how conservative you are Goat was a cesspool. And it wasn't because the people on it were conservative but because it was where people too vulgar for Reddit went. /r/popular might bleed dark blue but Reddit hosts plenty of active conservative communities that aren't /r/TD.

The argument "we have law enforcement are courts for that" is disingenuous as best unless you want the gov't to start employing hundreds of thousands of internet cops tied into the moderation tools of every platform. Without platform moderation there are literally zero practical consequences for online death threats, harassment, hate speech. It just doesn't happen. There is no one to call. Your local police won't take you seriously and have zero power to do anything even if they did. In spirit I actually agree with you but saying "throw it to the legal system" without any plan to make it work just feels like you don't actually want any moderation and know that this would accomplish that.
Sure, of course. They're still both free software, they're still both used by companies who aren't paying for Red Hat subscriptions, there's no shortage of consulting companies who will provide support for CentOS or Fedora like Red Hat would for RHEL, etc. That's the point: Red Hat has plenty of competition, including from others using their own software, and that's fine!

EDIT: And honestly the fact that Red Hat owns both makes it extra clear that they're fine with it, because again, they're a company built on free software.

Well, before the IBM acquisition anyway. We'll see where things go from here.
Just a thought after having read through the comments, not all emergencies are the result of death, and, since pretty much any textual information can be stored in a Bitwarden vault, the kinds of emergencies could vary widely. A well-thought out use of the share/collection features might mitigate a lot of "emergency" situations though.

I do, however, look forward to the clichéd "you had her change the will just days before her death" in murder mysteries being replaced with "you signed her up for Bitwarden's emergency access just days before her death"…
I don’t agree with you, but you sound like a textbook example of the modern left.
> The reason is that the mirrors are expected to fail after the same amount of TBW

You could fix that by writing a bit more to one of the disks, e.g. run badblocks for different amounts of time before putting them in service.
SWE often make more
Tesla is screwed.
Great comment.

Just to add a bit more nuance, I think we tend to focus a lot on community contributions, but IMO the biggest benefit of FOSS is not that; it's adoption.

Even if Elastic writes 100% of the code, by making it open source, they are promoting the widespread adoption of their software. A project with a non-free license or a custom license is a non-starter at many (most?) companies, or at a minimum requires talking to legal which is a PITA.

So, even with no community contributions, Elastic would never have been able to get to where they're at now - making $500MM in revenue a year and at a $15B evaluation - if it weren't open source.

Now just to be clear, Elastic is totally allowed to close things up now that they've reaped the benefits. The beautiful irony is that, when you close source after you've reaped the benefits, by definition you've also hit the point where it's now obviously beneficial for a company like Amazon to make their own fork and keep their AWS Elasticsearch cash cow going.

So, ultimately the community is totally fine. Indeed Elastic has been going down this road for a few years now, so it's actually a good thing for us that this happened. Better to have an amicable divorce early rather than a messy one later. But I can't help but point out that Elastic has broken its promises and misled the community - to their detriment more than to ours.
Here comes the difference between GPL / AGPL and dual licensing, and the easy BSD / MIT licenses.

Linux is GPL2, and there can't be a closed-source fork. FreeBSD is BSD, and see how widespread it is, in comparison.
Toyota is in a much better position than E.U. or U.S. manufacturers, except for Tesla.

In the early 00's, the EU introduced emmissions regulations focused on Carbon, which didn't take sulphur into account. That's why Volkswagen and others like Mercedes focused so heavily on small diesel turbo engines, and explains the 2005-2010 or so diesel vehicle boom.

American manufacturers mostly just made big gas sonking vehicles running on petrol

Japanese manufacturers developed the Prius and other hybrid-electric products and were early to the game. Remember that the Toyota Prius Hybrid Electric vehicle was released in 1997. 1997! They currently sell four million units a year of Prius alone, and definitely have the knowledge + capacity to mass produce EV's
This comment is just like one of millions of FAKE REVIEWS on AMAZON. They do what they do best.
Thanks for the link. I traveled on the Cory Choeust multiple times during the late 80s, though not on Heard island test. Very interesting working on SONAR in the 80s, both on surface ships and subs. Riding alone in the conning tower of an SSN in Exuma sound was fun. And saw a full rainbow in north Atlantic
disclosure: I work at AWS

You're not required to contribute with your amazon e-mail address, and I see a lot of people who don't due to inertia or because they want to avoid tying their identity their employer.
I mean I was an embedded C dev, I "integrated" a compiler, an x86 chip, and a bunch of proprietary hardware. All software can be described as a kind of glue (luckily glue can be interesting lol)...
Is it better than AWS’s implementation?