skysight-inc/HackerNews huggingface dataset:
I wonder if we need a new UX pattern where every single destructive action is delayed by ~30s such that there is ample time to press “cmd+z” or a toast undo button.

It’s not very difficult to implement the client side code for this, and I think users would appreciate it.

However delaying a “delete” would cause some complications with the local data, where you might want to optimistically render the UI such that the delete went through. That shouldn’t be difficult in any modern state management library though.
I don’t know of a way that a manufacturer and a consumer could allow a buyer to voluntarily “lose warranty” with a software toggle installed and offered by the manufacturer, without running into complications with the laws around automobile lemon laws. One constructed example to demonstrate the problem might be, “They claim to have provided a switch that voided the warranty and my three year old flipped it in the car’s mobile app when I wasn’t paying attention, I want a full refund for my car now”.
Background: https://en.wikipedia.org/wiki/Neodymium_magnet_toys#United_S...

I have a set of Zen Magnets that I bought a decade ago. They're fun to play with, and I guess now illegal to manufacture.
They currently have filed chapter 11.
Cool project, I had fun. Could be like Wordle but more interesting.
wasi-js is another one I’m actively supporting that is in pure JavaScript (hence small and easily hackable): https://www.npmjs.com/package/wasi-js

This is based on what wasmer used to provide for wasi in the browser before they did their major rewrite in rust mentioned above. I personally find the JavaScript version more useful for my projects so I revived their old project and am maintaining it.
"permits for fossil fuel plants used for cryptocurrency mining that utilizes “proof-of-work authentication.”".

I don't get it. Are cryptominers running their own oil generators in NY?

Edit:
https://apnews.com/article/bitcoin-mining-new-york-power-pla...

What the ...
Just want to point out the obvious: if you are staying at 1300 for over 1y, you are not improving and likely not understanding why you are losing. I would recommend you study rather than banging your head against the wall by playing more games.

Opening theory and tactics are a good place to start.

An easy step is make sure you know a few common openings and have at least one response prepared to each. But also a good understanding of principles. Opening principles are more important, you can wing it if you don't know the theory. There are thousands of videos on YouTube about these topics.

And obviously just don't hang pieces and take your opponent's hung pieces. At 1300 on lichess, your opponent will make a bunch of tactical mistakes which you can just take if you see them, after you can just win if you play solidly for the rest of the game. The way to study here is with puzzles.

Sorry to patronize. I have played thousands of 1300's on lichess and improved after I sat down and studied. But I can tell you, if you're actually 1300 you are not strong enough in some of these areas.

P.S. I don't believe the comment above yours. The dude went from 2200 to 1300??
How interesting! Have you done any experiments to try to identify the “line” between the two skills? For example, can you write individual letters in isolation? Like a single letter “T” by itself?
And can you still draw shapes? (Like a circle? Which is basically an “O”.) If so can you draw a series of shapes? A circle, a square, and a triangle? Have you tried writing words with your non-dominant hand? It won’t look very nice but I wonder if the jumble impacts both sides or just the side that “knows” how to write?
Yes. To provide the context necessary to understand the "this is why we can't have nice things" quote, you have to say what "this" is. That's how pronouns work.
>At a minimum, it’s useful, as you can get a particular dog to do something when it’s addressed individually.

That can work, particularly with smarter breeds that can understand context, but it actually isn't anywhere close to best practice.

MUCH better is to train separate commands for the same action for each dog.
> when we all know that's tokens like FTT.

Yeah, this is just absurd. It's an illiquid self made token which only a small percentage was circulating. Even a fairly unsophisticated trader would know that you can't just mark that to market at spot and get a reasonable price!

I agree that has to be a feint to avoid criminal charges. I hope the prosecutors see it for what it is, it's essentially one notch improvement to writing: "Our bank account is down to $5000. However, I checked the break room and our copy Monopoly still has $20,000 so we're solvent against our liabilities of $19,000 and can continue to operate as usual."

The letter does include a hint to where more of the real assets could have gone: "included buying out binance". -- presumably clawing back that transaction is at the top of the bankrupt entities priorities. The realestate purchases for SBF and his family are more obvious but taking those back is less urgent.
I'm a fan of first person sentences.

Do you want to quit?

> No. I'm still working!

> Yes. I'm done for now.

Especially in a mobile interface. The user is physically touching "I'm done for now"; it's a visceral interface; real hard to mess up unless some motility accident happens (like the phone slips)
Firefox has added a small delay to prevent this exploit.

Chrome has responded that it has yet to have been detected and weaponized yet.

Imagine a small game where you must press the [Enter] key rapidly.

Would you, with a few similar boxes in game to detract, notice the Open_Folder_DialogBox for a few frames? Probably not in time to not hit the [Enter] key, giving the webpage's javascript full permissions to everything in the default, selected Folder...which is the C: drive.
This is why open book examinations are a thing. Memorization is rather redundant IMO. Being able to use the concepts to solve the problems is an important skill.
eh if you were a senior at FB people will give you the benefit of the doubt in a lot of cases. If you're interested you should apply
This is an interesting thread :)

I see lots of conjecture on the nature of voice assistants, or why they haven’t taken off.

As someone who was at Amazon, and close to this area, let me offer a simpler explanation.

Alexa has stagnated because its leadership has little to no direction. The incentive structure driving the product teams and tech falls under two categories: 1. rest and vest 2. or write documents to build your promotion portfolio and get promoted. Then leave the org to find a job in AWS.

In fact, Alexa could be used as a text book study in empire building.

* Myriad teams that maintain or increase head count each year, with absolutely no meaningful deliverables.

* Services that could be maintained by a 2-3 person on call that have an entire team of 6-8 engineers.

* Tech directors, Sr. SDMs, and SDMs in a race to build their empire to get promoted to the next level. SDMs solemnly hiring head count for the sake of having more reports. Other SDMs hiring SDMs below them, even though there’s no need for additional management (team is idle), so they can show a larger footprint and get promoted to the next level.

Voice assistant tech may as well be hitting a brick wall for technical or human computer interaction gaps that need to be thought much more in depth. But saying this was just an insanely hard technical problem is misleading and missing the bigger picture.

If you build an organization as a pet project and then throw money at it to do whatever the hell it likes, with practically no accountability, of course you won’t get meaningful results.

In recent years, Alexa became a place to chill and wait for your RSUs to vest. I personally know great engineers in Alexa, who are now stressed out of their mind about their work and visa situation because of the layoffs. But look - you decided to join a team where you basically just hang out at work, have a series of useless meetings, or half the time, your manager is complaining for some reason that his team doesn’t all show up to daily stand ups. A ton of extremely talented folks became extremely lazy, and so here we are.

To root cause: misaligned incentives, lack of accountability and a poor work ethic, shockingly poor given at least some other parts of the company are still on the other, opposite extreme.
Some TVs are known to look for open WiFi networks in order to connect to the internet and send data back home.
Some heroes don't wear capes.
> how come this isn't being used by activitypub to offload server work?

Because ActivityPub is the same thing as HTTP, a protocol for exchanging information. Basing a protocol around the idea that you send data to a closed-source platform goes against the whole idea of creating a open protocol in the first place.

Not to mention it goes against the idea and culture behind Mastodon as well, as bunny.net doesn't seem to be FOSS at all.
This would be more convincing if it wasn’t so bad faith
Can someone ELI5 what problem this solves? I think of WebAssembly as being a tool for getting code written in <random language> to run in a web client. Can't I already run code written in <random language> on a server that I control? Heck, PG went on at some length in one of his early essays about how that was one of the great things about the Web: you could use any language you wanted on the server. Even Common Lisp...
Does the exe generation need any runtime like vb needed vbrun.dll back in the day?
> get the game out of the door fast

But at what cost? Using Unity/Unreal incur the cost of lower flexibility in your design, more time spent learning "the unreal way"/"the unity way", and a finished product that looks and feels like every other unity/unreal game.

Of course the argument for unity/unreal is also true: Building your own game engine takes lots and lots of time.

So it's a tradeoff, like all things.
Yeah, even tweaking kernel IO scheduling would probably be sufficient. It'll depend on spinning rust vs SSDs though.
As someone who does more back-end work in my job, I love learning about this kind of front-end stuff that I don't get to use as often.

Flexbox has been great to work with because it's much easier to control your responsive design. You can choose what lengths stay fixed, which expand and shrink, etc.

When I learned how to use flexbox I went searching for how to add tools to my responsive-design toolbox. I learned about how to use media queries so that different CSS rules are applied based on the width of the page.

Flexbox, grid, and media queries are some of the heavy hitters in responsive design these days, but wanted to know more about effective use of things like CSS functions like calc, min, max, clamp, minmax (grid only) and when to use them. I can find reference material, but I haven't found any good resources that explain when you'd use them instead of something else.

Does anyone have a good resource for responsive design that covers use of CSS functions too? It's no good to have a tool in your toolbox if you don't know you should be using it.
"Abstract: The Names of All Manner of Hounds is a unique list of 1065 names for hunting dogs (running hounds, terriers and greyhounds) found in a fifteenth-century manuscript that has recently been sold into a closed private collection. The present article offers a critical edition of this unusual text, which has never been published before, preceded by an introduction that contextualizes its contents in terms of the hunting culture and the milieu to which they belong. ..."

https://sci-hub.ru/10.1484/j.viator.1.103488
This was a great read, I have always had a love of PC fans, and the technology behind them. It'd quite a complicated engineering challenge to produce a high static pressure, high rate of airflow, and minimize noise while maintaining high reliability. I'm one of those folks that has no problem dropping significant money on fans every time I do a PC build, and so far I have very very rarely ever had a fan fail on me, even after decades of running at high duty cycles. The thing I always marvel at is how high the draw is for some of these fans. At one point I even retrofitted a system with an external radiator for water cooling that used 120V 120mm Panaflos and was separately powered from the computer.

I wish folks took cooling more seriously. There are so many devices that benefit from active cooling but rarely get it, or even being strategic around placement, positioning, and mounting to make convective cooling more effective. Thermal limiting is such a common occurrence on modern electronics if you don't give due consideration to cooling, as we've moved towards more passively cooled devices, including PCs (laptop especially).
If I read the numbers correctly, they have monthly costs of about $0.07 per user.

Interesting, when you compare that to Twitter:

https://masto.ai/@mg/109394485136585413
I'm afraid I'm a bit too young for OS/2 Warp, but I can write about Haiku OS in the future if that'd help?
You don't necessarily get fault-tolerance for free; there will always be some shared resources (or you don't have a single program in multiple processes, you just have unrelated programs), so you still need to design for the requirement "when a process exits, external state is valid." In a sufficiently complicated system, this doesn't happen by accident.

I do find it a better lever for "make the easy things simple and the hard things possible" though.
I think the sibling post by samwillis explains my view the clearest.

Basically, the business case for breaking the signup flow to require users to check their email is low. It interrupts flow and reduces conversion rates.

The suggestion then is yes, you are allowed to use emails you don't own to sign up for an account. The reason this is allowable is that who would want to do it? The account would be broken and the real owner of that account can pop your password.
We are definitely hiring a designer in Europe. :)

I asked DJ (not on HN, but hangs out in our community Slack [3] where you can ask further if curious), who knows the disk side of things best, and he responds:

The OS is free to reorder writes (this is true for both io_uring and conventional IO).

In practice it does this for spinning disks, but not SSDs.

The OS is aware of the "geometry" of a spinning disk, i.e. what sectors are physically close to each other.

But for NVME SSDs it is typically handled in the firmware. SSDs internally remap "logical" addresses (i.e. the address from the OS point of view) to "physical" addresses (actual locations on the SSD).

e.g. if the application (or OS) writes to block address "1" then "2", the SSD does not necessarily store these in adjacent physical locations. (OSTEP explains this well [0].)

"Performance Analysis of NVMe SSDs and their Implication on Real World Databases" explains in more detail:

> In the conventional SATA I/O path, an I/O request arriving at the block layer will first be inserted into a request queue (Elevator). The Elevator would then reorder and combine multiple requests into sequential requests. While reordering was needed in HDDs because of their slow random access characteristics, it became redundant in SSDs where random access latencies are almost the same as sequential. Indeed, the most commonly used Elevator scheduler for SSDs is the noop scheduler (Rice 2013), which implements a simple First-In-First-Out (FIFO) policy without any reordering.

Applications can help performance by grouping writes according to time-of-death (per "The Unwritten Contract of Solid State Drives" [2]), but the SSD is free to do whatever. We are shortly going to be reworking the LSM's compaction scheduling to take advantage of this: https://github.com/tigerbeetledb/tigerbeetle/issues/269.

[0] https://pages.cs.wisc.edu/~remzi/OSTEP/file-ssd.pdf

[1] https://www.cs.binghamton.edu/~tameesh/pubs/systor2015.pdf

[2] https://pages.cs.wisc.edu/~jhe/eurosys17-he.pdf

[3] https://join.slack.com/t/tigerbeetle/shared_invite/zt-1gf3qn...
Yea, the front page seems to be optimized for recency -- Istio is on top because its the newest module, as the heading "Latest release" states.

If you scroll down to "View all series" they have one listed as "KUBERNETES FOR COMPLETE BEGINNERS"[1]. The content is 1-2 years old which can be quite a ways back in our field.

[1]: https://learnkubernetes.withgoogle.com/kubernetes-essentials....
> Are you sure you want to delete this draft? [(Yes) Delete Draft] [Cancel (Deletion)]

> Are you sure you would like to Exit? [(Yes) Exit ($appname)] [No, Continue]

I see you are starting to discover the GNOME Human Interface Guidelines. Yes/No and OK/Cancel are discouraged, opting for meaningful button names instead.
> All costs are detailed here: https://hub.fosstodon.org/about/#current-funding

It doesn't actually list where and how the service itself is hosted, it just says "Fosstodon hosting" and the amount. I'm looking to understand what hardware is being used and where it's hosted.
Tell HN: Making Twitter likes backup tool as side quest of browser/second brain
I want to build a browser that captures everything I saw on the internet, allows me to search it, run graph algorithms (like PageRank). Improves navigation (by showing trails as tree instead of tabs). Heavily offline focused (Backend only for updates, maybe for analytics).

Difference with rewind.ai: linkkraft does not have funding, i'm solo, no apps & image/video/audio recognition. Focus on web, trails, research and using web copies, selections/highlights as part of your notes & whiteboards. Preserving all possible graphs.

My inspirations: https://pages.gseis.ucla.edu/faculty/bates/berrypicking.html, https://beepb00p.xyz/promnesia.html, Jeff Raskin (Global Search, Zoom UI) https://linkkraft.com/notes/backstory

I've built a prototype with trails tree & HTML snapshoting. For each my step even inside SPA linkkraft creates HTML snapshot.
https://arestov.github.io/linkkraft-notes/comparing/linkkraf...
https://arestov.github.io/linkkraft-notes/trails-tree-plus-o...

Across similar software ("too many tabs" solvers, snapshoters) combination of trails tree & snapshots that reinforces is unique in linkkraft.

To make snapshot it takes current state of DOM, current state of styles (to capture CSSinJS stuff), take resources like font/images from network storage (Chrome Dev Tools protocol) and saves it as HTML on disk.

I've been developing created frontend in-memory graph DB / state manager for 1) replication 2) incremental sync 3) fast rendering (without VDOM/react). Used in https://seesu.me & https://meetsidekick.com.

So, I have in memory db in main process of electron that send chunks to render process with replica. And to LevelDB to persist graph.

From user perspective, I also want to have a copy of all my bookmarks (Cause things disappear from internet and things are slow in internet). As special wish: twitter likes/bookmarks (because I use intensively for inspiration from other makers and Twitter is especially slow & unavailable for scoped search).

There are changes in twitter HQ, that looks reasonable to speedup ability to make backup for twitter likes/bookmarks.

https://youtu.be/yTpysdSM9WQ

I have 3 tech tasks for that:
1. Scan/scroll likes pages (actually it would be better to inject code in twitter page to make direct requests to API)
2. Fetch page HTML snapshot. I'm thinking to not fetch page from start, but instead reuse SPA. Something like push to history API, so without full reload I'll get renderer page and comments triggered to load.
3. Speedup resources fetching a) run everything as soon as possible (not when everything is ready) b) use key/value ( url+etag) cache for hash. Which is used to dedup images, fonts, styles.

For me it's not to escape twitter, but to speed up interaction and discover even more things on twitter
Jonathan Blow is a skilled craftsman with stuff like this and he knows he's going to get a bunch of Opinions About His Language from people who think they have a complete superset of his knowlege, and he is making his language without involving those people in any way.
I agree, and with multiple processes that's just a single mmap() call away!
The `create-exe` subcommand is interesting!

For any language with decent cross compiling capability, is there a use case for `create-exe`? Eg i use Rust these days.. and i wonder if there's any use case for me to cross compile via wasmer instead of natively. My project(s) do work on WASM as a target (for browser reasons), maybe it would be easier to setup cross compiling via wasmer and not manage the release pipelines i have?

Though for some of my performance critical applications i may not want to bother with it. Simply because i'd suspect wasmer might not have the same platform specific optimizations that natively compiling would give me.
If you really care about this person as a human, just tell her to do what she can when she has power, and when she’s able to evacuate help her out however you can. I think it’s funny that you seem to be more focused on the work she can do but I’m assuming you do care about her well being first and foremost.
You can DIY powdered alcohol. It's alcohol that's been mixed with a cyclodextrin
Eh, that's definitely a matter of taste. You definitely shouldn't have to pass an additional parameter everywhere you want context there's no absolutes here, just preferences.
Good, how on earth did their legal team think this was OK?
They may not be very useful at the moment, but if progress in large language models continues at the current pace then I can imagine that conversational AI might be useful in several years. Investments by companies to establish and maintain voice assistant market share might thus eventually pay off.
Looking at mastodon.art, the admins seem to have blocked/muted hundreds of instances, including mastodon.social, mastodon.online, qoto.org, all of which are moderate instances with a clear policy against racism, harassment, etc., I don't see how this is good for artists, who probably need engagement. I think mastodon.art admins are trying to push their agenda by pressuring other instances to adopt stricter restrictions and limit users' freedom, instead of simply protecting their users (which is not achieved by restricting users from interacting with moderated instances).