ramblurr

Stagnant? Both are alive and well. It's never been better to be a clojure+datomic dev.

TLS certificates for internal services* done right

* "internal services" = on a single server that is publicly routable

their cost of operation is still something most people can afford: approximately $30/mo now.

Your definition of "most people" must be very different than the literal meaning.

Don't forget these price increases are only for new purchases. Old rentals keep their price.

This is the second company (that I know of) that got acquired shortly after an AI pivot and re-brand. See: OpenAI to acquire Ona https://news.ycombinator.com/item?id=48491821

> The bottleneck is compute and data, not the model.

I disagree. It is not the model alone. It needs a system which capitalizes on it. And this is very complex. Hardware, software, architecture - it takes a lot to get it right.

What do you disagree with exactly?

> The Kobos don't limit what you can do with them either, you can sideload alternative e-reader software like KOReader that improves on the built-in reader functionality.

This is patently false, the latest Kobo Libra Color is using secure boot which completely locks out custom development

Your "patently false" is not true. There are nuances here that you are glossing over or ignoring.

Yes, the Kobo Libra Color uses secure boot.

But, you can still get root and install KOReader on it.

What is "custom development" if you mean "boot my own operating system" because, then yes. But the 90+% of the Kobo hacking community has never meant that.

For most folks in the community "custom development" means being able to install/side-load applications like Plato and KOReader alongside the existing Kobo/Nickel software.

Yea, I agree it sucks that the new Kobo uses secureboot, but it was never an open development platform. I feel for the quill-os folks, that sucks. I'm glad they found a home with the PN as they won't get a rugpull.

But the Kobo is still a system where you can trivially get root on it without having to jailbreak or otherwise exploit a vulnerability.

And +1 for the xteink x4 (though if you're rabidly against manufactures locking down their devices, you should look at the recent xteink developments where they are only releasing unlocked devices to the western market.)

Yes, it is widely known in the epub space that targeting 3.1 or 2 is the more sane option.

With EPUB compatibility issues CSS should always be suspect number 1. Using "modern" CSS features and complaining about missing flex boxz grid, etc is a web developer's mindset.

Just because EPUB shares some of the stack with the web doesn't mean they perfectly overlap (or even should).

Hardly any e-ink embedded e-reader devices use a browser for rendering, they all use purpose built HTML/CSS parsing and rendering toolchains, are baked into firmware and updated once in a blue moon. (If you're interested look at koreader's crengine or Crosspoint reader which runs on an ESP32!)

The blog post reeks of overly confident AI prose. But don't be fooled.

But a message about your Door dasher also likely wouldn't be justified.

That is false for AWS. There are no spending limits that stop usage and cost after some threshold.

Ona used to be GitPod. They renamed about 9 months ago. Looks like the AI pivot paid off! Congrats.

Have you tried jeep?

https://github.com/pyrmont/jeep/

It let's you vendor deps and easily install modern Janet bundles without jpm.

Always nice to see janet getting some attention.

shout out to one modern feature: sandbox

"Disable feature sets to prevent the interpreter from using certain system resources. Once a feature is disabled, there is no way to re-enable it."

https://janet-lang.org/api/misc.html#sandbox

Gosh. I am very interested in the story here. But I find that I can't engage with the text, because all my attention is going to is noticing the AI-isms. The way in which a message is delivered matters.

What document?

Do you have any sources to back these claims up?

This link is clearly an AI laundered version of the long running joke from Xe Iaso. Shame.

https://xeiaso.net/shitposts/no-way-to-prevent-this/CVE-2024...

https://news.ycombinator.com/item?id=40438408

Is y'alls collective memory so short? Copilot just a few years ago was auto complete on steroids that was entirely first party and trained by GH on users' code.

Postgres, MySQL, all of them, they write to files (binary, not text) on your disk. What happens if your postgres VM dies?

(Hint: whatever your answer is it'll apply to SQLite too)

Emacs totally supports this!

Mixing monosoace and proportional fonts can be a little strange, but there are some 3rd party packages or guides (prot has one iirc) to workaround it.

Interesting! I was looking for discussion of LCM and found your comment. Something I am seeing in my impl is that the agent isn't using the retrieval tools enough to make it useful. Have you experienced this? Any tips?

...and all the HN comment replies too! Egh.

It seems like there's a missed use case: web archiving. I don't see any mention of WARC as an output format. This could be useful to journalists and academically if they had it.

Cut to the chase: This is a marketing post (ad?) for Mesa. https://www.mesa.dev/

A code-first proprietary git-like clone.

They seem to make the mistake many do which is to conflate git and GitHub (though TFA doesn't), because why would you adopt a proprietary hosted VCS (and a startup to boot which could disappear anyway)?

At least with GitHub you can pack up your repos and move elsewhere.

GitHub is certainly in trouble for many reasons. Git...maybe? But is the answer really a proprietary vc-funded ($5M seed) startup?

This is from 2021. Still very laudable. A follow up on how that change in policy is going would be a very interesting read!

I disagree. Nearly every tui/app I install these days still barebacks my $HOME. When you report it the macos bros glaze over with the "complexity" of having to figure out the right dir.

If they can't get that right after 23 years, there's no hope for .well-known/ (especially when they're vibing that tedious bit of code).

Who is the target audience of this? Solo devs? VC backed startups looking to move fast? Corporate teams?

Deploy backends without the hassle

followed by:

It is built primarily on AWS Lambda...

In my experience Lambda is absolutely a hassle.

If we are locking ourselves in to AWS products How does this improve over first-party AWS offerings like Amplify?

Also the readme... I have to try hard not to dismiss a project like this out if hand when I see the LLM generated README.md. They all look the same, have no personality, and frankly are easy to just scroll past.

If you don't take the time to curate and polish your project's readme (the absolute very first thing people read about your project), I can't help but wonder if you bothered to review and polish the code itself.

Nary a mention of parking garages / underground parking?

Austrian cities have way more parking than one would expect, but it's nearly all underground and costs €

The benefits are huge, you have have dense commerical areas where you drive in, park underground, pay for some hours, then walk between the shops to do all your business.

It also affects the digital markup of music. Music can't be expressed with a tree structure as there is lots of overlap.

A simple example is a slur. It crosses bar lines. <bar1> ... <slur> ... </bar1> ... </slur> <bar2> uhoh!

In fact there are many mutually incompatible hierarchies in music engraving.

It's funny though MusicXML is a popular interchange format, but internally looks nothing like what one would naively expect.

Copying my comment from last time

https://news.ycombinator.com/item?id=46616033

Interesting project.. and props for spending the time to figure out all those settings and how to flip them off (for all 4 major browsers too!)

I like the goal of stripping browsers back to basics, but I'm not sure why I'd run a third-party script to flip low-level browser and system settings I can change myself.

From a security point of view, that feels, not great?

This might work better as a simple guide with screenshots, so people can see and control exactly what’s being touched.

Is this much different than https://github.com/kagisearch/smallweb ?