skysight-inc/HackerNews huggingface dataset:
Aye, the rule before this change is in the terms as:

> 11. Simulcasting

> When you are streaming live on the Twitch Services you may not simultaneously live stream or broadcast (“Simulcast”) on any other “Twitch-like Service,” meaning any web-based network, platform, or service that supports live streaming of user generated content, without advance written permission from Twitch. For clarity, you may Simulcast on mobile-first services that support live streaming. This Section does not apply to non-profit or government entities that are live streaming for non-commercial purposes.

Twitch-like being YouTube, Kick, and similars. Mobile first being Tiktok, Instagram, etc - vertical/portrait resolution

https://www.twitch.tv/p/en/legal/terms-of-service/#11-simulc...

I imagine this will be changing soon so for posterity https://archive.ph/Y3Vti#11-simulcasting
I was hyped about materialize in the beginning but now looks like they’re just cloud focused and it’s unclear who is supposed to be their customer at all. Also I swear I saw their original docs said they can do window functions but not anymore.
Yeah. "You ensure" that Twitch users' "experience" of your stream is "no less" than other platform users' "experience".

They write them like this deliberately -- so they can enforce them however they like, and there's nothing clear-cut so they are largely unaccountable. They're "guidelines" after all -- mere suggestions at things you might like to consider. You know, "guidelines", as in "your account has been closed due to your recent breach/es of the guidelines".

So, if I can't ensure that every person watching on OtherPlatform is having a measurably worse time than every person watching on Twitch, I'm risking my Twitch channel? Unless they came here for a bad time, I guess, so every Twitch viewer must be having the experience that they deem as more than or equal to every OtherPlatform viewer.

I guess if I can't comply with that then maybe I just don't have what it takes to be a god/Twitch streamer.
Unknown unmarked mysterious drone harassing you? I'd say it's skeet shooting time.
This metaphor is wrong: meteorologists don't have any impact on the sunshine, whereas devs have direct impact on estimates.

In both cases, wrong estimates will generate problems for the stakeholders, but devs can make choices during the implementation that will influence the outcome and may in some ways mitigate the lower estimates, but meteorologists won't ever have any influence on the weather.
Tracking emotions on social media to predict which posts go viral
I would not be surprised if Ticketmaster gives the NFL some major incentives to using their services.
The lowest courts hear issues related to legality of actions. Appeals courts may overturn if the government is acting outside of its authority (the constitution).

In this case, he's already gone through the appeals court, which made a bad decision.

The supreme Court only hears cases on constitutionality.
As a casual user twitter feels exactly the same to me, but perhaps less spammy responses to tweets selling NFTs and the addition of community notes.

Twitter has always had a reputation of reliability issues. They're basically famous for it.
The nobility doesn't directly control the monopoly on violence like they did under Feudalism. However, they still make a living by owning things rather than by working, this still gives them crossed incentives to most commoners on a wide variety of issues, and they still exert outsized political influence in furtherance of those crossed incentives.
Wow, this looks amazing. I am super excited to play it. I have a pretty beefy PC. Is there any benefit in playing it on steam and streaming to my quest, or is the quest native as high quality?
> Sure, a frontend dev who strictly works on that won’t know much about, say, the OS layer. But they don’t have to, it’s not part of their job in any way.

The HTTP protocol, HTML and vanilla JS are not "the OS layer", and yes, it's part of your job as a web developer to at least understand the basics of them. There are many so-called "frontend devs" nowadays who literally only know React, and if you asked them to create a basic webpage where clicking a button changes some text in an element without React, they'd be completely lost.

Usually the problem with this kind of developer is not just that they don't know, it's that they don't care. They WILL inevitably run into problems that require this basic knowledge to solve because the frameworks can only hold your hand so far, and instead of trying to figure out what's going on under the hood that's causing their issue, they will instead shrug and go "it's not part of my job" and just write a bunch of garbage spaghetti code in an attempt to work around the issue.
Geany 2.0.0 Is Out
Satellites and Spacecraft Are Polluting the Atmosphere, Scientists Find
Show HN: YouTube Musical Spectrum – visualizer for YouTube with musical notes
Dear,

This is an update from first submission [1].
New features:
- add Hz scale
- add YT Music support
- add microphone recording
- add scale (x and y) options to reduce CPU usage

[1] https://news.ycombinator.com/item?id=28135562
But we can fight back with Linux?

I've thought about this a bit and based on previous challenges that could be technically solved with technology I would say that the answer depends on who "we" are. We as a small group of technical people, for sure. We as a society, not a chance. People gravitate to big platforms that are low friction that all of their friends can use. Big platforms and operating systems tend to be run by companies and companies must remain in the good graces of their governments. They will flex and say they will stand up to big brother but prior to earnings calls they will back down. I wish that were not true. More specific to your question, should Linux become the dominate platform it would become bloated and infected with corporate monitoring and malevolent patterns. At least one distribution has already tested the waters and another distribution is putting their toe in the water. Corporate sponsored distributions are likely the ones that the masses would land on.

For what it's worth Rob does have some great videos that cover many aspects of privacy and freedom. He has a video that covers how cell phones are evolving to leak data through multiple methods that most people are not even aware of.
Implement a proper Proof of Possession system (PoP) and make Let's Encrypt opt-in instead of opt-out.

Given that in the end, Let's Encrypt/ACME relies on PoP of a DNS domain, DNSSEC setup on the domain should have been a prerequisite.

In addition, an explicit opt-in should be required, for example, with a requirement for a CAA record pointing to LE.

---

As a side note, this whole situation leaves me with a really weird feeling.

On one end, I will always be grateful for LE enabling tls/https generalization.

On the other, I kind of feel betrayed and/or ashamed that LE/ACME almost willingly introduced protocol flaws weakening the whole CA infrastructure and that we (me included) didn't challenge it more when LE was introduced.
Why do you think that? There is pending problematic population decline in many areas of the world.
_SELECT 1 means "select the first column"_

In SQL Server at least, no, it literally means select the integer 1. In the ORDER BY clause, it does mean to order by ordinal position, but that's not a great thing to glorify, since ordinal position is not necessarily stable. I think other dialects like MySQL might allow GROUP BY 1, but that's not a great thing to glorify either.
Quantization of events and the emergence of quantum mechanics
The T2 fixed what you are complaining about. Was released in 2007.
> Signal has massive usability issues

I'd say these are security issues
As a somewhat old greybeard at this point, let me apologize for all of the other greybeards who never shut up about this movie.

I don't blame you if you watch this movie and are left wondering what all the fuss is about.

It's sort of like the LOTR novels, the original Star Wars movies, or maybe even the original Alien movie. Or listening to the Beatles or Nirvana. They were the progenitors of absolutely zillions of derivative works, to the point where Blade Runner's "neon noir cyberscape" aesthetic and LOTR's "humans n' orcs n' elves n' wizards" dynamic have utterly saturated and permeated our cultural landscape.

So if you experience these things in reverse chronological order, once you get back to the "originals" it's understandable if you wonder what the fuss is all about.

For those who did experience things in roughly chronological order, there's a real thrill and nostalgia attached to these utterly game-changing works. And obviously there are lots of other folks who enjoy that kind of uh, cultural spelunking or whatever we want to call it. There's a lot of fun to be had if you enjoy exploring art that way.

On the other hand... there's no reason to do it that way either. Don't listen to any stupid old nerd who tells you that you have to love Blade Runner or some other retro-ass thing.

If everybody just worshipped the past we'd never come up with anything new.
Also some designers throw in too many features because they want to fill space in the design.
BulletNotes: Open-source note taking app
This is not a FE thing. Plenty of BE devs who don't know HTTP from their arsehole.
> hope we can see some government movement about this at some point.

I do too! I get so sick of Ticketmaster's fees upon fees upon fees and "sorry, your browser isn't Chrome" junk.
>Why hasn't there been more adoption/movement of OpenPOWER or OpenSPARC?

For the same reasons RISC-V had to be created. This is documented in the paper Instruction Sets Should Be Free: The Case For RISC-V[0].

0. https://www2.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-...
What is the problem with 1-2 days delay?
There are a gigantic number of widespread misconceptions that anyone who spent even a little time on the issue would immediately notice are false.

Phil Plait used to complain about people who told him the moon wasn't visible during the day.
Ticketmasters is an excellent book about their history, some of which has been touched on in the comments here. https://www.audible.com/pd/B00B2S9K46
> Have you ever implemented a database?

Yes, multiple times, in both American companies and in Chinese startups.

> Most operations (filtering, joining, indexing) are purely integer workloads with large working sets that are likely to stall the processor while waiting for data.

That is not a justification for having only one FPU. Let's use logic here, it is not that hard.

> That's exactly the scenario that was targeted with that processor design, many threads per core such that the cores are always busy even if some of the threads are stalled on memory accesses.

Again, that doesn't justify the stupidity of having just one FPU.

> It wasn't meant for single threaded workloads or HPC workloads, and afaik wasn't marketed for those segments.

I am now totally confused. You are defending the stupid T1 design which only has 1 FPU for its entire processor capable of running 32 threads in parallel, yet your argument is that such design is meant for multi-threaded workloads? I thought you need multiple FPUs to truly parallelize those multi-threaded workloads.
I don't need to know assembly to write a web app - it's totally magic, and it's fine.

However, if I am using an abstraction like an ORM without understanding what is happening with the database under the hood, or why it's getting slow all of a sudden, it is bound to bite me in the ass.

I shudder to think of how much money and energy the world is burning every second just because of this one alone.
$5,800 is almost the exact price a friend of mine paid for his Pentium 66MHz back in 1993 (1994?).

That was probably closer to like $12,000 in todays money
> “ancient Caucasian Albanian temples.”

And Albanians in the Balkans claim they are indigenous people there...
> As a developer I hate "precise" and "complete" requirements. Usually these extremely detailed roadmaps are just fairy tales.

Requirements and roadmaps are very different in my opinion. Requirements say what the product needs to do, scaling and/or response time targets, systems or needs to integrate with, etc. Roadmaps are either a high level plan for where the project goes in the future or a list of seemingly arbitrary deadlines.

Both have their place, but in my experience the right balance has been precise and complete specs with a high level, flexible roadmap.
>We, people who really understand the technology that the world runs on, are a slowly dying breed. We are still here as tech leads, managers, directors, business owners.

There will still be people at e.g faang/semiconductor companies

that do this stuff day2day and even push advances in those areas and have already created solid training materials for younger employees

If you're worried that this knowledge will disappear, then feel free to write it up in form of tutorials.
I wonder what a VR version of Maniac Mansion would look like.
Building a port in the north sea sounded like a terrible idea to me at first.
However, I asked chatgpt and Bard and they both state that Delta-v needed to reach orbit is only 9.7 km/s versus 9.4 km/s from cape Canaveral.
It's a disadvantage, but it doesn't sound like a deal breaker.
I talked to a guy who "managed software development", and when I asked him about the resources om their developer machines (some kind of VM), he got angry at me when I laughed nervously when he didn't know what RAM was.

No wonder a lot of modern software is terrible.
As a 15+ years webdev my recent projects in the front-end are almost pure "vanilla JS" (Just JS) + Html, and CSS with only Petite Vue / Alpine on top.

I find the modern Vue, React etc. stacks absolutely insufferably complex and prone to breaking in 1000 places each time you upgrade some package, or change som random thing in the already stupidly complex "Tooling/Build" chains people are setting up by default.

And it's because no one, not even experts in the field seem to understand 5% the stuff that is contained in these monster codebases.

I found myself using 90% of my time on this setup and tooling, and i'm pretty sure most devs do not need these.

I'm wondering if i can somehow pivot into making only these elegant products for customers. Have anyone done this as a solo dev, contracting or in an agency? Maybe make a "frameworkless" agency? Will hopefully save my sanity and my career.

I find the code much easier to read, the codebase is way smaller, and the app's can do the same thing. You can always pull a library here and there if needed.

Also coding and putting together a project is suddenly fun again, and it seems most languages; CSS, JS etc. are now so mature you can do almost anything with them without the bloat.

And as a bonus you actually have time to understand the different underlying concepts like back in the day instead of using weeks in the issue trackers and playing tetris with dependencies.
Without abstraction, you have to re-invent the boilerplates everytime, everywhere.
I think Twitch doubts it too, that's part of this strategy. They tell you you are free, contingent on these guidelines being followed (but they're not rules). They then present vague conditions which seem unenforceable and impossible to follow. They can and will enforce them, you just don't know how, why, or when -- so you play it safe: cripple the experience on OtherPlatform, or, as that's too much effort, just don't use OtherPlatform. Problem solved!
Software simply mirrors the development of modern society. Highly complex and relying on countless abstractions to tame that complexity and be able to operate.

This design is sort-of working under plain sailing conditions (lots of available resources, booming markets, peaceful cooperation). But it is very non-resilient under stress (subdued expectations, broken promises, resource scarcity, hostility and strife).

Remember the pandemic? It was painful lesson and we like to forget pain. But it was an instance of our abstractions failing at a global and systemic level. Broken supply chains, panic, implosion. Thankfully it wasn't the worst kind of negative development but it shows that in the way we design essential pieces of the economy we are basically simply ignoring entirely plausible scenarios.

Now, how are we to respond to this momentous challenge? We can't go back to some low-tech autarky. People cannot build and program their own silicon from ground up (though it would be really cool to be able to do it at least as a proof-of-concept).

The gist of the right approach seems to me is to make sure that abstractions are tethered. If you need dozens of pieces to be in place to deliver something, the combinatorial possibilities of some of them not being available grows exponentially. If you need the latest and most expensive gear to operate this means the long tail of humanity is left behind.

Another analogy might be the drastically different structures you can build out of carbon atoms. You can have graphite layers that peel off at the slightest pressure or you can have diamonds that are the hardest of them all. The difference is the more connected nature of the diamond lattice. The different abstractions should be really fitting together very tightly with strong bonds.

Don't be like graphite, be like diamond :-)
I wish we could somehow get away from estimates where the expectation is precision and instead talk about a spectrum of possibilities (i.e., best case, worst case, and points in between). As the journey to the destination gets longer and more complex the range of possibilities increases. Why do we continue to pretend otherwise?

That aside, more accurate running scoring (if you will) would also help. Engineering is asked for an estimate but engineering knows that they don't have absolute complete control end to end of everything. Someone else somewhere along the line is going to cause delays, but the estimate stays fixed and engineering remains accountable. That's not helpful in the short term or long.
Against Ticketmaster specifically.
Okta messed this up big time. Companies get breached all the time but how they handle the breach shows the maturity/mettle of the leadership team. This is the second time their comms strategy failed miserably. They need to immediately re-evaluate their incident response operating structure. Cloudfare has some good suggestions.
The Problem with Jon Stewart cancellation highlights a problem for Apple content
See also:

DIY Git in Python (https://www.leshenko.net/p/ugit/) - see https://hn.algolia.com/?q=leshenko.net for discussions
> A very different time, thank goodness for DEI now

or a picture of senior leadership at Google.

plus ça change, plus c’est la même chose
> Can you tell whether this will return exactly one line for each customer ?

I can tell it will return one row for each Customer.B.

If Customer.B is a candidate key of Customer, that will also be one eow per Customer.

> If INNER JOIN + GROUP BY was the dedicated construct to do so

The dedicated construct to say what you want one row per is GROUP BY. Yes, it operates by columns, not tables, so what it means in table terms is schema-dependent.

> each value of column Customer.A must also appear in column Sales

Well, yes, that’s what INNER JOIN means. The dedicated construct to assure that every row from the first source but not the second source table is included in the result set before filtering by WHERE is LEFT [OUTER] JOIN.
There’s a spiritual sequel called Contraption Maker: https://store.steampowered.com/app/241240/Contraption_Maker/
Ludricrous estimates are usually a symptom of other organizational quirks.

I'd compare it to the military's $435 hammer [0], from the outside you'd think it makes no sense, but that's the logical end of a series of processes that all somehwat made sense on their own.

A common issue I've seen is devs having to put their head on the chopping block when making estimates. After the second or third time they get seriously punished for blowing pat deadlines, they'll happily go with around 10 times their own estimate. But there's so many other incentives where going with a "done in 2h" estimate is just a bad decision.

[0] https://www.washingtonpost.com/blogs/wonkblog/post/the-penta...
The $2,500 MRI That Told Me I Might Drink Too Much
This feels like a phishing ploy to me. Isn't anyone else hesitant to provide their personal data to such sites? It's like something one would see on Facebook.
I said they bombed a church. You said I should reconsider my sources. My source was Reuters, quoting the Church representatives, saying: "...was hit overnight by an Israeli air strike".

In no shape or form was it anywhere implied that the church no longer exists, just that it was bombed. The quote from a non-hamas source in a respectable news source confirms it was hit. That you're poorly attempting to make some kind of an argument that never was tells me you have no leg to stand on.
https://archive.ph/nzRdd
I see. "Look, a joke about racism! Let's ignore that and make it about the white man instead."
I loved Thief and Thief 3.

Never played 2 but always hear it is amazing.
>Is there anything I could be doing better here?

Yes. Not give a fuck about the code debt and quality, and just rush out something that barely works. That will keep them satisfied.
It's weird how the final season of Picard is the best one, because the first two were so so bad.
OP, every single one of your submissions is a blog post of your own, and every single one of your comments is a non sequitur on one of those submissions, apparently in an attempt to boost it. Get that kind of drivel off HN.

Also, this particular article
is nearly 100% insight-free, rehashed, productivity influencer pablum.
I don't understand what is happening here. How is working with the audio for example?
'Fire Weather' Author John Vaillant: What I Told Parliament
> It's not up to the employer.
> There are states where paid sick leave is mandated, and the state law explicitly lets workers take sick leave for _ANY_ reason related to health.

My comment wasn't on defining what constitutes as "sick," but the parent asked what constitutes "abuse." As there is no law which defines it, yes, it unfortunately is the employer that will determine what "abuse" means.

> Aside from being a huge red flag, what's stopping you from just putting in "mental health" and not being very specific?

Requiring doctor's certification that one was ill in my (unionized) workplace. If they don't like the explanation, paid sick leave law or not, pay is refused. Challenged in court and upheld.

I refuse to think this is the only employer in the US that does it. Cases like these however have situations that lead to them. I surely don't think it's right, but do see where if someone's not showing up to work because he's "sick" and then posting photos of having a good time, and doing it often, it doesn't look good. In fact it's stuff like that which lead to such policies where I work.

A search got me this, so obviously it is done elsewhere:

https://www.businessmanagementdaily.com/10847/checking-up-on...
https://www.quora.com/Can-your-employer-check-if-you-re-real...
> It's not even particularly necessary for 95% of DB Ops.

Let's say I have databases full of some sensor data that need to be processed by some fancy SQL scripts to crunch those numbers. Tell me how I am suppose to get that done without using floating point.

With only one FPU in mind, tell me how to parallelize such processing and full utilize all those cores.
Feedback: love fantasy do not see the problem. The only thing you need to remember is that communication usually fails except by accident. I have seen many definition change meaning during my life it is just part of life. If you are content that you have the same definition you usually do not.

https://en.wikipedia.org/wiki/Wiio%27s_laws