It would've been nice if each of those claims in the article also linked to either the relevant announcement or to the documentation. If I'm interested in any of these headline items, I'd like to learn more.

I don't believe AWS offers permalinks, so it would only help until they rolled over the next documentation release :-(

They actually used to have the upstream docs in GitHub, and that was super nice for giving permalinks but also building the docs locally in a non-pdf-single-file setup. Pour one out, I guess

> RFC 9112 is a fantastic document that details the exact format of HTTP 1.1 requests, how servers should respond to those requests ...

> This server follows almost none of that.

This made me chuckle :-)

The comedy continues in the next paragraph:

> Readers MUST NOT hold this against the project, and SHOULD use this as motivation to keep some of their own side projects fun and short.

That's comedy gold, right there. (Tip: RFC-2119)

Gave it a quick try. Annotations didn't work at all in Fierfox, but all annotation types (underline, highlight, etc.) worked as expected in Chrome.

I haven’t had the chance to test annotations in Firefox yet, so thanks for pointing that out. I’ll check what’s going on there, good to know they’re working fine in Chrome.

Sounds like a mobile-vs-desktop issue, since the error mentions TouchEvent. The Firefox error fires even when just hovering the cursor over the PDF in View mode, and text is also not selectable.

While I'm here, a suggestion to add Undo/Redo; yes HN, I know I could make a PR..

Thanks for pointing that out! I’ve fixed the Firefox issue. And we actually already have Undo/Redo on the annotation toolbar.

If you haven't checked yet, you'll notice:

    Uncaught ReferenceError: TouchEvent is not defined

https://developer.mozilla.org/en-US/docs/Web/API/TouchEvent#...

Yep, that’s exactly the issue! I’ve fixed it so it no longer throws the TouchEvent error in Firefox. Thanks for flagging it.

Redaction doesn't seem to work in Firefox either. Otherwise looks great!

Thanks! The redaction issue in Firefox should now be fixed.

Would love some more info about how redaction works. We currently use Acrobat Pro for redaction mostly because of 'trust' issues, but I'd love to replace it with a web tool. I just need to convince our CFO that it's safe.

Shameless plug and completely tangential: Since we're talking about protocols we need, I wrote a specification called ToolsConfig that aims to reduce the clutter in our software projects (think of all the Makefile, package.json, .npmrc, .vscode/, .gitignore, etc. files and directories that clutter our software projects' directories and sometimes even sub-directories).

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

And it does it in an unusual way. After browsing around on the website and then noticing that the back button history is just the same site name repeated many times, I worried about my history needlessly polluted by this website. But when I opened my browser history, it was just a handful of URLs in there, each representing the screenshot I had actually clicked on.

So, yes, it does break the back button, but it doesn't pollute the actual history.

This is so odd. How is the entire history stack populated with 1 entry?

Since the link shared here is for Triple N-Back method/app, for those looking for a standard Dual N-Back, there are many web apps, one such app I found in search results is https://dual-n-back.io/

Thank you for creating and sharing this utility.

I ran it over my Postgres development directories that have almost identical files. It saved me about 1.7GB.

The project doesn't have any license associated with it. If you don't mind, can you please license this project with a license of your choice.

As a gesture of thanks, I have attempted to improve the installation step slightly and have created this pull request: https://github.com/ttkb-oss/dedup/pull/6

Thanks for the PR. Individual files were licensed, but I’ve also added a LICENSE file as well.

So albertzeyer's script can be adapted to use `cp -c` command, to achieve the same effect as Hyperspace.

If you'd like. In the blog post he says he wrote the prototype in an afternoon. Hyperspace does try hard to preserve unique metadata as well as other protections.

Regular price for the non-TMobile customers is $20/mo.

From the linked page:

How much will it cost?

The beta is free for all. When T-Mobile Starlink launches in July, it will be included FREE on our best plan – Go5G Next – and available on other plans for $15/month.

Until March 1st, T-Mobile beta testers not on Go5G Next can secure an Early Adopter Discount of $5 off per month, reducing the monthly cost to just $10/month.

Verizon, AT&T and other customers can get T-Mobile Starlink without switching to T-Mobile for $20/month after the beta ends in July.