skysight-inc/HackerNews huggingface dataset:
Maybe they are thinking of BAYC and yugalabs.

Yugalabs[0] assign copyright license to whoever owns the NFT on the chain forever.

So if someone mints a NFT, they get a perpetual license to use it however they like. The downside is if they lose the NFT for any reason such as theft, they lose the license as well.

Other NFT projects of yugalabs store data on chain or use a separate storage chain built for permanence. This basically means they cannot take the content down once they have uploaded it and attached it to a NFT.

However this doesn't solve anything unless corporations are forced to accept it as the only way to sell content.

One big problem it may solve for corporations is uniqueness and validation of all license in existence through a ledger. If a company sells their content exclusively via NFT, they can take advantage of immutable receipt system and built in programming capabilities to embed royalties on transfer. This would make it hard for people to sell their copies without giving companies a cut. Legally, that is. Nothing stops them from ripping off a copy and selling it but it would be easy to prove it is invalid and enforce via legal system.

0] Yugalabs is a big NFT IP company valued at 4 billion. They are behind monkey jpegs which are called BAYC.
Mercedes-Benz Bionic – the “fish car” concept of the 2000s
Not necessarily true. At least all my medical records in all the facilities I visited in the last 5 years were digitized and I live in an eastern European, post-communist country.
As someone working across tech and natural disasters, and with a background in engineering, this doesn't make a whole lot of sense from a tech, engineering, or response perspective.

High speed mesh networks exist, and commercial operators exist whose tech can cover 160km / 100miles with a single airborne repeater. A repeater on a hill in the distance is enough. Local network without that line of sight, but in bands like Cat-M are good for 16km / 10 miles with a single local repeater. In a mesh configuration 1 mile or 1.6km between meshed nodes is quite achievable. These are all band and power dependent, with differing limitations of each.

What is quite clear, however, is that disaster areas are messy, smoky, wet, muddy, windy, inaccessible, chaotic places. Requiring a camera to watch for wiggling requires a clear camera, a high power computer to interpret the dance (at 93% confidence, apparently), and motors at the other end to do the dance. These are all very power hungry things in what is potentially a power poor area. Why would you not look at a mutil band local mesh network with exit nodes and low power requirements already? That's what we are using for human and machine communications, and we have had very few issues with newer tech achieving full data comes in signal deprived areas. When it comes to machine to machine comms it's far more efficient from a data point of view to send the details over the air than it is to do a dance and misinterpret with a dirty camera whilst burning power.

This seems like a group of researchers who don't understand the problem space properly and have come up with a pie in the sky solution that is quite impractical. Speaking frankly.
I must say, that mediocre article lead to very interesting comments.
Yes. But, frankly, async is also simpler in JS than in Python: e.g. no need to start a reactor loop.
This definitively signals that Apple devices are no longer secure, terrible move.
I'm interested in NixOS but it only supports systemd.

Seriously, init systems like OpenRC do one thing and do it well. Where have I heard that before?
You could even have the content shared over public BitTorrent networks, encrypted with a symmetric key and then store a personalised asymmetric decryption key (the symmetric key encrypted using the owner wallets public key, ensuring only the current owner can derive it from the public NFT data) in the NFT. You would re-compute this asymmetric key for the new owner during the TransferNFT function and store it in the contract.

Yeah, the symmetric key would probably leak quickly, and the content decrypted and shared, the point here is to make the system so convenient and simple that it discourages piracy, which you can never fully beat anyway.
They are not using waste heat but low-cost electricity. A system heated to 500C is not running on waste heat.
The other part of that statement was 'easily accessed by a mobile device'. That's a much bigger problem, since now you're running a server, and you've got to secure a server.
DBT Helps Data Engineers Operate Like Software Engineers
You can sort of tell from the other responses, but really the core of this argument is not the one you think it is: You think this means it is less appropriate for New York because of this fact. It is the opposite. Your population density is higher, so these types of solutions are easier and more cost-effective. This makes the fact that you don't already have it seem even more incompetent, which is the opposite of what you wanted to achieve.
Sorry, we don't accept Sony Media NFTs, you need a Sony Xperience Plus NFT. The old ones were phased out last year.
It might be that the person doing the praising is not brilliant either.

Praise is such an ingrained part of our culture, I feel like my generation has been praised throughout our lives for every little, entirely normal thing we do. It takes so very little. It feels hollow and fake, social norm that is followed.

I cannot construe praise to be anything beyond "affirmative, the task was done and there was nothing so wrong with it that it needs mention".

I don't like to receive "high praise" it feels patronizing at the very least.
True but STEM still usually lends itself to less social interaction than many other jobs such as education, nursing, arts, etc.
Poland, Which Is Nowhere: The Fifth Dimension of Eurasian Time
I can also use stuff like Tasker on Android.
I really love listening to the Donkey Kong soundtrack. It really has something that just relaxes you, or pushes you to the programming limits. It has tracks for every kind of mood. I listen to it on the train or when I travel to work to gain mental focus for the day. In the office, I switch to a different, more upbeat song to create tension. With passing time I switch to Donkey Kong songs with increasing tempo. My hands are literally flying over the keyboard and I am in complete balance with the code. Some of my coworkers say I'm "wired in". I wouldn't disaggre with that.
At some point, when the evening is within grasp, I slowly decrease the tempo of my Donkey Kong songs to calm down step by step. On my way home I switch into chill-song mode again. During the night I let the aquatic ambience of Donkey Kong Country guide my dreams.
Highly recommend it to everyone!
Right but if they post just that part, they're probably heavily implying that now is not the time to optimize. I've seen way more people using it to argue that you shouldn't be focussing on performance at this time, than saying "sometimes you gotta focus on that 3% mentioned in the part of the quote that I deliberately omitted"
When the sidewalks are melted, it becomes waste heat. The rest of the year, it is waste heat. No matter how cold it is, if you accidentally leak heat it is wasteful - even if the side effect is something you may otherwise want.
I'm already benefiting from IRCv3's server time extension [1], since I use ZNC and get the actual timestamps for each message that I get from its buffer that way. You have capability negotiation [2] at the core of it all, anyway. So even if you end up not liking some of the new features, your client should ideally allow you to just turn them off.

[1] https://ircv3.net/specs/extensions/server-time
[2] https://ircv3.net/specs/extensions/capability-negotiation
> What does `make_pizza()` do? It could be a lot or it could be a little. It could have side-effects or not. Now I have to read another function to understand it, rather than easily skimming the ~four lines of code that I would have to repeat.

This is not a problem of DRY. This is a problem of wrong abstraction and naming. If the function is just four lines, it could easily be named `make_and_cook_pizza`. In the alternative scenario where those four lines are copy pasted all over the place, one is never sure if they are exactly the same or have little tweaks in one instance or the other. Therefore, one has to be careful of the details, which is much harder than navigating to function definition, because in this case you cannot navigate to other instances of the code.
I agree, especially because there are people out there doing hard work all day who earn a fraction.

We sit in nice offices, sipping coffee and play with computers..
Misses the most important reason.

Repetition creates symmetrical cases. As they say in German, 'einmal ist keinmal' -- once is never. Overly DRY code is incredibly non-educational.

Why?

Because you learn by comparing and contrasting -- if you can't compare, you can't contrast, and therefore, you cannot learn.
> explains why sputnik the vaccine from Russia was developed so quickly and was effective

FYI Sputnik clinical trial results were based on clearly faked data, and that vaccines effectiveness is highly uncertain.
If you were to look at the website of any major digital infrastructure provider – from Digital Realty to Echelon, and Vantage to Kao – you will find a page dedicated to that company’s environmental, social, and governance (ESG) commitments.
Nope, they just use a single national health insurer instead of many private ones. This changes the problem from many-to-many (as is in the US) to just many-to-one, which is immensely simpler.
Until you end up with multiple similar pieces of code, that seem to do exactly the same thing except for a few small changes... and you wonder if maybe all the other copies would benefit from those changes too.
> This sounds dumb but it just simply is much harder to keep context about what's going on around if you can't refer back to it because it's on the same screen or one short mouse scroll above or below your current screen.

To note, a common effect of not DRYing functions is an increase in local code length.

In many code bases that lived long enough, that means screens and screens of functions inside the module/class files. It is still easier to navigate than between many files, but not by that much in practice (back/forth keyboard shortcuts go a long way to alleviate this type of pain)
Yes, you can do it that way!

We also cover parser combinators on our blog for the interested: https://serokell.io/blog/parser-combinators-in-haskell

And if you want to see what are the benefits of this approach over parser combinators, the second part of this series covers a little bit of that: https://serokell.io/blog/parsing-with-happy#happy-vs.-megapa...
Electret
> Think that solution scales through the entirety of society?

It does when I need to get a repair for something I bought that is still under warranty.

EDIT:

Also: does keeping a cryptographic key safe scale through the entirety of society?
I agree, this mode seems like something most people could manage without difficulty. Amusingly, my (non-Apple) system is much more locked down than this and isn't exactly unusuable IMO, although some things might be harder to manage on a phone.

Microsoft did some tests for Edgium's "Super Duper Secure Mode" and found that disabling JIT improves real world performance more often than it makes it worse (and usually makes no difference):

https://microsoftedge.github.io/edgevr/posts/Super-Duper-Sec...

Diabling JIT makes it possible to enable some additional exploit mitigation methods. A follow up article mentioned that few people who tried it noticed a difference:

https://microsoftedge.github.io/edgevr/posts/Introducing-Enh...

"It is worth mentioning that when we originally had this idea, we doubted our Microsoft Edge peers would even consider it. We quietly made changes to our browser without explicitly telling them the specifics and then asked them weeks later to see if they noticed the change. They would always say no, and only then would we inform them that we disabled the JIT. After surprising multiple developers in Microsoft Edge, we got the support needed to try this experiment. One can’t help but wonder what other well established assumptions about users and the web we should reconsider."
"I wonder, why doesn't Apple (and MS, Google, ...) throw all their weight into the ring and lobby for making selling exploits commerically a crime?"

I would be strongly, strongly opposed to this.

It is a clear-cut free speech / first amendment issue.

If you don't believe me, just imagine yourself describing the pseudocode of an exploit to someone over the phone - or sketching out the details of a vulnerability in a short note.

I believe we won't get to this place because we have the first amendment but I would really love to not waste ten years fighting about it ...
Great write-up.

What I don't understand: Why do you let your users run downloaded executables, at all?
Being no frontend dev myself, the rare times I have to do a webpage I go for jquery and bootstrap. May sound old-fashioned, and perhaps it is, but it works.
Absolutely. Cruise goers eat and drink on the ship and have a few hours during the day to quickly hit all the sites - thousands all at the same time.
Portions of NYC are heated by pipes. ConEd operates the largest commercial steam system in the world.

https://en.m.wikipedia.org/wiki/New_York_City_steam_system
> I suspect any developer reading this is aware of the DRY principle because it is just so ubiquitous. If not though, you just need to know that it stands for "Don't Repeat Yourself" and is generally invoked when advising people to not copy and paste snippets of code all over the place and instead consolidate logic into a central place.

Well, no.

What you actually need to know is the next layer out: DRY stands for Don't Repeat Yourself, sure, but Don’t Repeat Yourself isn't the rule, it's a short phrase that is supposed to be a memory cue for the principle “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system”.

If all you know is “Don’t Repeat Yourself”, you don't know the principle, and you can neither apply nor critique it.

#1 is simply applying the memory cue as if it were the principle. Yeah, don't do that.

#2 is, well, no, you only refactor to extract a bit of knowledge to a common place where it is immediately reused: there is no presumption of reusability, it is demonstrated.

The specific example they use of how this might be done wrong is...so bad.

Starting with: the example code that they suggest is bad design but works does not work.

make_pizza([left_topping, right_topping])

gives args a length of 1, not 2, but their function definition relies on it having length 2, and using that to distinguish from the simple case.
The whole reason laws exist is because we recognise not everyone can be trusted to act in a decent manner. The law gives us a way to codify what "decent" means and to explain to folks what we expect of them (as well as consequences for when folks step outside those boundaries).

What I'm trying to say is that no, it is not silly. In fact the entire civilised world is built on the premise that laws are required.
You can get retromusic streamed on Slay Radio, Nectarine demoscene music or scenesat. I have been using Slay Radio for near 20 years. C64 only.
https://tailwindui.com/ - lots of pre-made templates using tailwind css. Some are free, but the more advanced ones require payment.
About Three-in-Ten U.S. Adults Are Now Religiously Unaffiliated (2021)
Compact Halo Object
Most Apple-centric enterprise workplaces use Office. With the exception of some features that are specific to O365-specific licenses, it has feature parity with the Windows version.

LivreOffice does not do PowerQuery, and while it ‘opens Excel files well enough’, it probably only has 70% feature parity at most.

They themselves claim that it has ‘tens of millions of users’…

I’m not saying it’s a bad - or new - product. It’s just yet another customer requesting to install something. Very, very few (exactly zero) workplaces I have visited in Oceania and South East Asia are using it.
Streaming services have no pretense of ownership. You can watch whatever they happen to have as long as you keep paying.

When you buy a title on Amazon, Apple, etc., the digital services are selling you on "ownership". In theory, this will be in your account forever (without any money changing hands after the initial transaction). The reality is obviously not so simple.
This reminded me of an old classic, “Starbucks does not use two-phase commit”: https://www.enterpriseintegrationpatterns.com/ramblings/18_s...

Previous discussion of it on HN (2010): https://news.ycombinator.com/item?id=1554126
> Someone interested in $THING would be better off learning $THING directly rather than tip-toeing around it.

This is not really the universal truth that you think it is. I remember when I learned to drive my father started me on his car with a manual transmission. I skipped gears, Started from a stop in 3rd gear, and had a whole lot of frustration trying to deal with both the concepts of driving the car, the rules of the road, and trying not to completely destroy the clutch of the car. I switched to learning on my mother's car, which was an automatic. I gained confidence on the road and then I went back to learning how to drive stick. This resulted in a much easier time for both me and the clutch. So no, I wasn't better off learning it directly. The same can be said for something like walking and then running, or learning how to program. They typically don't start students off learning to write Assembly even if their intent is to be an Assembly programmer. Training wheels on a bike exist for the same reason too. Can people make this approach work? Sure, but that doesn't mean it's better. In fact I think in quite a lot of cases it's way worse.

> they get very frustrated by the real Vim

They are using the "real" Vim. You being weirdly gatekeepy about this doesn't change the fact that they're using the same application that you are, except they loaded a config different from yours. There is a list of different keybinds from vanilla vim in their documentation and you can disable them with one line in your config. Pretty much all the typical vim paradigms are exactly the same.

> they try to replicate their previous ready-made config anyway.

kind of their prerogative and one of the nice things about extensible programs like vim is that people can do exactly that. I could change vim to use CUA commands, be mouse-focused, and default to insert mode and I'd still be using vim.
Bit of a tangent, but it's nice to see a project with a googlable name. If this were started today it would be called Avocado or Potato or something like that.
To the sibling commenters here: "traditional vaccines" are much more than killed-off viruses. They can be made of manufactured sub-units of viral proteins for example. There has been continuous development of vaccines ever since the first ones were developed.

In general, the problem is not getting (parts) of the virus into the body. This can for sure be done in many many ways. It's getting the immune system to care enough to start manufacturing and remembering the antibody formulae for future infections.

One traditional way is to add an "adjuvant" to the viral subunits (or similar), which is designed to trigger the immune system. In either case, usually you do require to trigger some kind of local inflammation. When your arm hurts after a vaccine injection it's a good thing.
Yes, e.g. when I need to add a new line/block of code, I just search for a pattern and edit there. When refactoring demands heavy structural cross-module changes, I just don’t do it honestly. What’s dead is dead, but I may do a “guided” side by side rewrite.

I don’t touch snippets unless there is a good reason to do that. They are my general templates, not per-project tools.

In most of my code, the need for refactoring was mostly a consequence of building a too rigid high-tech structure which with time turned out to not fit the job anyway. Figured out I can avoid it by not building it, and antiDRY also plays a role in it (albeit mostly psychological).
I just read that you didn't want to troubleshoot html, css and js, so my goto toolkit for simple UIs might not fit your bill, but hear me out :)

At work, when I do internal tools, they are usually well received.
They also pass just below the threshold of having their looks be judged.
They're not ugly, because they're almost not there.

Very plain HTML: HEAD+TITLE, H1, H2, UL, OL, A, IMG, INPUT, BR, TABLE, P
Javascript as needed, usually embedded in the HEAD
There is no CSS.

There's simply no design to attack, no colors or alignments to disagree with. It exposes the interface to communicate with the backend, nothing more.

It's also the fastest and simplest way of getting stuff done, if you don't need to expose it to "end users".
I would say the opposite, most "good" house music, or house that is considered tasteful, doesn't have lyrics. It may have some voice samples, but nothing too distracting. There are obviously many exceptions to this rule, but you can generally consider most house music to be instrumental.
IEA warns China will soon produce 95% of the solar supply chain – Seeking Alpha
Strictly speaking the backup must be based on what you actually have bought (i.e. if you strip the DRM from your purchase and store that, that's fine). That means you cannot download essentially an identical copy, that's still naughty. I know this is idiotic, but apparently whoever writes laws doesn't know this.
Parolee Single-Handedly Attempts to Break Up Climate Change Protesters
Idaho summers are very hot. The district heat only runs part time. It is all waste heat from the power plant. There’s ample hydroelectric and wind power in the region as well. I’m not sure if the plant does demand shifting over the course of seasons but it could only run in winter because it runs on biomass and employs students. Many campus facilities are essentially jobs programs for students. The mission is experiential learning. I got a B.S. in business that included welding.
Just posting this in case anybody else experiences it too but I've found that listening to a 140 bpm instrumental track on a loop puts me in the zone very quickly.

It doesn't even have to be long track, even a 30s loop does the trick. The 140 bpm is like a sweet spot for some reason though.

I dunno if it's because it's like a video game music which repeat over and over but it really helps me focus and get in the zone everytime. Anybody else have something like this to share?
This works until someone updates code in one place, but not the other, and subtle bugs are introduced.

DRY / single source of truth offers a certain protection against such bugs.
Honestly? React [0], Tailwind [1] and Vite [2]. Using Vite so setup the environment and tailwind components for css I have never been able to create front end faster than now. It feels like a super power.

[0] https://reactjs.org/

[1] https://tailwindcss.com/

[2] https://vitejs.dev/
Similar issue with Scots, which has many variant orthographies but is frequently written in mostly-English anyway.
Took me a moment to realize that frontend here means HTML+js, not the HTTP server (that is the first server that handles user's request, therefore being the frontend to everything else).
It depends a bit. If you want a real "micro" framework so it is super fast loading, then that will narrow down your options (I looked at purecss which is really small) but then it is likely to lack the more powerful controls you get with something like bootstrap.

If you want more bells and whistles then bootstrap is fairly easy to understand, allows you to customise your js/css to only include what you are actually using but if you want the full scss experience to easily tweak parts of your design, it is all extra work to setup using gulp/webpack/visual studio code plugins or whatever.
On the Disassembly Line