skysight-inc/HackerNews huggingface dataset:
I do both within the same app (Obsidian) with some plugins, so let me explain the difference from my perspective.

Wiki, in my mind, is more suitable for somewhat long and detailed notes about concepts. Random titles from my notes: conspiracy theories, neoliberalism, borders, norms, monopolies, habits, addiction, time management...

Zettelkasten is kind of the opposite of that. It's more about making connections between concepts than thoroughly researching certain concepts. Random titles from my notes: news kills creativity, inequality generates status anxiety which generates ecological damage, relationship between paywalls and echo-chambers...

These connections made in zettelkastens have no place in a wiki page because the point of wiki pages is to have a somewhat detailed explanation of concepts. Zettelkastens are much shorter (usually between 5-10 sentences and 1-3 sources).

Another way to look at it: zettelkasten is for stuff that you write once and rarely have a reason to expand upon (other than to create a new link to something similar), while wiki is for stuff that you know you're gonna have to return to with the goal of adding more stuff.
Absolutely. Again, I’m not choosing a side here, just trying to observe phenomena. My own politics don’t fit neatly into a box.

I think one could accurately describe both as explosions of long-standing resentment, legitimate reasons to be upset, and lack of trust in institutions, finally ignited by social media making it easy to construct exaggerated or outright false narratives.
TSMC to spend over US$15B on 3nm process in 2021
Main menu but also in game UI. Ability timers, weapon reticles, health bars, etc.
We seriously need to break up Google. This is a chokepoint for innovation, should not be controlled by one company, and has serious downstream consequences on economic growth as a nation.
It should just have been File not found without anything else by the logic presented in the article.

However, there are some problems with entire thinking:

- When you are looking into results of larger set of operation (i.e. scripts) you may need more info to easier grasp the context

- Did you see it already ? There is no need for verbosity once you experienced a problem recently (which is what happens most of the time)

The errors deserve both variants, short and terse, just not on the same place (I don't want spams in terminal or logs). Short variant should provide some form of id that can be looked at for more details:

cat(e123): file not found

e123 could be searched in detailed error message document.
Imagine a future where multiple big tech companies share “blacklists” of individuals and applications that should be banned across their networks. Your entire business and digital life could be snuffed out in an instant. Already seen it happen, now it just has to scale.
Gaddafi's Oddest Idea: Abolish Switzerland
Author here.

That is definitely a good idea, and I recommend it. But that should not be the main takeaway.

In our particular case, that was not found to be the problem (we think it was some sort of false positive), and there are valid reasons for users to do that anyway (upload a phishing email attachment onto an IT support ticket, for example).
Too bad (I use Ubuntu's Chromium): I don't use sync, but I'll miss the Google Translate feature in Chromium.
In this case, it "really means" picking candidates who will not lie to their supporters and inspire a violent uprising against congress in an attempt to stay in office.

I'm not proposing a rigorous test here which all candidates must pass. I'm pointing out that attempts to finger "digital media" as the root cause of the problem are flawed, and the much simpler reason (albeit less palatable to half the electorate) is simply that we failed to choose a grownup for a leader.
Unless maybe it was somewhere I knew people well, I'd be very hesitant to switch jobs in a situation where I only had communicated virtually--unless I had no choice in the matter.
> personal attack on this woman with the intent to humiliate and embarrass her professionally.

This is exactly what it feels like to me.
After years of seeing developments like this, getting worse and worse, it fills me with rage to think about how clearly nobody in power at Google cares.

I naively used to think, "they probably don't realize what's happening and will fix it." I always try to give benefit of the doubt, especially having been on the other side so many times and seeing how 9 times out of 10 it's not malice, just incompetence, apathy, or hard priority choices based on economic constraints (the latter not likely a problem Google has though).

At this point however, I still don't think it's outright malice, but the doubling down on these horrific practices (algorithmically and opaquely destroying people) is so egregious that it doesn't really matter. As far as I'm concerned, Google is to be considered a hostile actor. It's not possible to do business on the internet in any way without running into them, so "de-Googling" isn't an option. Instead, I am going to personally (and advise my clients as well) to:

Consider Google as a malicious actor/threat in the InfoSec threat modeling that you do. Actively have a mitigation strategy in place to minimize damage to your company should you become the target of their attack.

As with most security planning/analyzing/mitigation, you have to balance the concerns of the CIA Triad. You can't just refuse Google altogether these days, but do NOT treat them as a friend or ally of your business, because they are most assuredly NOT.

I'm also considering AWS and Digital Ocean more in the same vein, although that's off topic on this thread. (I use Linode now as their support is great and they don't just drop ban hammers and leave you scrambling to figure out what happened).

Edit: Just to clarify (based on confusion in comments below), I am not saying Google is acting with malice (I don't believe they are personally). I am just suggesting you treat it as such for purposes of threat modeling your business/application.
I dunno, I see a lot of react codebases at my day job, and my experience is that libraries are all over the place. The really popular libs are often framework agnostic (e.g. lodash, date-fns, etc), but there's also a long tail of questionable quality libs: some react packages only work with webpack, some use unusual idioms (e.g. having to reference a node_modules path for some css, which doesn't fly with yarn 2), some are unmaintained, etc.

I've also seen cases where people were not aware that high quality vanilla libs exist, e.g. react-dnd vs dragula

There are a lot more wrapper libs for react, that is definitely true, but FWIW, I've come to despise them. Often you end up running into governance/versioning issues (e.g. one moving part releases a new version but you're stuck with the old one because a wrapper author doesn't have time to fix the breaking change, or are MIA, etc), or there are missing/broken pass-through options or whatever...
Interesting observation. I feel like I am like that - I hate doing anything that requires me to develop only a superficial understanding (e.g. messing around with Kubernetes configuration without understanding how it all works on a fundamental level). I also don't like systems that are hard to debug - I want to be able to make assumptions and test them, and that can sometimes be notoriously difficult with cloud-based infrastructure.
Possibly. It's not just the loadouts though. Reticles and health bars need to animate at least 30 fps if not 60.
But, left with fewer resources, Google's security might become like the security of smaller companies, and the crowd will be crying.
That, try to understand all the things that are not documented. Sure some projects may have written extensive documentation and all the options they considered and why the did what they did, but most of the decisions usually are not documented. Try to get into the mindset of those people and get into the conversation.
Collaborative notebooks to train, track, deploy, and monitor ML models
Show HN: Interactive CS Courses in the Browser
Jenkins at Scale
Author here. That was exactly our situation with the impacted systems. We got lucky with the fast "review" and it happened late enough in the day that only PST customers were impacted meaningully.

But still, quite frightening, hence the post. It's not a failure mode we had in mind when we established the SLAs.
The “special compilation” step is what annoys me as well. Modern JavaScript is powerful enough and almost universally supported enough to no longer need this. I’m looking forward to the day when we don’t have to use transpiled languages and preprocessrs for basic things.
Thank you for spending the time to write so far and for wishing me good health. I really appreciate it. I could tell about your background in your writing.

> what seems to have work for you does not mean that it will work for everybody else.

I agree with you on this. I just hope there was more funding or incentives for scientists studying this which, so far, has helped me and many people I know.
It's still there, it's just white instead of grey. Which works fine with the header, but disappears as you scroll.
There's middle ground with TS. Just allow implicit any and use JSDoc.
I think I conflate the two, and I'm not sure that's wrong. I've never seen anyone use Groovy outside Gradle. I mean why would you, if you had a choice?
It reads like SEO spam: a plausible collection of statements scraped from other articles and then cobbled together with no understanding. It's a shame that stackoverflow has sunk to this.
Sad. I have often switched to Chromium whenever a Chrome update was breaking various websites I used. Chromium is lagging a bit behind in repositories; some delay is enough to let the website owners update. Then I can switch back to Chrome for that site once again.

This has been happening more often lately, in my experience. Sure, you could say that the website is broken and not the browser. But from a user’s perspective, it used to work and now it doesn’t. Users don’t care whose fault it is.

But big corps don’t care if less than 0.1% of users are impacted. Even if that means 100,000 people. So it’s ok to break a few eggs.

As a website owner myself, I’ve had to make changes about once a year to keep things running properly in Chrome due to deprecated APIs. This is for a website that has not changed at all otherwise in 5 years, and I built without using any external dependencies so that I can avoid updating things.

Compare this with other environments: Windows apps usually can run for 20 years without issues; Linux apps even more. Not to mention document formats, like PDF, which are pretty much guaranteed to be accessible forever. Adobe got at least one thing right.

The only good thing I can say about this disregard for backwards compatibility is that it gives web developers good job security.
Generically any use of a vendor represents some amount of vendor lock-in since the reason why the vendor was selected often reflects some unique capability or added value of the vendor.
A self-hosted personal wiki sounds like a fantastic idea! Is it just a html 'pedia? How do you host the media? I would love to see the "How this wiki was built" page of your wiki.
No. [1][2][3]

[1] https://en.wikipedia.org/wiki/Sender_Policy_Framework

[2] https://en.wikipedia.org/wiki/DMARC

[3] https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
Ask HN: Why do you think Signal's service fell over with this week's user surge?
As of now, status.signal.org still shows that Signal is still struggling to handle the agreeable huge influx of new users. However, these are smart guys behind the project (perhaps their strength is privacy, not system scalability? doubt it though). The question is: why did this happen? Especially since WhatsApp's famous super-scalability with just a handful of servers.

It looks from their GitHub repo that the signal server is a Java project [1]. WhatsApp's "secret" weapon for getting such great scalability for so cheap was choosing to use Erlang. I would like to believe that this technology choice must have played a role here (not that people haven't build massively scalable apps with Java/JVM).

Now, why the slow response to increase capacity? Are they perhaps not running on a cloud infrastructure, where adding more servers to the problems is as easy as a few clicks (or zero, e.g. with k8s autoscaling and other such tricks)? Perhaps, again for privacy/control, they're running their own metal at a colo or somewhere.

Finally, could it be their clustering system works in a way that prevents them from just "throw more servers to the problem" and is rather more intricate than this?

I think all this may be a fun "postmortem in the dark" experiment :)

[1] https://github.com/signalapp/Signal-Server
For anyone who's interested, you can use this code for free access this week: KZV3PS

I'd love any and all feedback on the project :) We have a discord community if you want to join and discuss the project: https://discord.com/invite/QtSmHu2J
> I do business online
> Anyone who couldnt do that, like ours suffered.

I'm curious, what business operates online but can't move? Is it a company with large manufacturing that can't pick up and move?
Did you check if your public IP changes after this minute? I don't know if this still happens but back in the past my router did this every 24h to get a new IP.
Getting replacements for some of those older parts is hard!
Everybody gets a public key certificate, possibly since birth. There needs to be some way of establishing that which keys belong to which person, perhaps via some government registry, and a way to invalidate old/compromised keys. Overkill?
>> Personally, I would go with wikipedia, craigslist, twitter, internet archive, and a public search algorithm.

Well none of these should be public domain, since were created, and are run by, existing organizations. Going down the route of "if you become successful, you'll get "nationalized" and placed in the public domain" seems to be, well, not likely to get much support.

Of course nothing stops you creating a project, placing it in the public domain, and then driving the project, getting funding, attracting an audience, becoming a meaningful social good. (See SQLite as an example of this approach.)

But turning over existing, valuable, successful projects to a "Trusted Public Body" (whatever that is? trusted by whom? which public? .org debacle anyone?) is simply a good way to kill successful projects.

And that's before we get to impossible questions like "who decides what gets moved to public domain?" - the Greek government? Silicon Value investors? my mom?
Yes, I fully agree that a correct program can't contain memory bugs, and that we want the compiler to help us.

For a systems programming language though, I think Zig hits the sweet spot, and not only with regards to memory safety.

Correctness, in this realm, is as much memory safety as:

* error safety (making sure that your program correctly handles all system call errors that could possibly occur, without forgetting any, and there are many! The Zig compiler can actually inspect and check this for you, something not many languages do), see https://www.eecg.utoronto.ca/~yuan/papers/failure_analysis_o... for how critical error handling is in distributed systems,

* OOM safety (making sure your program can actually handle resource allocation failures without crashing),

* explicitness (clear control flow with a minimum of abstractions to make it easy to reason about the code with no hidden surprises, no weird undefined behavior),

* and especially as much runtime safety as you can possibly get from the language when you need to write unsafe code (which you will still need to do when writing systems code, even if your language offers memory safety guarantees, see https://andrewkelley.me/post/unsafe-zig-safer-than-unsafe-ru...). Here, Zig helps you not only at compile time, but also at runtime (and with varying degrees of granularity as you see fit), something not all systems languages will do.

On all these axes, Zig is at least an order of magnitude more likely to lead to a correct program than C, while optimizing for more readable code (even for someone coming from TypeScript) and thus code review, also essential for improving the odds that your code is correct with respect to its requirements.
Author here. I don't think it's malice on their part, but their hammer is too big to be wielded so carelessly.
But they keep adding more and more ads. It started with the stupid reward-coin reminders, then ads on new pages, now the coin icon is constantly present in URL bar and on top of that they also show promoted news sites at the very bottom of empty pages (iOS).
Pretty sure the main point was a private company can effectively delist you from the internet without any rhyme or reason. Most of us have heard Google horror stories when you use their products the fact you can be free of them and have any new customers bounce from your sight in terror is uh, terrifying.

I would like to emphasize of course they have good stated reasons for warning users before accessing websites. The issue is that they are a private company whose behavior affects all major browsers and (for kicks) they have an extremely opaque review process.

If you ran a "divest from Big Tech" website which started gaining steam they could delist like this and the only real force stopping them is public backlash. If you think you can effectively sue Google to stop them I have a bridge to sell you.
And a touch sardonic.
There's a very obvious reason not to do that: if you apparently maliciously cry wolf a few times, people won't trust your cries any more, and, for example, other browsers might choose to stop using the Google Safe Browsing list.
A url containing 'harvard' and redirecting to an actual faculty website is going to convince most people if the communications are plausible. Many large organizations use multiple url forms for emails, especially for quasi-separate divisions like business schools or extension programmes.

A particularly sneaky scammer without access to Harvard mailboxes might register a plausible-sounding domain with an .ac TLD (which resembles the .ac reserved for universities in many national domain systems including the author's, but is actually a freely purchasable domain supposedly associated with Ascension Island)
This is not new; such things happened many times in the past (25 years ago Microsoft was the behemoth trampling small companies) and will happen again. I do not think Google is doing it consciously -- this is probably just collateral damage from some bot or rule.

The way to handle it is to reduce dependencies on the cloud. This does not mean cutting cloud services altogether, but once the company is big enough (and the author talks about 1000s SMEs and millions of users), plan for graceful degradation with a fallback to a different provider and another fallback to owned servers.

This takes work and reduces capability during the crunch, but it is often a lot easier and cheaper than people think if planned properly and not in a shotgun style of crisis engineering. My 2c.
> I think another take away from this article is “don’t allow users to upload malicious files to your domain”

I disagree, at which point did we all accept Google's role as defacto regulator and arbiter of the Internet? Why should we tacitly accept the constraints they deem as appropriate and modify the way we build the web?

In other words, those are our domains, our apps, our systems and we'll do as we please; that includes worrying about content moderation, or not.

When and why did we accept google as the Internet's babysitter?

Apologies if this sounds aggressive, but your takeaway reflects an appalling and quite fatalistic mindset; one which I sadly believe is increasingly common: big corporations knows best, big corporations say and we do, big corporations lead the way.

On the other hand, probably I'm just biased and tired considering how tiresome it's been to explain to my friends and family why Signal is the better alternative after the WhatsApp/Facebook fiasco.

/EndRant
> I consider this a bad behavior.

Part of it is probably that I fixed something that wasn't broken for them personally.

I understand than when a new person joins and starts telling you that you should now start using this "new", "Makefile" thing, you'd probably be annoyed and get back to work instead.
SQL is a number of different discrete things including:

- A query language

- A schema definition language

- A storage engine

- A server

You can mix and match the parts so it works for you.
On reddit there is a group of volunteers that describe images - /r/descriptionplease. Something like this, perhaps, with short video clips as you mentioned, would be a nice feature.
I didn't mean that. Simply, pharmaceutical companies don't have incentives to invest in drugs that they won't profit from. Expired patent drugs come off first on that list.
Trying to minimize the error message as the implementor is a dangerous game because nobody else will have as much context as you.
Rust error messages are widely lauded because they give context and help, not because they minimize character count.

My priorities for errors are:

- enough context to find the error and possibly further information

- consistent formatting so users can learn pattern recognition. Powershell is much better at this than Unix tools because the shell displays errors

- error message should fit on one screen and little but the relevant error should be printed after an interactive command

Terseness is mostly relevant for non-interactive use such as log files that need to be read quickly.
It would be more helpful if she uploaded screenshots of the emails, including the sending address, and pictures of the letterhead. Assuming she's telling the truth about everything this would be by far the most elaborate phishing attack I've ever seen.
My beef with operator overloading is googling symbols and when I can't inspect it with a language server / IDE. In Pycharm/Clion you can jump to the dunder definition of the operator. Haskell lets you get :info on symbols.

Google has gotten much better at handling symbols.

Basically, custom infix operators are super convenient as long as they are auditable and aren't abused.
Yep that was the correct interpretation! CEO being reasonable.
I really love the wrist friendliness of Svelte. Are there yet any good UI frameworks/libraries to use with it?
A part of my work tasks consists of reviewing answers to security questionnaires.

These are reasonable questions and I see quite a lot of value if they are filled out extensively and in a good faith approach. Most of the answers of usual security questionnaires can be deduced from the responses to this DSQ.

I really have a problem with Q6:

> Have you had any security breaches in the last two years?

> If yes: please explain the breach, and provide copies of any postmortem/root cause analysis/after-action reports.

Almost nobody will answer this truthfully. I see a couple of options:
1. There was a breach and it was public, then why are you asking. Do your research!
2. There was a breach and it was not made public. The company will likely not admit it to you.
3. There was a breach but it was a) not relevant to your case/b) internal/c) the data lost was not customer data/d) we forgot that there was/etc.

While lying in case of 2. might make the vendor liable (IANAL) they might be able to argue that 3 was actually the case.
> People used to share greatly embellished stories with oral traditions before written language.

Ah, this is a good point, thanks! Will
need to tweak my terms.
Being completely blacklisted is very bad, but u know at least that something needs fixing. Imagine if google partially punishes u and downrank you in the search for no reason. This is harder to figure out.
It took us several months to discover such a problem until finally we registered to google websmaster tool.