skysight-inc/HackerNews huggingface dataset:
The problem with being a docker registry is that you're still having to double-dip: distribute to the registry, then docker pull.

But you shouldn't need to: you should be able to do the same thing with a docker graph driver, so there is no registry - even daemon should perceive the local registry as "already available", even though in reality it's going to just download the parts it needs as it overlay mounts the image layers.

Which would actually potentially save a ton of bandwidth, since the stuff in an image is usually quite different to the stuff any given application needs (i.e. I usually base off Ubuntu, but if I'm only throwing a Go binary in there plus wanting debugging tools maybe available, then in most executions the actual image pulled to the local disk would be very small).
Are there any significant differences in the geography of Brazil that could also contribute to some of the difference in infection rates?
Police can be extremely vindictive. For instance, they tried to put this guy away in prison for potentially decades because he recorded phone calls of statements they made in an official capacity.

I've seen cops make statements that they must have known were not truthful to people's employers, seemingly for no purpose other than to damage the person's reputation after a heated (but legally protected) conversation. I've worked on bills where multiple members of law enforcement turned up to testify to say things that I'm pretty sure they knew were wrong, just to get their way in policy.

The sad reality is that there are many cops out there who lie to get their way and hurt people they don't like, and so I really don't find it hard to believe that they would accuse this guy of being a sovcit to damage his credibility.

edit: also in this case, remember that they've also accused him of resisting arrest when they went to get him for recording phone calls. So they've also made many claims that WERE about law violations.
Descent 3 Source Code
Someone recently asked if the source code from Descent 3 will be released. I reached out to my old boss (Matt Toschlog) at Outrage Entertainment and he gave me the go ahead. I'm going to work on getting this running again and I'm looking for some co-maintainers.
you’re not thinking creatively enough. a mm-sized hole may not incapacitate someone but a mm-thick slice across their belly would disembowel them. just wave it around!
It really is hard to leave Gmail when all of your data has been conveniently stored therein. This is one of Google's retention strategies and it is indeed brilliant.

That said, there's a vast number of self-hosted alternatives like Stalwart Mail (email) [1], Immich (images) [2], NextCloud (Google Docs) [3], etc.

[1] https://stalwa.rt

[2] https://immich.app

[3] https://nextcloud.com/
I think Tesla’s problems really boil down to two things:

Anyone who really wants a Tesla has probably bought one already.

…And…

Almost everyone without an EV, but wants to buy one, probably will not buy a Tesla.
It is a good post but I'm suggesting it is missing a Step 0: find a distributed computing problem and spend some time playing with it. Like writing a few toy services and using a text file to coordinate instead of a database even, if you don't have access to an industrial level problem.

A lot of this stuff makes a lot more sense to someone who has a bit of "why we care" context - I'd suggest that for most people transactions look much more exciting after realising how much pain is involved in systems that don't have them. Conversely things like CAP theorem are a lot easier to contextualise as "ah ok, so there are failure cases I can't recover from theoretically; I have to make sure they are rare in practice" - it helps to know how big the magnitude is of these sort of theoretical limits.
Vector Graphics Display- you draw with lines instead of pixels.
Another fun one is the Aho-Corasick algorithm [0] which is great (i.e. more efficient) when you have multiple different target strings you want to find and you don't want to do multiple scans of the document.

Like KMP, it involves a preliminary step of analyzing the search term(s), and from them it builds a directed graph representing rules for what to do while consuming the stream of document-characters.

To find all occurrences, it's something like O(document_length + all_target_words_combined_length + number_of_hits) .

[0] https://en.wikipedia.org/wiki/Aho-Corasick_algorithm
It isn't fair because entropy is uncaring. You can't control all the variables and so even if you had perfectly balanced society in spreadsheets, you couldn't implement it. This is the fallacy of city planners too, you can't control the human factor, the weather, the global community etc.

Even if we just talk money in one community, you could give everyone the exact same amount of money and through no fault of their own, some people would lose it and some would benefit wildly, because of the human factor. Person A starts a coffee shop that goes bust, person B starts a coffee shop that does well, just due to timing or luck or even the weather the month they opened.
It's the same in a sense that both are cloud-based, so the same set of problems applies.
That's the same as one-party consent (that is, one of the parties having the conversation, not random passersby), which in the US applies federally as well as in about 3/4 of the states.

But most states - whether one-party or two-party - do not require consent to record a broad swathe of exceptions (particularly extortion, but not just that). Exact laws vary quite a bit - honestly one of the worst things about America is how different laws (of all sorts) can be in different jurisdictions.
For sure. One way I'll talk about this is, "The biggest fantasy novels I've read are project plans." Everybody coalesces around a vision quite detached from reality and then just kind of lives in it for years. It's a weird sort of collective arrogance/faith.

There are alternatives, though! In Rother's "Toyota Kata", he describes a Toyota practice where they pick some far-off goal (which I think is called a "target condition"). That can be something that nobody knows how to do. Then they take one step in that direction and reassess. Over time the path might be somewhat wandering as they learn what works and what doesn't. Or they might revise the goal based on new knowledge. But they keep going, step by step.

That's a lot like short-cycle iterative software processes. Which I know work, because I've used them for many projects. But even software, which is infinitely soft, often gets the same sort of fantasy-driven planning.

I think you're right that the ultimate problem is how authority behaves, and at least in the US there's a terrible managerial culture that this is embedded in. My solution has been to find small pockets of sanity, but I've not figured out how to scale that up. But you might find some hope in this Mary Poppendieck talk, where she explains that it hasn't always been this way: https://www.infoq.com/presentations/tyranny-of-plan/
Lunar is so good - rock solid. Along with BetterDisplay, these have been a comprehensive solution to my various MacOS external monitor woes over the years.
There are a lot of laws passed to clarify or elaborate on existing laws. Unless there's common law that already specifies this exact scenario, this just specifies a specific case for judges, citizens and first responders.
Bobby Tables but with LLMs – Google NotebookML Data Exfiltration
Yeah, that's exactly it- but the point is I was using an unmodified key.

I've tried this on higher-end tumblers and I could really feel that it wasn't going to work. It's just about the el-cheapo builder-grade locks (which comprise a shocking percentage of home and apartment locks).
The style is an artifact/limitation of using a vector display.

Compare to today’s ubiquity of a raster display. Why did they choose to use a vector display? Maybe to decrease cost and avoid placing framebuffer memory? Maybe rendering maps directly to a vector display could be faster by skipping a rasterization process? Any other reason?
You might perhaps be interested in my ongoing side-project "Factonaut" at https://www.factonaut.com/ It is a (closed-source) Windows application that allows you to compile historical events in a knowledgebase and easily create chronological overviews. Currently it only supports very simple chronological tables, not maps. The project is in an early stage, and I have a huge to-do list, but only little free-time to work on it. But the application is useable. Its main speciality is that it can handle Julian and Gregorian calendar dates in the same chronology and sort them correctly.
> They're still the best, it's a very powerful and impressive product

first, thanks for these kind words - it's encouraging (as a maintainer, not just a team member) when we know we're on the right track

sorry about the frustrations, especially around the ssr/auth-helpers. We definitely could have handled that migration better (and the comms in particular). To address some of your other points:

> 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries

Yesterday we made it even easier to do just that with "supabase bootstrap"[0]. We'll be adding all of our quickstarts[1] which cover most of the key (frontend) frameworks

> 3) obvious migration guides and timelines whenever you deprecate something

Agreed. We actually developed this internally after the auth-helpers/ssr. We'll do better in the future.

[0] bootstrap: https://supabase.com/blog/supabase-bootstrap

[1] quickstarts: https://supabase.com/docs/guides/getting-started
I feel like a tree provides much more protection for transit than a rope bridge. I wonder if they’ll avoid the bridge after a bunch are eaten by birds. They need cover.
Did that interface inspire the PipBoy in the first Fallout game 12 years later?
They know. One of their teams (x ai?) announced something recently including a joke about the pussy-in-bio spam - that's how aware they are. Yet, they won't apply the most basic filter possible.
Look how nicely davetron5000's comment below can be read. Proper capitalization makes text much more readable.
aka "eat the frog" method.
Not only that, but it's also fairly potent, allowing you to pass variables from one request to another, transform response, inject .env vars etc.

If all of your team is using Jetbrains products, you can also add the http files to the version control so everyone could have the requests ready to use.

In other words: it's a beast

https://www.jetbrains.com/help/idea/http-client-in-product-c...

---

BTW, you might also find useful to know that you also have a very powerful SQL environment as well ;)

https://www.jetbrains.com/help/idea/relational-databases.htm...
thanks for building with supabase. good luck with your startup!
These rope bridges would seem to make easy pickings for raptors looking for an easy snack.
X/Twitter Wants New Users to a Pay Fee Before They Can Post
FWIW, I've updated the comparison using the latest versions of EROFS and DwarFS. There definitely have been improvements to EROFS in the meantime. DwarFS is still orders of magnitude faster in creating the file system and can achieve significantly better compression, but throughput is very similar unless you start optimizing the EROFS image for better compression.
I've seen plenty of videos of police where the people filming are actively escalating tensions. It's usually by yelling though, not filming, but the yelling seems to usually be for the video, rather than anything productive.
It’s a vector display.

Perhaps one of the most widespread device that used a vector display was the original Asteroids arcade game.

There’s a functioning machine at the Alamo Drafthouse in San Francisco (at least there was last time I went there), I can’t help but stare at it (and give a mini display history lesson to friends) every time I go. Those lines are just so crisp and bright and beautiful.
When the monitors connected have the same serial number the OS could just use the connection side to distinguish the monitors, i.e. where is the monitor plugged in. I gets bad when that is not possible, for example when using a bluetooth headset, where suddenly you hear someone elses conversation because you have the same MAC adress. This requires a workaround on the users end: manually change the MAC adress.
Yeah, it's always so cool looking. The device is using a CRT vector display, so instead of the CRT drawing each pixel row line by line, each shape on the screen is drawn one by one as small line segments.
Curves are also possible, but you'd have to formulate the vector shape for it, which is harder than for straight lines.

It also looks even cooler in person, as the refresh rate is also really good due to the CRTs, if there's an old arcade close with Asteroids or similar early vector games I'd really recommend going to see it.
Does it really apply if you don't do the bare minimum? I wouldn't complain if they were fighting automated building of sophisticated account networks that guide you towards some hidden ad. But until they do a pattern match on the most popular spam words used every day, Red Queen is not an issue.
It is amazing that they got it to work as well as it did given how it was 15-20 years ahead of its time. Sure the unit ended up costing as much as the car it was mounted in, but given the limitations of the technology of the time that is simply amazing. To get an idea of how ahead of its time this is, it wouldn't be until a year after the release that High Sierra formatting for CD-ROMs would be proposed. A CD Drive would have added even more expense, but it should would have beat out swapping around dozens of cassettes.

I wonder how much memory it had. The contemporary PC-XT using the same chip started out with 128kb but could be expanded to 640kb. One can imagine it had to page data in and out of that slow cassette interface quite regularly as you're driving around.
Time-Frequency Analysis of Time-Varying Signals and Non-Stationary Processes [pdf]
I loved loved loved this game. Never understood why this concept didn’t become a whole genre. No actual up, 360 degree freedom, enemies that were smart and could snipe you. Wasted many hours back then and very eager to try this out.
New York is one-party consent; however, such recordings are not admissible as evidence in court, that requires two-party; one-party recordings can be used to embarrass.
Poems for the lost, because I'm lost too. By exurbia.

Excellent book, some poems go very deep but most of them are just funny (at least for me).
Pretty cool on the surface, but 2 things I can think of right now that mostly kills it for me (and maybe many others). 1) the things one usually use Bittorrent for tend to need the complete files to be all there to be useful, and internet speeds is a limiter in that regard. 2) seeder count tends to break down pretty quickly, as people delete or even just move the files elsewhere for whatever reason, so availability falls.
Florida’s website is a bit confusing to navigate, but I think I found the actual text of the law.

https://myfloridahouse.gov/Sections/Bills/billsdetail.aspx?B...

I think it is under bill text/enrolled.

I don’t find the word re-established in there. So, I think that’s just the wording that the newspaper picked. Regardless of any difference between establish or re-establish, it doesn’t really make sense to put too much weight on subtle implications of the newspaper’s wording.
> we can all agree that someone loudly "recording" shoulder to shoulder with police officer disrupts their ability to resolve situations

Sure. We can also agree that throwing rotting sea slugs at anyone eating a hamburger is disagreeable. But absent evidence of it (a) happening and (b) going un(der)punished, any legislation to ban it is performative.

Performative legislation isn't bad per se. Ideally, it would have no effect. But given almost any increase in legal surface area brings rise to unintended consequences, the result is a net negative.

> are disingenuous protesters who abuse recording excuses to disrupt law enforcement

Again, do you have examples of people recording police disrupting law enforcement where those recording weren't punished (sufficiently)?

> Both of these things are wrong

If one is occuring more frequently, and moreover going more-frequently unpunished, then tipping the scale further in that direction is counterproductive.

If police abuse is running rampant while nobody can find unpunished instances of disruptive recording of the police, then these rules are more likely to further the abuse than facilitate legitimate law enforcement. (To say nothing of the wasted political capital, given the myriad of problems Florida has to deal with.)
etak (navigation): https://en.wikipedia.org/wiki/Etak_(navigation)

a word of Micronesian origin for a distinctive cognitive and mnemonic approach to oceanic navigation and orientation involving a notional reference point or "island", called etak, and triangulation based on it.

... the use of a relative frame, in which the boat is considered to be at rest, while the etak moves.
The solution is obvious: pin Steam to the taskbar, not to the start menu, as well as Chrome.
Put a shortcut on desktop to shutdown the computer, then never use the OS for anything else.

I recently put Kubuntu on my desktop and I've been way happier.

What a depressing ending for that OS
I'm not a lawyer so take this with a grain of salt, especially with the current scotus, but I wouldn't be super surprised if courts found it legal to record government officials in general. Other forms of communication (like email) for government employees are already subject to FOI requests, and the barrier for them to block FOI requests when it's about an interaction you were a part of is much much higher in general than for asking about interactions with other people.
The name is perfect. "Etak" refers to a system of navigation used by Micronesian and Polynesian seafarers to navigate from island to island in the vast Pacific Ocean. Much like this device, it operates by "augmented dead reckoning" (as it says in TFA).

The etak system of navigation involves navigating by stars and ocean swells to get the heading, but a key issue when navigating by dead reckoning over long distances is that if you're a fraction of a degree off you may miss your destination and never know it, so it's also vitally important to know how far you've gone. This is hard when there are no landmarks. The navigators estimated their distance by using intermediary islands off to the side, which they viewed as coming towards them (from their point of view, the navigator stays motionless on the open ocean while the world moves towards them) and past them. These reference islands were called etaks.

However, confusingly, the etaks were generally not visible, being beyond the horizon, and sometimes did not even exist. The navigators would have named etaks that they pictured being just over the horizon, whether they were there or not, and would track their procession past their boat. When the set number of etaks had passed, they would know they were in the vicinity of the destination island. If they were not at the right time of day for birds to be out, they would then hang out in the area waiting to spot the birds leaving or returning at dawn or dusk.

So the system involves dead reckoning plus a system of turning the navigators' own well-developed intuition of how far they had travelled into a formalized system of generally-invisible islands that they used as a mental model to externalize this intuition.

(My knowledge of this is from Cognition in the wild, Hutchins, E., 1995.)

Edit: D'oh, I should have finished TFA. This is described at the end, although more roughly.
The preferred AV1 encoder that ships with ffmpeg, SVT-AV1, is faster than any software H.265 encoder now. You can encode 1080p video in real time at preset 6 (the equivalent of 'medium' -- presets are on a scale from 0 to 13) on a $120 desktop CPU.
No rush to Ukraine tho cuz the US has such a bizarre long term security strategy -> https://michael-hudson.com/2023/11/israel-as-a-landed-aircra...
It's possible, but it's also similar to other vector graphics from the time.
Depends, I might opt for the limb remover if it is simpler and works more reliably. Time is money and I'm confident I could use either properly so I'd likely waste more of my limited lifespan fixing the safe but more complex and more unreliable machine.

If there's no cost to the safety factor then sure, put it in. However there's almost always a cost. We all pay with a portion of our life every time we stand in an airport security line and every time we click accept to one of those EU cookie popups in a futile attempt to keep our data safe. With each click, billions of humans have a precious few moments severed from their short time on earth, moments that could be spent with loved ones.
> the good stuff, the useful stuff was behind the cloud subscription paywall

can you share more? everything is open source, the code available, and all OSI-compliant

> Much of the logic should be server side also for security reasons and that wasn't possible when I tried it.

This is possible in very many ways:

1. Write an RPC function and use PostgREST

2. Use Edge Functions

3. Use whichever frontend framework you are developing with (they all integrate well with supabase)

4. Connect a server directly to the Postgres data ase in a 3-tier architecture

> I think the appeal is to people who like doing frontend but don't like doing backend.

Perhaps! We also have a large number of customers using us as a traditional Postgres host. And we have a lot of "Postgres maxis" who love the RLS + PostgREST combo. You choose your level of comfort with Postgres: https://supabase.com/docs/guides/platform/shared-responsibil...
> but I'd like to see other people's ideas

Naive Bayes. They're at the level where that would improve things. Start with basics before gen AI.
HTTP2 multiplexing is great for issuing multiple requests within the same HTTP connection, so that you don't have to deal with the overhead of establishing separate connections for each resource that's being fetched, but that doesn't solve the problem I'm talking about. Link preloading is great for having the browser fetch resources in the background before you need them, but if you're server side rendering your components you presumably need those components to be styled immediately (otherwise why are you server side rendering them in the first place), so that also doesn't solve the problem I'm talking about.

What I'm saying is that if you inline your styles in a style tag (either in the shadow DOM or in the head of the document) then the browser doesn't have to make any additional requests at all, because the styling information is present in the initial document already.

If you don't inline your styles, then the browser has to make two separate requests if the cache is empty: one to fetch the document and figure out which additional resources need to be loaded, and then an additional request to actually download those resources. There's no HTTP protocol shenanigans or link preloading that can change the fact that packets are being transmitted from the browser to the server and back again twice. It's basically another formulation of the N + 1 query problem. Once the CSS file has been cached you only have N requests instead of N + 1, but then the cache has to be invalidated every time you update your styles so you're back to square one again. The documentation for Lit explicitly recommends avoiding external stylesheets for web components, because it can lead to a flash of unstyled content while the browser makes an additional request to load the external styles: https://lit.dev/docs/components/styles/#external-stylesheet