skysight-inc/HackerNews huggingface dataset:
A number of pretty important things missing from this article:

1. The administration of publishing rights is often really badly executed. Investors like Hipgnosis are really good at finding both historic uncollected revenues and making sure the catalogue is getting very penny it is due.

2. A lot of these investors are not “bankers”. The founder of Hipgnosis is a very shrewd and very successful music industry artist manager. Many of the other acquisitions are by music conglomerates. Eg Sony has spent a huge amount in the past year - hundreds of millions.

3. Aggregated data is hugely powerful in valuing catalogue.

4. Streaming is a market share game. If you have more market share you get a bigger slice of the pie. Streaming revenues from the significant platforms are not based on number of streams directly or minutes listened.

5. There are legislative changes going on just now which could radically shake up the publishers share.

6. A big big issue with publishing revenues revenue leakage and multiple commissions. A Collective Management Organisation handles local royalty collection - and takes a commission for doing so- but before those royalties hit the bank account of the rights holder there may be several other people commissioning. Rights investors can establish direct relationships on a territory level meaning double/triple commissions vanish, vastly increasing the value of the revenue streams.

7. It’s very easy to assign asset value to music rights because there’s a HUGE amount of detailed data. People aren’t simply sticking a finger in the air.

8. I personally believe that publishing rights are undervalued and will increase in value quite significantly as we enter the next phase of music consumption, linked to metaverse/tokenisation/digital fandom. There are huge opportunities around digital artefacts in the decade ahead. If you’d asked me a few months back what I thought about the metaverse and NFTs in the context of music I probably would have said “emperor’s new clothes”. I’ve spent a couple of months doing some pretty detailed research and I now believe there are really significant opportunities opening up. Kids who are 12 years old now - so younger than instagram - are growing up in “blended reality” where physical and digital existence are completely blurred, digital existence is a significant part of identity and physical artefacts may begin to be seen as inconvenient and unwieldy. That opens significant opportunities for digital exploitation of publishing rights. Want an interactive 3d music related artwork for your metaverse space? If that uses lyrics you need a licence.
Moving people moving to Berkeley is good for the environment. It has a low carbon footprint per resident: https://coolclimate.berkeley.edu/maps

To protect the environment, we must allow increased urban density so people are not forced into further suburban sprawl. Doing it in a place like Berkeley with limited heating/cooling energy needs is a no-brainer.

The fatal flaw of CEQA is it doesn’t contemplate the environmental impact of not building the project. Ultimately, the earth suffers as more damaging development occurs in less-regulated places.
not directly, no, but one of the most common ways to maintain a persistent IRC session is to ssh to a server somewhere (typically not on a residential or dynamic internet connection) and then run your CLI irc client like ircII, bitchx or irssi inside of a gnu screen session, or inside of tmux.
Draw.io is good and flexible
My emphasis was on the high-performance aspect, not the platform itself. It's not a trivial problem to host videos and have them easily watchable in a way like Vimeo does it. Bandwidth, streaming tech and other aspects can't be done adequately by the average development team without significant expense.
The motion parallx supported here makes it more natural to consume such content and when you drive the motion yourself (using our Vimmerse player) this takes you to a whole new level. For some content, you really feel that you are present there!
No.

Diplomacy is not crime.

Try living in a small country!
Yes, you need to set the RPATH correctly when building ELF executables and shared objects. You would only not know this if you were only ever building things to install into /usr with dependencies on things in /usr.

> Curious observation: dynamic linking on NixOS is not entirely dynamic. Because executables expect to find shared libraries in specific locations marked with hashes of the libraries themselves, it’s not possible to just upgrade .so on disk for all the binaries to pick it up.

Dynamic linking is not just about being able to upgrade without re-linking. Dynamic linking is not even primarily about that, not anymore, if it ever was.

Dynamic linking is more than anything about semantics that no one has bothered to add to static linking!

Static linking for C is stuck in the 1970s.

Dynamic linking for C makes C more like C+ -- a different language.

Specifically:

- with static linking symbol conflicts are a serious problem

- with dynamic linking symbol conflicts need not be a problem because with direct binding (Illumos) or versioned symbols (GNU), you get to resolve the bindings correctly at build-time and have them resolve correctly at run-time

- at build time you get to list just direct dependencies, and the linker does the rest -- compare to static linking, where you have to list all dependencies only in the final link-edit and then you must flatten the dependency list into some order, and then if there are conflicts, you lose.

For all those who keep harping on how static linking is better than dynamic linking, what I would suggest is that what must be done to make static linking not suck is to enrich .a files with the kinds of metadata that ELF adds to shared objects so we can get the same "list only direct dependencies" semantics when static linking as when dynamic linking. And I would note that libtool does this, just... very poorly.

What I would do to fix static linking:

- have `ld` add a .o to every .a that includes the `-L`/`-R`/-l` arguments given when constructing the .a (normally one does not do this when linking statically!)

- have `ld` look in every .a found when doing a final link-edit to recursively find its dependencies, and, most importantly,

- provide the same direct binding / versioned symbol semantics as in dynamic linking so that external symbols in dependents are resolved to the correct dependencies in the same way as in dynamic linking.

Notionally this is quite simple. But adding this to the various ld implementations would probably be rather a lot of work. Still, if people insist on static linking, this work should be done.
I learned a lot about this stuff from this paper:

https://lmax-exchange.github.io/disruptor/disruptor.html

I think the Disruptor is probably still the most ideal approach for serializing multiple producers on an x86 platform. The core idea is to decouple the producer and consumer so that they do not contend over the same CAS variable (position in a ring buffer). If you only have a single producer, the CAS goes entirely uncontended and you will get tens to hundreds of millions of items per second without issue. Even with multiple producers, the figures are fairly incredible.

The trade off is that you basically have to sacrifice an entire core to busy-waiting if you want the world-class latency performance. Alternatives can yield or wait on conditions, but clearly would be slower.
Swift.org Website Is Now Open Source
Goroutines and channels seem comparatively simple compared to the representational symbolic changes involved with generics, which make the code look and read more like Greek. The beauty of Go is (was) largely in its simplicity and python-esque (or maybe better than python) readability.

With generics, reading and reasoning about code becomes [even] more challenging.

Personally for me, at this juncture I'm finding that for new projects I might just as soon spring for Java or maybe even prefer it to Go. For the straightforward mvn-style dependency management, if nothing else.

It's all moot now, though. There's no going back, this puppy is cooked!
Know anyone who ended up rich thanks to Y2K? Possibly not since chances are they went into early retirement.
OneDrive for Business File Size Limit
Rome, Zombie City
I found this thread interesting, few things that stood out:
The outputs were really good
The shareable link shows both input/output.
"I don’t care as much about “hidden truths” as I do expanding my understanding of self and its relation to the world"
I run around the house updating every clock I can find early on the Sunday morning. I update the clocks on rental cars if they're wrong. I'm not otherwise a super detail-oriented person. Clearly this is some kind of personality test.
My kid doesn't go to sleep earlier just because the sun sets at 5PM. In fact, he has gotten used to spending most of his evenings in darkness, not being able to go to the park after school to let off some energy makes him go to bed later rather than earlier.
Not everyone is a morning person, I'd rather have my daylight in the afternoon where it's actually useful to me. I suspect that most people agree with me.
Is there really any software yet that uses the V?
For that one rare occasion, obviously.

I can't find that code but IIRC it was me working with with AWS SDK and it infamously exposes all sort of stuff as *strings and *ints because there is no sane way to have Maybe<string> in Go. So I had a whole screen of those `if resp.foo != nil { v = *resp.foo } else { v = fallback }`, sometimes deeply nested (for resp.foo.bar[idx].baz, because no null chaining operator either). Yes, a purist may argue that's AWS SDK problem and they should've went with something else, and that Go's decision to not have ?: still stands true. Sadly, I haven't had luxury to wait another decade until Amazon maybe sorts it out, yet I still wanted to write something I could read back.

I don't disagree typical use results in poor readability. I'm not gonna put those ?:s just about everywhere. Yet I do think that there are sometimes infrequent exceptions where ternary would've been objectively better.
I worked a blue color job where I was at work at 5:30 AM, sometimes 4:30 AM. The fact that it was never light out when I went to work, even when standard time was in effect, didn't bother me much.
> You always see 10-15% cuts leading up to an IPO

No you don't
Never brush your teeth straight after eating/drinking. Give it an hour at least.
> but I'm genuinely curious how the real software development practitioners would approach an open ended task like this

I just panic and procrastinate. Some of us never grow out of that.

But that aside, pick one of the mature traditional "batteries included" web frameworks to get started. It's never going to be the ideal architecture, but it's not going to be an awful one either. Really learn how to use it, and keep the code quality high from the start. Too many projects I've worked on have ended up in a deep hole because people decided to try a whole new tech stack in production without actually learning how to use it first. Learning by doing is great and all, but there will always be a pressure to "just ship it" instead of reworking all the beginner mistakes that will eventually come back and bite you down the line.
I didn’t know this is for the senate to decide, and find that surprising, given that most of Arizona doesn’t do DST at all.

https://en.wikipedia.org/wiki/Time_in_Arizona:

“Arizona does not observe daylight saving time (DST), with the exception of the Navajo Nation, which does observe DST. The Hopi Reservation, which is not part of the Navajo Nation but is geographically surrounded by it, also does not observe DST.[2] For this reason, driving the length of Arizona State Route 264 east from Tuba City while DST is in place involves six time zone changes in less than 100 miles (160 km).”
Alternative is to store the hash in the filename which avoids this.
At least with macOS you don’t actually need control very often.
I think you misspelled sysadmins there. My experience is that, at least in the traditional corporate world, it is the DBAs who connect just before midnight to put their precious SQL servers to sleep during the danger time, since who know how the software will behave in the real world. In some places DST dates are often changed in the last minute, wrecking havoc everyone's calendar meetings and inflicting pain on the Exchange servers admins.
The argument is basically "if the state-sponsored babysitters change their hours partway through the year it will be a massive headache for parents". But if such babysitting is so crucial to a functioning society, surely society can become a bit less rigid to accommodate it?
A reasonable idea, for people living in Europe or Africa.
You are misunderstanding my response too :D

As the other poster replied, time is continuous, and sunrise/noon/sunset changes as you move East or West gradually. There are no 1h jumps like with timezones.

So in any timezone, "noon is noon" holds only for a very limited set of areas exactly at the appropriate meridian. Move 80km/50mi East or West at the latitude of 45 degrees, and you are looking at 1 degree of longitude displacement, or noon being 24h/360 or 4 minutes off.

At the same time, in that same timezone, you'll have areas that have their astronomical noons off by 1h (and even more when timezone is not strictly aligned to the 15 degrees of latitude — in Europe, Western-most parts of Spain are almost 2h away from Eastern-most parts of countries in CET/CEST). But as you cross timezone boundaries, you might go 5km between towns, and have a time difference of 1h even though noon is at pretty much the same time in both towns. Any practical solution is going to be similarly "incorrect" no matter how you construct it.

So in essence, all of this is a convention on what time is most useful for a region: none of it is "sane" or, on the contrary, "insane". It is simply what majority of the people agree to. If you are in a minority that disagrees, yes, tough luck.

Finally, time is there to coordinate events between people. Timezones are there to coordinate our internal biological clocks (and some sunlight dependent activities) to the area we are in. While "continuous" timezones would be most correct, they'd be in conflict with time serving as a coordination tool. And not having any timezones would be in conflict with coordinating our internal biological clocks. Both of these are societal constructs to help with societal behaviour.

So 24 timezones (or 48 with DST on/off) is the middle ground, and while I can appreciate some people will struggle more to acclimatize to one or the other, neither is more correct or more wrong. I personally prefer permanent DST for the same reason others have raised: I like my post-work hours to have some daylight even in the winter, and it seems this is the predominant feeling which is why DST is "winning out".

Basically, all this is to say that you seem to be inventing an argument instead of simply saying "I prefer more daylight in the mornings when adjusted to the wall clock time of the society", which is a fair standpoint to have.
It wasn't supposed to be – Coppola made it because Paramount said either he could make it, or they could give it to someone else, but they were going ahead with a trilogy.

Coppola and Puzo wanted it to be its own film, titled "The Death of Michael Corleone," and believed (rightly) that a duology of Godfather films based on the original novel was the right decision.
de-hypertexting the web & turning into a way to push pixels is a mortal threat to internetworks. personally i think almost amy such tech is evil & only to be used in extreme circumstances. ground lost being web-native is ground lost against user-agency & augmentativeness: of the the most defining & powerful aspects of the web, that the user agent has user power in this client-server system. degrade that at humamities peril.
Play Store’s ‘Play as you download’ is coming to all Android 12 devices
>It's not obviously wrong to break a law to save a child's life though.

I don't think that's a fair interpretation of what was said. The claim made was that they broke the law, which is wrong to do on deontological grounds, especially for the institution tasked by society with enforcing the law. They may be justified by utilitarian ethics, but a police department setting the precedent of "if we believe the need is great enough, we are free to ignore the law" is both wrong and illegal. That's the fundamental principle at stake here - the same base argument that leads governments to suspend civil rights for the sake of security. "It is terrible for these people to die, so we need more power to prevent it." A ratcheting system that cedes ever more ground to autocratic forces. It's not like this process has been particularly hidden from us; there are many here who remember the US before the PATRIOT Act was put in place, after all.

The cost of not beating this thief might have been a child's death. The cost of beating him is instilling a norm that police have the right to beat prisoners. And because the change in societal norms is so slow, and the grief of a dead child so sudden, this always seems like a good trade. You would be a monster for saying that the rights of a car thief are worth a dead child. Until police prisoners have no rights. Until political prisoners have no rights. Until people have no rights.

End-to-end encryption is evil! Only a criminal would want to hide their activities from the police! A social credit system rewards pro-social activity and prevents instability! This state of emergency is only temporary - life will return to normal very soon! A surveillance state is much safer than a free one. As long as you have no issue with the state.

The civil rights we benefit from are measured in the blood of innocents. As cold-hearted as it is to say, if we are not willing to allow innocent people to die to protect civil rights, we will not have them for long.
This is definitely a bubble. What do you think the chances of someone who has spent 12 years at the same job could pass a coding interview at any of the tech companies without any practice?
>Timing of light and absence of light is critical - early morning light exposure greatly benefits people with SAD.

Of course, you aren't getting that in either system; even in Standard time the sun doesn't actually rise in the early morning. You're still going to need the wake-up light either way.

With permanent DST, you'll actually get more of a chance to witness the sun in general, as there's a greater span of time that it'll be available for use when you're allowed outside at the end of the workday.

Up in the dark, home in the dark just flat out sucks for the 4 months of the year these conditions occur; minimizing the number of people who have to deal with that and minimizing the number of days they have to deal with that should be top priority.
Mostly it is just that there are no other kids to play with: yes, we might do it, but if we are the only ones it isn't great for him. But the real big problem is that sunshine in a Seattle winter is a precious commodity: 7/10 even with daylight we wouldn't get to the park because of rain, or its just not pleasant out. The problem with standard time is that 7/10 turns into not going 10/10, it wastes the precious sunlight we do have.
> Also an interesting issue: bots that go around trying to brute force ssh into random IPs with common usernames. My current solution is banning if rapid successive joins are detected.

I should've read this before trying to connect 100 usernames in parallel.
>If you're tired of censorship, cancel culture, and the erosion of civil liberties subscribe to Reclaim The Net.

>btw we removed this problematic search engine

wtf
(note: I am the Director of Data Science at System)

We are building System with multiple personas in mind. While a domain expert might be interested in drilling down to understand the source of every piece of evidence, an average user may just want to understand the system of using pacifier for their newborn.

The atom of System is a single statistical association that carries its context (population, covariates, etc). As you zoom out, we summarize and combine pieces of evidence (through semantic matching and meta-analysis).

This method provides an incredibly powerful framework to tailor to different needs and level of expertise.
The whole lesson of gangster films is centered around regret and the tragedy that befalls the family. It's actually a good test on people and their views of status. If someone emulates gangster bravado, it reveals a lot about them and how they've missed the entire point of the genre.
If time is just a concept, what is the value of DST vs standard time?
The answer is: whatever the clock says, the day rythm of society follows strongly the sun. Permanent DST will shift most time schedules in the long run. Nothing will fundamentally be changed. The disadvantabe is, "noon" will be further off the high point of the sun. Due to time zones, it was not exactly the same in most places, but with standard time the deviation is reduced. Which for example has the practical consequence, that sunrise and sunset is symmetric to noon.
Ask HN: Why does LinkedIn not do keyword muting?
I think LinkedIn is a potentially valuable tool/resource/network. Yet, I can't stand spending more than two minutes on it because of all the cringe/hustle porn/rockstar recruiting.
Does anybody have a solution for this? Muting individuals isn't enough.
I’m an intermediate Nix user - aren’t pkgs usually passed in as an argument so that the caller can choose them? I sort of accepted that verbose command line as a necessary evil of good design.
I think most ravers from that time period have moved on. :)
They just released Scala 3 this this year so hardly stagnant. The community seems to promoting more pragmatic functional approaches recently which I think is going to make Scala much more popular in the future.
If it is all but dead why are news publications still including AMP links. For example, following AMP links without Javascript/CSS enabled has long been an easy way avoid some of them that use "paywalls" to annoy and track non-subscribers (instead of simply denying access through use of password protection). See, e.g., WSJ.
Sure, but this guy wasn't caught planning anything, he was just a rando family member and as the article mentions the cia itself already assessed that was the case, that he wasn't a danger

Yet they decided to use him as a training dummy anyway, why? Because the cia is just fucking evil and it ought have been disbanded in the 1960s with JFK

Anyhow, what I just wish is that more world powers had their own CIAs and dedicated themselves to hunt down and kill US cia agents as needed to defend their national sovereignty and population

The US doesn't understand anything but violence, I just wish there were more tools to deter the US from using it, forcing it to a dialogue table, terrorist country.
Interesting. Someone I know well with bipolar has very predictable manic episodes around the same date each springtime, but they aren't tied directly to the time change I.e. they happen +/- a week or so each year.
>“We thoroughly investigated this employee’s claims and found there was no retaliation,” Google spokesperson Shannon Newberry said in a statement.

It sounds like if anything bad would have happened she would have classified it as "retaliation."
Maybe once you eliminate one level of "boring" code, that just means parts of the next-higher level of code become rote and boring. It reminds me a little of Richard Gabriel's reply to Guy Steele, when Steele said something like "Lisp doesn't need design patterns; it has macros." Gabriel said "That just moves the patterns up a level of abstraction."

(I probably remember that story all wrong. But I like it anyway!)
> but are you at all familiar with the history of pre-CCP Tibet? Their "theocracy" was likely worse than Saudi Arabias