skysight-inc/HackerNews huggingface dataset:
IMHO TCP made the correct call here. TCP is a transport, not an application protocol. You are supposed to run your protocol over top of it, including things like blocking, substreams, etc... It's easy to add features to a simple transport, it's not so easy to work around features when you don't want them, plus they end up complicating the stack and become a possible source of bugs. Even "simple" TCP proved to be quite a challenge to implement back in the 90s, with many many buggy stacks out on the Internet.

By being just a stream of bytes you are free to do whatever you want with the protocol. Sure that may mean implementing your own form of blocking but that's better than being stuck in a protocol where you are forced to work around the message oriented features even though you are just streaming data.

The checksum does hail from an earlier era where 16 bit machines were commonplace and the total amount of data sent is minimal. Also, there is some assumption that the underlying transport is going to have its own checksums. You will note that IPv6 ditches the checksum entirely.
Ever since Brendan Gregg started using eBPF for observability back in 2015 I've had the sense that eBPF is an extremely underrated tool of the future. I really would like to learn it, but beyond some improvised bpftrace scripting and the tools that come with bcc, I've not really had the need.

What custom usage do you have for it?
If you want to be _really_ fancy, you can set up an intermediary mail proxy that will store emails and then forward them to Google's servers.

For me personally, the small loss is acceptable. I know that it's going to take me maybe a day to set up everything on another provider.
> set of opinions about stack

The stack doesn't exist today. It could have if we didn't jump so quickly to new technology and all these different prog languages.

I've just never heard someone pitch new tech with: "easy to debug and change". It's always: look at this contrived example with some new esoteric feature.
>Why do you want to do a linear regression on random segments?

It may be worth reading the article fully -- why random segments and the logic of it is explained fairly well I think.

>Author talks about reasoning, but I think it would make the point clearer if there was a section that reasoned about the result on FTE.

Same as above. Have a read of the comments around the implementation.

>Why are there a white upward segment and a white downward segment?

There are no white segments -- those are gaps.

> Inside the blue segment there is a clear downward segment, about the size of the red downward segment.

I guess you mean the last graph? I think if the isotonic regression was plotted on the graphs, it'd be clearer why that segmentation makes sense. But in brief it is about how well an isotonic regression fits in the segments as opposed to how it may visually seem -- the two can come apart.
I do note that. I'm not sure how that relates, though.
Yeah, I don't know why my summary was flagged either. I like testing LLMs on article summarization (especially on articles about AI), and found this to be a very good summary, that's why I posted it.
nah it's all good. it's just the "estimation value" which is technically arbitrary, but a common practice is in a 2-week sprint, 1x eng 1x sprint is ~5 points.

By saying 8pts the team is effectively saying it's probably a 2 sprint job and individual tickets are not supposed to be 2 sprints long meaning there's complexity that either needs to be broken apart or on the rarer case, team agrees the ticket is fine as-is then it'll take 2 sprints.

Anything 13 or greater is saying this ticket is so big we can't even begin to accurately estimate it - PM take it away from us! It's fun to see 21 or 34 pts... it's all a joke at that point.
Do also check out https://en.wikipedia.org/wiki/Profit_(TV_series) that's a WILD experience. I believe all of it is available on Youtube as well (in glorious 90s quality experience).
I think it's because it's fun to work at a company that is tech-first (as opposed to just using tech as a tool for growing business) but it leads to doing things in complicated and risky ways "because we're a tech company"
I pressed a button on Twitter to not show me anything from musk. Now it’s a muskless twitter. Meanwhile I’ve heard that alternatives like mastodon have half the user base taking about musk. That’s much harder to block.
Having no other arguments, this attempt to appeal to "not having good faith" looks really weak.
Administrators memorized IPs a lot. This is hard to under estimate and is frequently the disconnect I see when a SWE doesn’t understand why people could possibly complain about ipv6.

This is likely the #1 issue I hear from people in the field.

#2, for better or worse, NAT became peoples’ comfort blanket. It’s a boneheaded stateful firewall regardless of how long people can scream “NAT isn’t security”. By forcing people to take both changes at the same time, adoption was setup for failure. So many places in the US turned it off “because nothing I use is v6 only” and they weren’t quite sure if they were exposing their end hosts accidentally.

#3, link local addresses, guids, etc all assigned at the same time is a steep learning curve. Which will be used for which flows in the network? If my ISP changes my prefixes, do I know have to reconfigure all of my local network firewalls?

#4, prefix delegation, should each client behind my router get its own /64? My ISP only gives me 128 of them to hand out which is a problem for IOT. Guidance here is weak.

Burning all of the early adopters with the slaac vs dhcpv6 vs privacy extensions didn’t help either.

Nobody gives a shit about fragmentation. The upgrade UX was a disaster.
Anti-aging by necessity also means solving the common causes of death and your body falling apart, not just letting them happen but somehow preventing them from killing you.
Re: graphite story. Wikipedia citation is to a biography of Szilard, and it says:

> Fermi and Szilard met with representatives of National Carbon Company, who manufactured graphite, and Szilard made another important discovery. He asked about impurities in graphite, and learned that it usually contained boron, a neutron absorber. He then had special boron-free graphite produced. Had he not done so, they might have concluded, as the German nuclear researchers did, that graphite was unsuitable for use as a neutron moderator.

A neat story, and although I haven't checked the citation I don't doubt it says so. But it probably didn't happen that way: many biography anecdotes are like that.

Here are some quotes from Voices of the Manhattan Project: Norman Hilberry's Interview (1965) Part 2. Primary source on the history of the Manhattan Project, so to speak. https://ahf.nuclearmuseum.org/voices/oral-histories/norman-h...

> This was just one of those things that Szilard had been needling the graphite companies for two years to try to get pure graphite. He had been working with the Speer Carbon Company... Boron was the one that we just had to keep out because it has such a terrifically high cross section for neutron absorption... But their facilities, a number of furnaces and so forth, were so few that I went down to National Carbon Company to see if we couldn't get them, now that we knew what had to be done, couldn't get them to start making stuff for us.

So it really can't be that Szilard made discovery about boron at meeting with National Carbon Company. Szilard already knew about boron, and developed boron-free graphite production process with Speer Carbon Company. But Speer was too small, so National Carbon Company was contacted to scale up the process.
What about playing a game that you have bought, but emulated on a different platform?
HN has always had some science content not just tech. Articles about fusion and batteries get promoted here often. If all your other sources are pure software focused it would make sense you dont see aging there.

As for the actual topic. Lots of people talk about fear of death, and i am sure that plays a part. For me though, i think its interesting because people have been trying to increase longevity since forever and haven't succeded yet. There is something fascinating about a problem everyone has tried to solve but still isn't solved.
So many network admins still prefer to configure smaller networks with IPv4 instead of ipv6 due to simplicity, then just nat peer it out

Hell even AWS didn't start seriously supporting it until the mid 2010s... And heck I don't know if they support ipv6 across the board or not
Technically true, but parent’s point still stands (even if it should have said “on top of IP”).

Byte streams are not ideal to deal with for protocols. As soon as you have encryption, like tls, you have discrete messages anyway (records) and the stream is largely an illusion.

That said, I still like TCP as a compromise between simplicity and versatility. It’s been holding up incredibly well for a huge variety of use cases.
Unfortunately the case -- you just have to be honest and say "no it can't do that" when it can't. The "impedance mismatch" between managers/stakeholders and contributors is an ever renewing source of BS for many of us.
There are a wide range of threat models in between "no effort" and "state-level intelligence agencies".
You can work around pretty much any issue like this, but you shouldn't have to. A beginner's guide should define the concept.
I played a full-ish playthrough (no more quest triggers on the map at completion) at version 1.60 and didn't ever crash once. I got a freeze that I need to tab to a different window and `kill -9` it, which required restarting from the previous autosave. No crashes though.

I'm currently 40ish hours into a second playthrough (no more tertiary/secondary quest markers on the map, although I need to wait for a few more secondary quests to activate before completing the main quest line) of 1.61 and haven't had any freezes or crashes.

For the record, I highly recommend the game. It has great world building, gameplay, immersiveness, it feels alive in a way that I haven't felt about any game in a while.

I'm playing on Linux with an AMD GPU in Wayland. YMMV on Windows and/or nvidia and/or X.org.
It's a valid topic of discussion around here because people are educated enough to consider medical anti-aging as a plausible thing, whereas in other demographics you would be ridiculed as an idiot with a God delusion.

But anti-aging in general is a topic permeating our entire society, from non-stop commercials to "rejuvenating" cosmetics and dead-sea-mineral-spas, to the boom of plastic surgery, to the fad diets promising a long healthy life, if we look around everybody talks about it one way or another because nobody wants to get old.
You are both right, it was a childish comment that I can no longer edit. Sorry.

I do disagree ignoring them is the best. This gives them an echo chamber here and can others can get the impression they are always right. The attack was not helpful as you said. I'll try to do better in the future.
You're calling my comment strained, but somehow missed the fact that all of the things you mentioned are shipped by Apple and updated basically together? The comment mentions Sparkle as "patching up this gap" so it's very clear what they meant: third party applications. Nobody is asking for updates for "every application there is", but providing an API to update third-party apps. MacPorts, despite getting significant investment in the past from Apple, is now definitely a third-party solution and not an system API.
By setting the bar lower, honestly. A walk in nature isn't very likely to make you happy, but it is quite likely to make you content. Happy is the top of the scale. Content is "good enough".

I have a slight tendency towards gloominess and light depression and for me the most powerful tool has been to change how I answer "how are you doing", both when other people ask and when I ask myself. Instead of trying to figure out if I'm happy, I just look if anything bad has happened yet. Usually the answer is no, so I can answer "doing good so far" pretty much always. Doing this has improved my mood incredibly. That's the same sort of happy-vs-content thing I'm talking about.

It's like going to sleep. If you try to will yourself to sleep it will invariably fail. Instead you have to make the conditions right and sleep will mostly happen by itself. Similarly you shouldn't try to be happy. You should try to not be unhappy -- by removing things that make you unhappy, or by learning to live with them without it affecting your mood too much -- and the rest will follow.
How about interactive books? Like Immersive Linear Algebra by J. Ström, K. Åström and T. Akenine-Möller; or http://immersivemath.com/ila/index.html or Interactive Linear Algebra by Dan Margalit and Joseph Rabinoff https://textbooks.math.gatech.edu/ila/index.html

I suppose they should work well for self-study, but I never tried learning by one myself.
Thunderbolt cables are extra thick to support the signaling that thunderbolt requires, so unless you're actually using that cable for data, it's more cumbersome. And shorter - max of 10ft. Which may be fine for you, but no thanks. And also, optical Thunderbolt cables can't carry power, so there's no guarantee that a thunderbolt cable will even do power delivery. If it's longer than 10 ft, then it won't.
This is pretty much where Google was obviously going in 2003.
They are hostile compared to most other platforms. I stopped using SO a while ago because it’s useless. You get much better results asking on a discord community where people are happy to help you out rather than spend all day scouring the site looking for posts to report.
Please note that Pidgin is still GTK2 but there is a GTK4 version in the works that has a more modern interface. I think they welcome donations to make that go more quickly.
To be honest, i've always wondered how many people would actually believe this if given the choice (assuming healthy immortality). It always struck me a bit as the sort of thing people say to be able to live with the fact they are going to die and there is nothing they can do about it. Always easier to accept something out of one's control by pretending it is what you wanted all along.
Is IPv6 on his list?
In some ideal world IP values vary between 0 and 999 and you just add a new block if you run out of them, `999.999.999.999` would be the last standard IP, simply add another `.000` block and you get some more billions IPs.

Having letters in IPv6 feels wrong, at that point why not just have words, reinvent DNS at a lower level. You are already living on Cherry Picked Street, number 15, let your computer have the IP `cherry.picked.15.1`.
> By being just a stream of bytes you are free to do whatever you want with the protocol.

Not entirely. Head-of-line blocking is an inherent problem with TCP so you can’t have real priority “streams” like you can with eg QUIC. Another “missing feature” is datagrams, ie simply opting out of the retransmission part of tcp.

That said, I still agree with the general statement.
I think this addresses most of my concerns regarding passkeys.

The biggest remaining one is still that fingerprint locked information is not protected under the fifth amendment in the US. Even pin protected information/logins has been ruled as both protected and not protected by different courts. The "key vs combination" debate hasn't been decided one way or another. I can imagine a government push to not count fingerprint locked passkeys as equivalent to passwords, but that's not a weakness of passkey technology.

I am also interested in seeing how phone secured passkeys will work, iOS currently forces the use of keychain, excluding users who opt for a third party password manager like bitwarden. I also wonder if phones will be able to be used to login without enabling bluetooth.

https://www.concordlawschool.edu/blog/constitutional-law/fif...
It's not an idea answer, but you can do everything in terms of file transfers and charging via the internet and magsafe respectively.
Isn't it like literally a data structure issue though? Like you have to route on prefixes? Like how else would you know where to go?

Ip routing is kind of like a tree (not a graph) in the ip regards, how would you get around it?

I admittedly don't know as much as I'd like about network, hence why I'm posing this question ;-)

If theres a way to efficiently model hierarchical domains for stuff like DNS/IP i'd love to know. Like, consistent hash rings maybe, but then we'd be reintroducing ring topologies...

Oh wait duh though. A cell tower is owned by a single company. Yeah that's prolly doable, the company can always buy beefier routers if they need the memory. And realistically speaking the virtual tree could be closely aligned to the physical one given how cell towers work.
They already do these special locked SKUs for American carriers.
Doombase – The First Doomer-as-a-Service (DaaS)
How are you going to learn all the essential Javascript frameworks in time if you die before you reach your first few centuries of age?
This is the way.

That said, I do have a hybrid solution: HomeKit for having a nice UI, Node-RED for a little custom logic, and a Homebridge MQTT plugin to tie it all together.

HomeKit is perhaps unique in that the Home app will work just fine without an Internet connection (although you do gain the benefit of remote control if you have an Apple TV or HomePod). Siri is pants, obviously, but good enough to set scenes.
> Jobs. There are too many white, asian, and Indian males in my company, we're told. So we have to hire others preferentially now to balance out our numbers. Yet if a white male identifies as a woman there's a space for them.

Isn't it weird how this doesn't seem to be predicated on them being hetero? Could the bias you see have other reasons, given it's not purely predicated on sexual identity?

I don't see a reason to reply to the rest of your comment, given how you're starting with obvious fallacious rhetoric.
I've had all these arguments before, that I don't care to have again.

> And telling other people when they should die is sorta messed up

I'm not telling other people when to die! I'm thinking more of a societal contract. Which in fairness, seem less and less these days.

Like, if I go to the back of a queue, and see you going to the front, and request you go to the back... I'm not trying to control your life. I'm just asking you to acknowledge and respect that we live in a society.
From the article, this molecule sounds like a big hammer that you can pound cell reproduction with, affecting a wide range of systems in unpredictable ways. Whereas what we need are precision watchmaker tools and a diagram of the watch.

On thing I think is well established about aging is that it's not a single factor disease that you can "cure" by removing a well defined cause. Rather, it's a pervasive accumulation of entropy in various systems from various causes that evolution had no ability to correct, so that slowing aging down and reversing it involves a massive amount of tinkering with the watch.
To be precise, MTU.

The MTU should have been reified to the IP layer. And it would have been so easy!

When a system sends a packet, it sets the "forward MTU" field in the IP packet to be equal to the MTU of the outgoing link. Each router along the way inspects the packet and if its outgoing link has a lower MTU, it replaces the "forward MTU" with its own.

Once the packet reaches the destination, the target host copies the "forward MTU" field (which now has the lowest MTU seen along the path) to the "reflected MTU" and sets it on the next reply packet.

So the originating system can discover the limiting MTU by the time it gets the ACK packet.

Sigh. Instead, we have a Ruby Goldberg machine with fragmentation, ICMP and all the related unreliable crap that has forever cemented max MTU as 1500.
- It is sold to someone who is willing to buy it (kind of like Smosh) or

- It is left as it is, public (like Filthy Frank) or

- It is deleted/made private (like Joana Ceddia)
No idea what you mean with outcomes vs means/tasks. Just put outcomes as cards in your Kanban board, they don’t have to be tasks.
Scrum needs surprising effort from coworkers to understand the system as well unlike common kanban that has existed for eternity. Meanwhile at some stages the stuff just becomes mythical and people stop to implement but rather improvise.
On the other hand, as a live-performing musician, the combination of a 12.3" iPad with Forscore (to replace sheet music) has zero competition. Nothing else comes remotely close.
I didn’t hear anything “wrong” at all. I know people personally which make a lot more than that. If you did R&D for 80k in a senior role you got robbed.
This is a recap of the top 10 posts on Hacker News on May 7th, 2023.

(00:31): Walkout at global science journal over ‘unethical’ fees
Original post: https://news.ycombinator.com/item?id=35848894

(02:14): I'm never investing in Google's smart home ecosystem again
Original post: https://news.ycombinator.com/item?id=35849060

(03:36): Pixel phones are sold with bootloader unlocking disabled
Original post: https://news.ycombinator.com/item?id=35852192

(04:58): The Prime Video microservices to monolith story
Original post: https://news.ycombinator.com/item?id=35853148

(06:16): EU sends Apple stark warning over USB-C charging on new iPhones
Original post: https://news.ycombinator.com/item?id=35849043

(07:45): Burnout
Original post: https://news.ycombinator.com/item?id=35849384

(09:04): Contrast Rebellion
Original post: https://news.ycombinator.com/item?id=35850044

(10:25): Five Books: The best books on everything
Original post: https://news.ycombinator.com/item?id=35853131

(11:52): Passkeys: A Loss of User Control?
Original post: https://news.ycombinator.com/item?id=35854216

(12:58): AMD promises its new laptop chips will crush the Apple M2 and it’s got receipts
Original post: https://news.ycombinator.com/item?id=35851174

This is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai
I've learned that I have many biases and ideas that aren't grounded in reality, even though I really thought they were, but data couldn't support them. Since then I've tried to confront more and more of my knowledge in the same way.

What you wrote might feel correct to you, but have you seen scientific research towards it? If you go by what you feel is right, how do you know you're not being manipulated? Seems like a perfect topic to divide people.
I would think that depends on the expectations.

I have both an iPad Pro and a MacBook Pro. For development and many other tasks I prefer the MacBook Pro.

For some tasks I prefer the iPad Pro. But there are things I don't like about the iPad (some because of its particular software/hardware and some because of the device class). So I would agree with some of the points.

I find text editing on the iPad screen to be difficult. The screen also gets dirty and needs to be cleaned. The keyboard is bulky. I'd like a few more interfaces on the hardware - otherwise I have to use a dongle/dock or wireless interfaces. Using more than one app for tasks is still difficult, due to the lack of software integration. Generally the software integration is incredibly weak. For me the iPadOS is a bit too locked, not sure if I wanted to run Linux on it in a VM, but I would like to see visual programming languages compiling down to the instruction set. I'd like to see programming on the device, but in a tablet-optimized way - but I admit that the majority of the user base is not doing programming and that's where the larger market is. It lacks stuff which the iPhone has, like being a native platform for health data.

What I like: the screen, the portability, the speed, the connectivity (included 5g), the precision, the responsiveness, ...