skysight-inc/HackerNews huggingface dataset:
I think it's great selfhosting has caught on again. I've been doing it since the 1990's. I host multiple low bandwidth domains on my old laptop over a Wireguard tunnel to my cheap AWS Lightsail instance for $3.50 with 1TB trasfer built in. Also I've hosted my own email all that time so I always have an alternative to Gmail or others (Gmail is good but I like options that I control). I host a custom service I wrote and run in Docker as well. I can and do use AWS services like Codecommit and am looking into others but for control; Selfhosting is where it's at.
It’s a fee, not interest. Interest is charged over time (either compounded or uncompounded, either way you pay more interest if you take longer to pay off the loan). Here they’re charging a onetime 50% fee.
What a plot twist! Thanks for sharing.
Only tracks a small number of sites, however.
> A big part of why I'm saying "I don't need a VPS anymore", is because I'm also saying "I don't need dynamic sites anymore". I've been building dynamic sites for two decades (once upon a time "original LAMP stack" PHP + MySQL, more recently Python + PostgreSQL). I honestly never imagined that static sites could one day compete with that. But times have changed, and the JAMstack of 2022 has all the functionality you need.

This IMO should have been the main point of the article, not VPSes. No one can argue that a maintaining a live website is better if a few HTML pages will do.
yeah it turned into bizzaro world for a few months, which was especially weird since we were basically Covid free for the majority of the past 2 years.
For topics france24.com seem
reasonable for me. I’m interested
mostly international topics.

Clear title and short description
no bias listed vertical I prefer.

Wish there is (like reader view)
a browser built-in for
view facts, opinions, what others
are saying —- as researched
expressed by the author of each
article.
You should already be using continuous integration, so it should already be moot.
Very uplifting. Thanks for sharing this.
Magic in the Tiles: I was going to quit playing Scrabble competitively
Bummer. What an unfortunate comment.

Many people in the Python GraphQL ecosystem are very aware of how much I pushed that ecosystem forward (in fact, I created it!) and actually cheered for the success of Quiver [1]. Probably downloads will speak louder than any words: Graphene has 1/5th of the downloads of Django (~1.2 million per month [2]), all on the spirit of an open community that is governed by many more people than myself.

If you want an open alternative to Quiver, you can start by investing your time creating it. But you are not entitled on other people's time doing it for you for free. As people say in the US: "Put your money (or time) where your mouth is".

[1] https://news.ycombinator.com/item?id=17568848

[2] https://pypistats.org/packages/graphene
When you say "kid" do you mean teenage or younger? I was 39 when I started-out with Perl and server-side programming.
This is something I’m fascinated by, but know I’m not going to win by argument: actual, good reporting is very expensive. People spend money on so many things, but for some reason there’s resistance to paying for news. Why??
Used this before their rename, it's the good shit.

Great for flowcharts, at least that's my use
I felt sad when I read all the "No more ..."'s then saw the cartoon and text parodying religion in a pejorative context and was done reading.
There was a hype on serverless, so a lot of people here on HN is a bit allergic on them and tell ‘an EC2 instance is all you need’. And it’s not wrong — I’ve seen seriously over-engineered serverless systems with so much AWS-specific code. But a few years passed now a lot more services now provide (almost) lockin-free APIs that are pretty useful for simple.

IMO blindly recommending ‘just self host’, a sentiment that I see a lot in HN isn’t a good answer.
From my point of view, you're the one putting forward an unclear statement. I understand what the author is saying clearly ("only humans developed language"), regardless of whether I agree or not. I can't guess what you're referring to, though. Are you referring to non-human animals, to the different species of human in prehistory, or both? What kind of communication are you considering to be language? I may even agree with you, but your tone seems unnecessarily hostile.
> Why does it have to be 6 digits?

See https://www.rfc-editor.org/rfc/rfc4226#section-4 and https://www.rfc-editor.org/rfc/rfc4226#appendix-E.1

> Especially if it expires in like 5 minutes?

Usually it's 60 seconds. See https://www.rfc-editor.org/rfc/rfc6238#section-5.2

> And why can't we have some sort of centralised solution to all this?

So, Single Sign On (SSO)? Who do you trust to run the SSO services? Google, Microsoft, Facebook? Bring your own SSO (this used to be a thing that some sites supported, but it was too complex for the average user and too much support burden for the average site).

> The authenticator apps are probably worse than SMS in terms of the interface.

Worse how? These apps solve a different threat model (documented in the 2 RFCs mentioned above. Particularly note:

* HOTP Intro: https://www.rfc-editor.org/rfc/rfc4226#section-2

* TOTP Intro: https://www.rfc-editor.org/rfc/rfc6238#section-1

> I am starting to think the amount of manpower wasted on this globally is way more than the fraud preventing in terms of economic cost.

How would you quantify that waste vs the threat mitigated?

---

The general answer to why 2FA at all is that password hygiene is generally pretty terrible. Pretty much every "normal" (non developer / security professional) when you talk about passwords will say some form of "I use a different password for my bank, from the services I don't care about" [unspoken... which all share the same password]. My guess is that most people don't even do that. 2FA prevents the problem of I know Joe's password for ServiceA, so I can also get into Joe's account on Service{B..ZZZ}

---

The landscape of 2FA auth for each service that you rely on pretty much looks like:

* Use your own password storage

* without 2FA

* with 2FA (TOTP/SMS/email)

* Use Google/Facebook/Twitter/...

* accept whatever the user has setup for 2FA

* Use a third party service (e.g. Auth0)

* U2F / WebAuthN - newer stuff happening. I don't know a lot about these to talk much about them

---

Being security aware and practicing security hygiene is hard, but personally I'd prefer not to be the low hanging fruit when it comes to security breaches.
The term is “fee”. It’s a 50% lending fee.
“Life found a way out” would’ve been a nice title for this. :)

Edit: seriously, this is a fascinating account of how unexpected some life events can be, and then turn out to bring happiness that was sought but wasn’t expected.
>Public sector employees who abuse job security are treated like crap by the people who pick up the slack. Understandably, but not justifiably.

If you're seriously considering a job with a FAANG, you should be a highly valuable employee elsewhere.

I was assuming I was addressing someone who is capable of sheer talent and productivity for a high paying job, but instinctively knows that in an interview they will seem "off" and if they are lucky enough to get the job, worry about maintaining a good relationship with their manager.

>Find a smaller employer and make yourself essential.

I disagree, although I'm no authority as I've mostly avoided them. The smaller a company is, the more it's like a family, and the more family-style dysfunction there is.

A job in government or with a big company can allow you to transfer somewhere else if things don't work out in one department. And people are less personally invested.
U.S. Makes Contingency Plans in Case Russia Uses Its Most Powerful Weapons
Personally I'm entirely uninterested in having enough real estate to have 100 different things on screen at once. I'm very interested in razor sharp, highly-detailed typography and image display. Image quality over quantity. That's the appeal. 4k is almost there, but not quite. 5k is perfect.
It appears this article has its own Wikipedia entry https://en.wikipedia.org/wiki/The_Kekul%C3%A9_Problem
Yeah, I'm completely satisfied. The M1 Pro is definitely the best computer for the money I've purchased, despite it costing an arm and a leg to get more RAM and SSD space.

For my workload (music production), and despite still having to run Ableton through Rosetta, it can handle roughly twice as many tracks as my 2018 MBP (which luckily is _not_ something I purchased). All my previous "problem" projects now run perfectly. And this is all while running completely silently and barely getting warm compared to my 2018 MBP, which runs fans full blast and gets super hot if I so much as glance at Ableton. Can't say I miss the hiss of the fan when I'm trying to mix tracks.

If the developers of plugins I use all the time ever get their ducks in a row and finally get around to updating them to support native ARM (that's the current limiting factor), I imagine it will be even better.

Kind of embarrassing that it's taking some devs so long.. Steve Duda managed to get Serum updated within a couple months of the original M1 release.
Not to mention Delbruck's principle of limited sloppiness. I don't know the best single place to read about it, but reading around the top google results you get the idea.

https://www.google.com/search?q=delbruck%27s+principle+of+li...

The prototypical story is Fleming's nose dripping into a petri dish enabling the discovery of penicillin. If he was less sloppy that wouldn't have happened. But he was unsloppy enough that when something unexpected happened he paid attention and knew what it meant.
> Heartbleed proved that the “many eyes” theory doesn’t always work in practice. It was in the codebase for years and no one noticed.

It proved that FOSS isn't infallible, which I hope isn't that great a shock. To argue that it weakens the general argument, you would need to present a similar TLS library which avoided exploits by being closed source.
You're just completely wrong, and judging by your comment history, you have a huge bias against Elon Musk and Tesla so trying to have a real discussion with you on this subject is impossible.
I think the real feat is escaping Ukraine as a male. That is a story
The point here is not so much the M1 side, but the Graviton side - if you're developing on an M1-based Mac and comfortable deploying to ARM stuff anyways, you may as well go for it.

https://www.anandtech.com/show/15578/cloud-clash-amazon-grav...

Once you factor in the costs on AWS, Graviton2 crushes x86.
It only runs macos, so I'll definitely return mine.
It’s people like that who make me think tar and feathering wasn’t a bad idea.
The thing is I only picked on forms off the top of my head. There's a ton of functionality in your average client site which I can't imagine JAMstack catering for without it costing a lot more than hosting it on a VPS. JAMstack seems to cater for the painting by numbers model of web development but that's only a small fraction of what clients need. The JAMstack equivalent of a typical WordPress site, I imagine, would have to pull-in a dozen external services costing a lot more than the VPS alternative. Netlify make a big deal about the low-cost scalability of the CDN factor in JAMstack but it's only low-cost when you don't use external services. It's quite the opposite, I've heard, once you've outgrown static and need a third party service for every new feature.
It’s not helpful to calculate APY that way. After all, if they had made the maximum repayment period 50 years instead of 5 years that would result in a lower APY according to your calculation.

In reality the APY will be heavily dependent and on your income (as a high income will result in repayment period less than 5 years, while a low income will result in only partial repayment by the end of the 5 years).
Thanks for the link. I think it's very helpful, I was able to explain more complex algorithm with visual. Love the explanation on bias-variance and overfitting, I don't think I could get my point across without something like this to visualize my mathematical standpoint.
Thanks for sharing this lovely story! Our whole family was captivated as I read it aloud :). Congrats on the birth of your son and best wishes to all!
Most preppers live in a fantasy. It’s mostly an excuse to buy toys.

If you’re really interested in being able to handle situations, join the ultra-light crowd. They mostly beat preppers at their own game. It’s harder, less toys, etc, but if you look at people in situations where fuel (and thus cars) is a luxury, the first thing people do is shed weight.
So there's a difference between being able to handle emotions, and not feeling them at all. The point of a lot of these exercises isn't to desensitize you to these feelings, but to teach you how to recognize, process and deal with them. A lot of the maladaptations we have come from avoiding negative feelings, and sacrificing our long-term well-being to prevent ourselves from encountering them.

I'm sure there's training out there to completely burn out your amygdala and turn you into a psychopath, but I wouldn't assume that's what this is.
They will pay when they believe in and can identify with the source.
Nope. KiTTY came first, and the issue of name collision has been raised with the author of Kitty - https://github.com/kovidgoyal/kitty/issues/9
> I also think that "my site is free as in beer and also lightning fast" generally transposes to "my site doesn't have any traffic"

its more about being able to handle spurts of traffic and sustained traffic. these services are good enough to power whole communities and mobile apps. and that means it covers most use cases, as well as the placeholder websites that may launch a product once.

and by most use cases, we're talking about just the 99th percentile of high load intertwined ratsnest products not being able to handle it, but even then that's only because of an insanely high traffic load that is loading unique queries that are impossible to cache and this breaks view rendering - aka the bottleneck is still elsewhere.

with things that render quickly and have that view cached on the nearest CDNs, and that have giant memcaches of the queries that will be used, you really aren't needed!

fortunately there are many web services that are not designed that way, cannot be designed that way, but more so can't/won't be redesigned that way.
> I tried Github pages once…and pulled my hair out trying to get HTTPS working with a personal domain.

Last I checked HTTPs was available by default even on custom domains. I did have to remove and re-add my custom domain on a Github pages site that was created before this was the case. But after doing that, it was 0-config.
Here's caddy's go/tls wrapper with e.g. ACME, OCSP stapling: https://github.com/caddyserver/caddy/blob/master/modules/cad...

Django-ca also does OCSP and certbot-compatible ACMEv2 w/ known limitations: https://django-ca.readthedocs.io/en/latest/acme.html#known-l...

E.g. https://google.github.io/clusterfuzzlite/ is likely not so great at protocols because that requires testing concurrent and distributed systems and TLAplus, which at least currently can't find side channels FWIU.

https://github.com/secfigo/Awesome-Fuzzing#network-protocol-...

OSS-Fuzz runs CloudFuzz[Lite?] for many open source repos and feeds OSV OpenSSF Vulnerability Format: https://github.com/google/osv#current-data-sources
Welcome to target triples. It's usually called a "triple" since there's conventionally three components to the identifier, but in practice, there's often more (or sometimes less!). The point is to unambiguously identify a complete environment for a compiler toolchain. Unfortunately, it kind of doesn't.

Notionally, the base component of the triple is "architecture", "vendor", and "OS". So you might have something like sparc-sun-solaris--SPARC is the architecture, Sun would be the vendor, and solaris would indicate the OS running on SPARC. The OS itself might also incorporate specific version numbers, which can be helpful for the many OSes that do not guarantee ABI stability. This basic triple of identifiers format has a few issues by itself.

First, it's not sufficient to uniquely identify the necessary ABI. The most salient example is hard float (using hardware FPUs) versus soft float (using software libraries to implement floating-point)--this impacts calling conventions, so you need to distinguish which one you're using.

A second issue is with Linux, where the requisite C library is (unusually) not part of the standard operating system. So triples for Linux need to distinguish between which C library you're using as well. This means the OS field becomes linux-gnu or linux-musl among other things.

The distinguishing on C library was backported to Windows for some tooling, to distinguish between building on Windows assuming a standard Windows environment (windows-msvc) or relying on mingw's let's-pretend-Windows-is-Unix (windows-gnu).

As a result our triple is actually four units long, right? Well, the vendor field itself is kind of redundant, so it's not uncommon to omit that field altogether.

And several architectures have been around since approximately forever, resulting in a proliferation of architecture versions. Sometimes they need to be distinguished, so you have, e.g., armv7 and armv8 as different architectures, or i386 versus i686.

Since there's a lot of potential for confusion in such a flexible format, it's obviously important that there's a central committee for coordination. As such, there's an all-important mailing list where all of these issues are handled--oh wait, that's just my fantasy. No, there's no coordination, which means you'll invariably have different people and different tools coming up with their own unique ideas as to what triples to use for any given platform, and these are inconsistent.

Naturally, if you try to ask anyone to give you a list of all the target triples, even just a list of all the ones they support, the response is "sorry, that's too complicated."

So, welcome again to target triples. Be thankful it's not your job to deal with them, unless it actually is, in which case an ample supply of a strong beverage of your choice is recommended.
Could you publish the Dockerfile? When attempting to run train in Docker according to tutorial instructions I get "Cannot load library: java.lang.UnsatisfiedLinkError: /tmp/lightgbm[123]/lib_lightgbm.so: libgomp.so.1"

I logged into the container as root and ran "apt-get update && apt-get install libgomp1" and then training worked, but it'd be nice to be able to view/tweak your existing Dockerfile if/when needed. Thanks, cool project!
I don't understand how this is a race condition, but I might need to check my old undergrad textbooks though. Props for the quirkyness, though! :>
It shouldn't be... This is why HSMs exist.

See https://www.rfc-editor.org/rfc/rfc4226#section-7.5 and https://www.rfc-editor.org/rfc/rfc4226#section-9 for bidirectional authentication
You have to do that and much more. A "self-hosting" basic OS is a great achievement that I am not trying to downplay. However there really aren't any examples that I am aware of where that was achieved without relying on artifacts somewhere up the chain that come from an external source. I would say that achieving any self-hosting OS without relying on external artifacts is well outside one human lifetime. Edit: You have to completely manually bootstrap your hardware design and manufacturing simultaneously with your software.
I think you are misinterpreting the joke... it isn't pejorative against or parodying religion, it is making fun of tech companies handling security by just confessing security sins and then thinking that is enough.
> Wasmer recently recently released a closed source wasm package manager. Something doesn't seem right. Anyone feel something is off here?

I have to agree. Are there any open source package managers similar to cargo?
This is an interesting perspective, though I would argue that the internet has created superior substitutes. It's hard for me to see random encounters as entry points to friendship, acquaintances, or romantic partners, though I speak with a bias from living in a city. When buying groceries and running errands, I'm typically focused on getting in and out quickly; I'm not as receptive to talking with others. If someone is asking for directions, I'm willing to help out via Maps, but I'm also aware that the person might be trying to steal my phone.

Despite this, regular chance encounters are alive and well. You can go to the gym, hang out at a pub, or stay at a coffee shop. People are typically more receptive to speak in these contexts, all of which can't be replicated in a digital space due to the reliance on physical equipment (e.g. weights, exercise machines, drinks, and coffee machines). Martial arts in particular can really expose you to people of different ages, socioeconomic groups, and interests.

Outside of these, I believe that conferences and seminars are a good way to meet others, which the internet helps with. I can see technology making these in-person activities less intuitive (it's so easy to just spend time on social media), but if there's a will to see others, technology can help rather than harm.
Better bicycling in the public sphere is among the benefits of my relocation.

The folding bike improves the situation in my domestic life.

In general a bike is a both-and to an automobile not an either-or.

Each is a tool that is better for some jobs and worse for others. As tools neither is moral or immoral, virtuous or evil, inherently right or wrong.
With regards to self-hosting, https://selfhosted.libhunt.com/ could be helpful.

Disclosure - the founder of LibHunt.
Then it’s like giving away free gas. They probably want it at current market rates what ever those are 1000:1 1m:1 that will help remove excess rubles out of the system.
In the early 80's Australia also had the Microbee: https://physicsmuseum.uq.edu.au/microbee-computer
Sourcehut pages offers Gemini capsule hosting.

Edit: Sourcehut pages is the most direct parallel to Github pages but there's a bunch more options for free hosting listed on gemini://geminiquickst.art/ And that's not even mentioning the number of Tilde's that are configured to let you host Gemini content.
New Blog: React Redux Remix
Started a new blog to explore the ins and outs of our digital universe. Enjoy!
Literally the only thing an M1 MacBook would be useful for me is web browsing. The hardware is totally wasted by the OS. I have an Intel MacBook Pro 16, but the M1 MacBooks have an impressive GPU that's only useful for extremely niche applications. If Apple ever added Vulkan support which would quickly allow proton/wine/dxvk to work, it would be something to consider.
Yeah its a home button model. Really its just a fault of having to rely on touch screen inputs which become naturally less accurate the more hasty you are. Maybe my quick swipes aren't firm enough, or my hands might be too hot or sweaty, or too cold to register input, etc. I wish there was some way to map a physical button assignment to the camera short of having to jailbreak the phone.
It’s basically a proposal to do the same thing for private loans. Unlike the federal government, the originator of a private loan will care about repayment rates, thus somewhat aligning incentives.
Just trying to prove a point! I kind of enjoy discussing this things openly.
I have the air and the pro. The air is plenty fast but can be difficult when you have large RAM consumption use cases such as doing front end workloads. It also can have some visual lag if you’re plugging into a larger monitor.

The pro, though very fast, can also hang when leaving too many apps open. But I did leave way too much running. It feels blazingly fast.

You should really think about that workloads you will use in the day to day. And also consider if you’re docking it. If you are, the pro is a much safer bet and the screen brightness and size is less relevant.

So the tldr is that the 64Gb of ram is the big differentiation. The other is plugging monitors into the pro.