skysight-inc/HackerNews huggingface dataset:
I think your description of linting can be true, but not necessarily for every eslint configuration. I feel that I've landed on configs that feel useful to myself and the rest of the devs in the team. Even with a rule set that contains many rules that can look nit picky at first glance, no one complains since they are auto fixable, and fixing is a part of a commit hook.

There are a handful of rules that are nice to have in a TypeScript project to make sure devs don't do things that break type safety. Plus some that avoids mistakes from slipping through (even though the code is reviewed).

One thing I've found super useful is to have @typescript-eslint/ban-ts-comment enabled, but configured so that you can still use @ts-expect-error and the others as long as you provide a comment when doing so. This is so nice when doing code reviews, either someone has provided a very good reason for the exception, or it is clear that the same result could have been achieved with a better approach. Same goes for disabling eslint rules inline in a file, also allowed if commented. I feel that this is a very good compromise between being strict with linting, but also not letting linting get in the way.
I did find that `ffmpeg -i file.png -lossless 1 test.webp` could produce a full-res chroma image, recognized as WebP by file and opening successfully in Chrome and Firefox. I was under the impression this was not possible, but I suppose it is (today, not sure in the past).

Why do I see WebP as an image format used to sneakily degrade PNG files? I've seen gaming wikis and CDNs serve PNG URLs as lossy WebP, ruining pixel art and degrading color detail in 2D art. And Discord CDN's "file.webp?size=1024&quality=lossless" serves icons/emotes with chroma subsampling (and ffprobe doesn't say the file is lossless, unlike test.webp above).
Ambitious project, I'm sure you'll learn tons with it. Best of luck. :)
My partner and I are on a one year break from booze since July.

Which is great.

But as others mentioned. Meat, fried stuff, anything carbs, the list of stuff you should avoid to stay healthy never ends.

Same with interesting past times. Climbing, paragliding, street/ramp skating, horse riding etc. Much higher risk of injury or even death than with "boring" sports or no sports at all.

The issue I rather have with the topic at hand & the general discussion people have around it is that the comparably "healthy" substance alternatives are illegal and/or hard to come by.

That said -- we live in Berlin.

You can easily get pure MDMA delivered to your door. Testing kits can be ordered from Amazon.

A shop around the corner sells high quality (beautifully packaged) mushroom chocolate under the counter; in different strengths.

A legal shop down the road[1] sells a LSD variant that seemingly changes every six months, as the government adds the variant they're currently selling to the controlled substance list.

We found microdosing the aforementioned three, depending on occasion, is similar/better than having a glass or two of wine. With the added benefit that you can choose the substance for the occasion, for better effect.

Specifically MDMA for social gatherings and mushrooms for tango dancing (which is our non-dangerous favorite past time).
LSD for either, depending on mood or what we have on the shelf.
And yeah, I also use LSD microdoses sometimes when writing challenging code.

And while we admittedly were "a glass of wine or two a day people before" -- which seems to be the norm when you live in central Berlin --, we find that we take the above three substances only once or twice a week, mostly during weekends and always in isolation & microdosed.

For MDMA the reasons are obvious (although literature is not conclusive about long term serotine depletion even being a thing with MDMA when taking it strictly in moderate doses & in isolation from other substances on the resp. occasion -- we are just not gambling there).

For mushrooms and LSD the reason is simply that you don't want psychoactive effects at all.

Kinda why you avoid drinking a bottle of wine by yourself during a dinner -- you still want to enjoy talking to other people.

[1] https://maps.app.goo.gl/AzA9uvJx7NsxquvN8 resp. http://lsd.store
Wuffs and SkWuffsCodec.cpp author here. Wuffs' GIF decoder has shipped in Google Chrome since July 2021 (milestone M93).

A fair chunk out of that 1000 lines of glue code is adapting Wuffs' API to Skia's API. (Skia is the 2-D graphics library used by Chromium and many other projects). Specifically, GIFs can be animated, Wuffs' animation API is designed for sequential access and its state needs O(1) memory but Skia's SkCodec animation API allows random access and needs O(N) memory, where N is the number of animation frames.

Random access means that, after decoding frame 100, the SkCodec can rewind and produce frame 70 (by scanning backwards through its O(N) state to find the most recent I-Frame equivalent that's <= 70 and replaying forward from there).

Random access seems a bit of a weird feature to me, but Chrome/Skia's old GIF codec could do it, for whatever historical reasons, so the new Wuffs-backed one does too (even though it needed a chunk of glue code).
No it's the actual word. "google it" allows for a liaison between the two words because "google" technically ends with an l sound (a consanant) and "it" begins with with a vowel - "googlit". It's also a soft sorta rolling consanant, which helps. In the case of "kagi it", "kagi" ends in an I and "it" begins in an I. That means you have to make a hard stop between the two words and pronounce clearly to differentiate between one I and the other otherwise you lose the words entirely. The two words fail to flow into each other in any way, making them feel less like a pair. Phrases that are easy and satisfying to say in the sense that they are actually just easy to get your mouth around are more likely to catch on. This is definitely something they should consider more carefully.

One could also argue that google is a pretty nice word for the English language since it evokes words like "look", "oggle", "oodles", implying looking through a lot of stuff and having a playful tone. Sounds silly but when someone says words sound like they mean something, it is a real phenomenon due to the way we interpret various sounds. In most languages, B sounds sound like big and round things and K sounds sound like sharp things. There have been studies on this. You can then get more specific in the subconscious patterns people recognise when you narrow it down to a certain language. This is why I say, Google is a great word for its function in the English language.
Since the government in many ways views citizens as threats to their conntrol / power, the last thing they want is that population armed with a powerful AI.
the API already is super simple, and low bandwidth could already work on retro machines (I had 6809 in mind when experimenting with it). The problem is e2ee, but we have the Pantalaimon e2ee proxy to convert unencrypted Matrix traffic into E2EE traffic for precisely this sort of thing :)
the most important thing though, is that that statement is true and verifiably so.

I am one of those persons that learned something by reading that comment.

assuming arrogance and sassyness in an otherwise neutral exposition of a true fact, to me means that, as usually happens, arrogance and sassyness are in the eye of the beholder.
I exercise regularly, I cycle and I work on our land (we have a few acres that need a lot of management).

None of that is available to quickly switch me off and relax me at 11.30pm after we had a production failure and the shit needed to be saved from hitting the fan.

I'm not really the meditation type.

It's true I could easily not have that glass of wine at that point, but I'd probably then go to bed in a more stressed state and sleep worse. :shrug:
And Comcast were the biggest proponents of building IPv6 support into the DOCSIS specs, because they exhausted 10/8 in the management network for their modem fleet.
Kagit
IPv6 adoption is only going to further the consolidation of customers onto the big monopoly providers. They will be the only ones who can afford to add the dedicated network engineering staff to make it work reliably.

Most people don't realize there are two IPv6 internets right now, the Cogent side and the Hurricane Electric side. Both are equally sized and refuse to connect to each other, so you need to know that and either buy transit from both or buy transit from a network that buys from both. At least one major provider I know of is still running v6 over tunnels. In many places your v6 traffic is taking suboptimal routes, whereas an enterprise network may have v4 connectivity at each datacenter, v6 all gets sent to that one box under Dave's desk.

But we continue to measure v6 adoption at places like Google and Cloudflare where dedicated teams make sure packets arrive and pat ourselves on the back.
At least they could make a syntax for joining on a “foreign key references” clause from create statement. E.g. “from a join b by a.b_id[, a.b_compound_id_2]”.

But that’s just a sugar for still too low-level SQL. I’d better have well named relations and use these names in code. This way, there would be no situation when you add/remove a constraint but forget to add/remove a condition.

create table a (id, b_id);
create table b (id);
create relation atob from a to b on a.b_id = b.id;

select from a left join b using atob;

This could also define classes of relationships to check in runtime. E.g. I’ve never sent all purchases with right join in my life, but had enough exploding relationships where 1:1 was expected.
I agree entirely about that tech debt. I've built, sold, grew and failed several startups myself. Many with Rails at the center. I've been building with Rails for way over a decade, so I'm well aware of the "options" back in the day.

What I'm arguing, however, isn't to take on debt¹, I'm saying that productivity and performance aren't always opposites.

Sure, Rails trades in performance for productivity. But, I've learned, this is mostly just Rails. There are many languages and frameworks that are just as productive (for a certain definition, see previous comment) as Rails, but also performant. And I'm arguing that performance affects productivity: a performant, scalable software is easier to work on, because it gives faster feedback (tests, ci, manual testing), wastes less time waiting for stuff (hundreds of single seconds add up over days and weeks weeks), and decreases friction (I'll postpone running the full test suite if I know it'll hog my machine for the next half hour. I'll gladly run it, if it takes a few minutes or less).

Edit: and, if what you say about tech debt is true (I think it is), wouldn't Shopify be at a position now to pay it back? Many startups that used Rails paid it back by migrating elsewhere. So maybe Rails in its entirety is Tech Debt?

¹A cautionary sidenote, that I've learned the hard way, is that taking on tech debt is an art in itself. Not all debt is alike. Many kinds will cripple my project. Where at the unlikely moment that I do need to scale, that's impossible. Or when I do need to pivot for the umpteenth time, we cannot, without that Giant Refactoring.
> This IS a pet project

I think that is a great attitude to start with.

When you build something with the attitude that it's for you and not "meant to be big and professional like GNU" to paraphrase Linus Torvalds, you can often achieve a lot with far less effort.

It allows you to be pragmatic and accept things that you otherwise might not, and you can get to something useful to you whether as a learning experience or to actually use with a tiny fraction of the effort you'd want to invest if you intended to build a "product".

A lot of my personal projects have involved stumbling over a project like yours and repurposing parts, and often veering off in entirely different directions, because it's often so much easier to pick up someones small pet project that is "close enough" than trying to pare down or adapt a huge, feature-complete beast.

With a browser, a huge part of the complexity comes from needing to support every site out there, and every usage scenario, but when you build for you, already just being able to focus on making sites you care about work well enough pares the problem back enormously...

And this is a long way of saying I think more people should take on "impossible" projects. Maybe the full thing won't be useful for other people anytime soon, but maybe parts of it will be, and sometimes something bigger comes out of what starts as a small pet project (like Linux did...)
Same here. I was astonished when I realized the device could very consistently "spot" when I have been drinking alcohol. It made me realize the effect of alcohol on the body are very measurable, and lasts multiple hours after your last drink.
nice idea.

Personally, I do not see myself using it, yet I can see the value and innovative line of thought.
You should really consider getting a proper router like Unifi or the like.
It's a one time cost and it will save you from these issues no matter what ISP supplied crap you end up getting.

Just plug whatever ISP router directly into your own, more capable, router and your home network will look identical, no matter where you move to or how many times you change ISP.

That said, running Pi-hole on a Raspberry pi is a treat!
What is your point?

The guy I was replying to was satirizing beer drinkers as consumerist cogs in the machine. I pointed out that of all the things to criticize someone for enjoying alcohol is probably one of the least corporate. If buying alcohol makes you a monopolist’s bitch then so does buying anything and everyone in the entire world is hopeless.

It’s like claiming solar panels make you a slave to factory owners when they can be used, operated and repaired in a distributed manner. Sure, maybe, but like what a weird hill to die on?
How would one anonymously train a LLM of sufficient size to produce the performance needed? Does it not required hundreds/ thousands of expensive Nvidia GPUs?
If you're not using token ring, it's not a real network.
We use Makefiles to run our data science pipelines. So my apprentices (yes, we have a data science apprenticeship program with school leavers doing data science degrees on day release) are all familiar with writing and running Makefiles
Talking about PagerDuty, I created a humble competitor: https://allquiet.app

I hope it will help some smaller teams/companies cope in this high rate / low growth environment. :=)
See my other sibling comment I’m not retyping that shit.
It is so easy being smarter than Plato/Kant/Freud. You just need to be born later. Still they are a valuable part of the evolution of the human mind IMHO. Some of his thoughts still make sense, even if they are not falsifiable.
That's what I thought at first, but that's not quite right.

Service Endpoint: Allows a PaaS service (that itself uses public addresses) have firewall rules for overlapping private vnet addresses. E.g.: You can have have two VMs both on 10.0.0.123 addresses (in separate VNets) using individual "Allow" rules to the target service. Essentially Azure tags the traffic at the VXLAN level with the source network ID on top of the IP address, making it a "fat IP address" that is unique within Azure and can be used in firewall rules.

Private Endpoint: Makes a PaaS service appear on a private network address range instead of the default public range. This allows your on-prem firewalls to isolate your specific PaaS instance from other customers -- otherwise the traffic gets "blended in" with everyone else in the same public service tag ranges. This also allows you to use your ExpressRoute fibre links to route traffic from on-prem to the public service.

In all scenarios, the traffic goes over Azure networks and/or Microsoft's private backbone. You have to go out of your way to route traffic "via the Internet". Remember: Network addresses are just numbers! Routing rules determine how they flow, and public addresses can be used on private networks.

Fundamentally, all this exists just to enable the ability to firewall things. With overlapping IPv4 addresses and small shared blocks of IPv4 addresses with NAT behind them, it would be impossible otherwise.

With IPv6, using firewalls would be much simpler because overlapping addresses aren't needed any more. Similarly, PaaS services could trivially allocate IPv6 addresses per customer instance, so that customers could apply selective firewall rules.
Mastodon 4.2
Yes, it is biological sampling! We have some biologists and ecologist in the team that took care of the methodology.

And indeed we have taken a simple approach with some string/ropes that works pretty well as you said. But we have a lot of sites in different parts of the world to sample on a yearly basis. I was looking for a way to make this easier for the people in the field.

Thanks for your tips!
> "Writing a browser" (from scratch) at this point basically means you are implementing a type of portable operating-system-in-a-box (the web platform) and that it will be compatible with whatever Google decides to add to theirs.

I'll bite... why? Most websites follow HTML and ECMAScript. Why do you need to do anything Google does? Isn't the whole point of this project to decouple from what big tech companies do?

The vast majority of websites don't want to follow whatever Google-only shit they've come up with most recently, whether it's adtech, AMP, DRM, or whatever.
I'd agree if the scale of money being poured into closed source models was what it was only a year ago, but now it's 10x greater. Open source can't compete with hundreds of millions of dollars and the talent vacuum it creates.
Thanks. I never heard of this. I'll look into it!
I certainly find there are many people who take that naive view.

The right thing to do is to triage them in your context and make your own risk assessment. The CVSS numbers are a guide to which ones you should prioritise looking at, but not a risk assessment.

However, in the security and risk world, you have to take a worst case view in the absence of further reliable information. This can lead to fixing things that maybe don't really need fixing, even when a triage has been done. It's often hard to discover enough reliable information.
That's not the point of the study. Many negative thoughts are safe to ignore. There's a difference in dealing with realitiy and wallowing in negativity for its own sake, or because of some freudian bullshit.
God trying to look up what some string of characters in a random programming language is feels like a Sisyphean task in Google. Try getting Google to understand what a typed hole in Haskell is without knowing it's called a typed hole
I'm talking about webcams, which have more complex use cases than unprocessed game capture. MJPEG is necessary blocky and bad at low values (shadows); if you're going to chat with friends, streaming it directly, it's probably not going to be noticeable. But if you want to look good, any raw noise or any processing will amplify the compression artifacts, especially in the dark tones, and 4:2:0 will wreck the saturated reds against the opposite background.

Take a look at this OBS forums thread I found, which is a pretty good illustration. [1] This is the best key from a cheap MJPEG webcam I've ever seen, usually it's terrible and streamers have to wear hats. The edge quality in the final picture is still bad (especially hair), and that's with unholy amount of polishing the turd he did, sacrificing latency and probably holding his breath (figuratively) to not go outside of his finely tuned setup. Especially the temporal noise reduction. Check this frame out as well [2], and pay attention to his shirt and hand - the edge is terribly pixelated, which he points out as well. And that is probably the best you can do with the crappy compressed source.

This is the reason cameras like Facecam Pro exist at all. Uncompressed YUV with full chroma resolution makes it all far easier.

> Obviously it's more dependent on what you use as camera, than the encoding method.

You can get away with a cheap camera, if you're using it indoors with controlled lighting; you can't get away with bad compression if you want to process it.

[1] https://obsproject.com/forum/threads/151600/

[2] https://obsproject.com/forum/attachments/78631/
> massive load of work for negligible (if any) gain

If you coded alone for 10 years and then add a strict linting config you're going to have a really bad time.

If you actually follow the advice a linter gives you, you come up a 10x better developer.

Of course not all lint rules are created equal, but some are arguably existential.
They are in luck - the person they are looking for is already working for their company. I mean, whoever determined that the job can be done in exactly 70 hours must know the system inside out and it's only a matter of putting in the work.
But I mean your rendering and layout engine don't need to pass all ACID tests out of the gate, right? You build it up gradually. You start by getting reasonably simple HTML websites to render. There's no rush, and there's no hard and fast rule saying you have to implement every corner of the standard.

Web browsers and the web are gloriously human.
Was there ever a claim of heart benefits from drinking alcohol?

I thought it was specific to wine due to resveratrol, rather than the alcohol.
I think there's also a difference in definitions. If you look at the comments here, there are many mentioning the effects the day after, after that night out with the gang. To me this would qualify as "heavy drinking that night" not just "drinking". So for some "drinking" means getting hammered, for me (and others) it means having a glass with a book in hand. And I see obvious (health) consequences only for one of those.
Isochronic Maps
I can't but point the reality of modern college education: professors nowadays are mostly fundraisers than teachers or lab directors.

This is especially true in the United States or Switzerland from my experience but it applies to virtually any country where the budget that goes in public research is not really enough.

Their first job is really fundraising, and their second job is actually academical.

I've worked for some time with scientists like Michael Graetzel[1], he was very important in the lab, don't get me wrong, he had a brilliant mind and he would still take decisions and give terrific feedback when he was in the labs, but the primary role was fundraising.

You can only have the best lab if you have the most money and can hire more and the best people, that's more important than teaching or directing a lab, sadly.

[1] https://en.wikipedia.org/wiki/Michael_Gr%C3%A4tzel
> port forwarding is no longer available through the administration interface.

Sounds like the CGNAT experience, possibly blanket applied even if you have a globally routable public IPv4 in order to have consistent behaviour and reduce network management / support case complexity.
Agree, trying to isolate a single variable additionally creates an illusion: that if one removes all the negative variables and adds all the positive variables you get a super-positive result: if all you eat is fibers and anti-oxidants you will surely die a premature death to put it crassly.

It ignores that things work in concert: a healthy life is about balance, i.e. in this case: a Mediterranean diet seems to nullify the impact of alcohol (which I assume is the reason for the low heart disease rates in France and Spain, despite having double the average alcohol intake compared to say the Nordics).
I replied to someone else's similar misconception of what problem Private Link solves here: https://news.ycombinator.com/edit?id=37609614

Hint: it's a complex workaround for insufficient IPv4 addresses.