godber

Thank god, in 18 months we can start making our own RAM.

Tokens are also a scarce resource for some of us:

> THE SCARCE RESOURCE: HUMAN TIME AND ATTENTION

This workflow may not be accessible to token poor teams. Though I’m not all the way through the post, so I don’t know if token scarcity is even acknowledged.

Have they axed it yet?

I think a solution to this could be for the government to require the companies to provide the original scans and OCR results to the government for safe keeping until copyright expires.

Clearly that makes assumptions about the function of government and the complacency of copyright holders.

Let me know when they offer to pay me to watch it.

Holy smokes that explains so much. Amazon’s review/feedback mechanism is completely worthless with commingled inventory. No wonder it seemed ineffective.

“the cost of trying ideas had collapsed”

This is a critical observation of the vibocene.

Nice post, one more thing to keep in mind with your StatefulSets is how long the service running in the pod takes to come back up. Many will scan the on disk state for integrity and perform recovery tasks. These can take a while and mean the overall service is in a degraded state.

Manage these things and any stateful distributed service can run easily in Kubernetes.

This makes a completely valid point when you constrain the meaning of Big Data to “the largest dataset one can fit on a single computer”.

Good find, I think those would be books written in English published by German publishers. The blog post discusses how ISBNs are allocated ... specifically the ones you picture are published by Springer, which is a German company that publishes in the English language.

Considering a specific example: "Forecasting Catastrophic Events in Technology, Nature and Medicine". The website's use of "Group 978-3: German language" is a bit of a misnomer, if they had said "Group 978-3: German issued" or "German publisher" it would be clearer to users.

This is really exceptional work, and still works on my ten year old iPad. Great job!

Yes, that sucks.

Using helmfile (yet another layer of abstraction on top of helm) lets you get diffs between current and new releases. And it’s all templated so could be dynamic.

The info on that page seems a bit contradictory, but maybe I need more coffee.

This claims to bypass the telematics functionality:

https://www.autoharnesshouse.com/69018.html

> Note for customers retaining OEM headunit: This adapter can also be used for those wishing to remove/disable the OEM Subaru Telematics functions. This is done to eliminate the tracking cabability that Subaru has built into these vehicles. If this is you, we will need to add an additional part to this adapter to re-enable the bluetooth microphone. Please purchase the option 2 adapter near the bottom of this page for this situation.

There's an even more recent post

https://subseacables.blogspot.com/2024/10/facebooks-semi-sec...

This is exceptionally cool work. I’d love to see it running.

I would definitely approach this problem by having the LLM write code to scrape the page. That would address the cost and accuracy problems. And also give you testable code.

OpenSearch really appears to have a significant amount of development momentum. It is functionally equivalent with Elasticsearch. There would be no incentive for AWS to do this. After ES broke their compatibility with OpenSearch they also broke compatibility with their own older versions. This forced users to choose in order to move forward with anything. I don’t know how it worked out for others but I’ve converted hundreds of ES clusters to OS and switched all development to OpenSearch because they started gaining momentum and didn’t make decisions that were actively hostile to their users.

Edit: As long as OpenSearch doesn’t start breaking the self hosted use case, I don’t see any reason to consider Elasticsearch again. In fact, ES would have to offer up a significant advantage to overcome the bother.

This article makes me think of the skill tree or roadmap posts we’ve seen here on HN or Reddit over the years. For example https://roadmap.sh/frontend …

I feel like we could do a better job of providing ourselves fundamental tools like this in helping ourselves and others learn. Not just in tech, but in life overall. The “dev” tree above is embedded in the life skill tree that should start in elementary school.

Haha, even the life skill tree has “fictional” branches that intercept the game world skill tree … you really do have to learn all of the dependencies necessary to case 5th level fireballs … there are real rules to be learned in the games their usefulness is just siloed into the fictional realm.

Edit: I forgot to point out that roadmap is open source here: https://github.com/kamranahmedse/developer-roadmap

Great find EndXA!! You melted my brain a bit.

We did some experimentation with quickwit about a year ago, writing about 1m docs/second of data into it for several months. It worked well and was pretty straight forward to learn and operate. If we didn’t also manage our own S3/Ceph it might be a big win, once feature complete. It’s definitely worth a look.

I think we've been thinking similarly. Decentralization will have it's costs. I've been thinking Opt-In centralized search for personal repos, maybe as a gitea (or other self hosted options) plug-in. But as you suggest, maybe existing features can be leveraged to prove the social/discoverability.

I’ve kind of anticipated this sentiment and have been thinking about providing Gitea hosting. Though I’ve been a little discouraged by Gitea’s release of their own cloud hosting service.

This blog post and the revenue growth at Gitlab over the last two quarters appear to be evidence of people wanting to moving away from GitHub (though their earnings report attribute the growth to other initiatives, clearly I had no real insight on this). As an extension of my self hosting of Mastodon efforts from last year I rolled up my other minor hosting efforts into https://hawt.cloud as a place to experiment with providing services like this.

This all ties in with the “Open Web” or “Small Web” sentiments I’ve seen expressed recently. The hyperscalers are locking more and more up into their ecosystems but there should still exist small vendors/hosting/service providers. They’ll never scale or be as reliable as the big guys but if they cease to exist a lot will be lost.

Haha, thanks for sharing!

I used to use OpenBSD about a decade ago, I liked it quite a bit. I haven’t paid attention for over a decade though. Does anyone know how the maintainer base has evolved? I guess my main question is will OpenBSD survive Theo’s death?

The site was launched about 5 years before the book was written.

Lol, Noel as an intern.