slavomirvojacek

I am wondering whether with GenAI, migrations like this one will be less and less painful, and therefore more people will be able to migrate to newer technologies/versions sooner and quicker.

I switched to Warp, much snappier, some AI features, overall very good experience. Also Ghostty is apparently good.

Yes sorry!! :)

Yes I meant satellite. Still strange as it's one of the busiest airports in the world and images appear to be taken during the day so... no way there were only 2 planes at any given point... For example Gatwick (LGW) does show quite a few planes just parked.

Yes sorry I meant satellite!!

Maybe someone from HN could help fix the title + desc if possible :))

I am surprised no-one is mentioning Buf for all the great work they've done with the CLI and Connect for much better devex, tooling, and interoperability.

I was on this flight and I am wondering if there is anything available online to see what actually happened? I don't think it was serious at all but would still love to know - out of curiosity. The airline hasn't shared any details, although I suspect they'd reply with _something_ if I asked nicely over email..?

Hi, we will be using https://aws.amazon.com/waf/features/bot-control/ which should help somewhat, but I think we will have to spend a bit more time trying to establish a more robust solution.

We're considering adding additional password protection as a new feature (see https://github.com/sniptt-official/ots/issues/2) - this password can then be shared via other channels with the recipient.

We kinda did this with the snip cli (which is one of our other repos besides the ots cli). It's basically a wrapper around PGP with some additional features like vaults to facilitate sharing PGP encrypted secrets with a team. And... It takes less than 10 minutes to set up :P

It is not at the moment but we are considering making the server + maybe infra repos public in the future, most likely when we've agreed on and implemented some sort of self-hosted option(s).

We will probably write a blog post or two about how we've designed the API + infra around it as there are some interesting topics to be covered.

One of the goals was to also have fun and experiment with a few approaches we've been wanting to use but could not on our daily jobs.

For reference, everything is on AWS and we are using AWS CDK (TypeScript), having moved away from serverless.com recently.

We are ONLY using managed services/resources which are "fully serverless" (API GW, WAF, Dynamo + Dynamo Streams, Lambda, EventBridge, ...) - to save cost, to minimise waste, to reduce ops, etc.

Hope this helps, happy to provide more details.

Hi, just for completeness - the decryption key is added to the secret URL as a fragment in the penultimate step.

Hi, I am one of the co-creators of Sniptt.

We faced this ourselves countless times, and it is exactly why we created both OTS and Snip (https://github.com/sniptt-official/snip - like OTS but with the ability to persist secrets and also create shared vaults etc.).

Pleased to say that self-hosted options for both OTS and Snip are currently top of our roadmap.

Keep an eye on the repos for updates! :)

Hi all, since we've had a bit of traction today I thought I'd ask whether there are any additional features you'd like to see added?

For example, some sort of "self-serve" UI where you could get an API key which would allow users/teams have dedicated rate-limits and not use the default/public limits? Or a self-hosted option where the API could be deployed to the company's cloud of choice?

Or.. leave as is?

Please let us know! :)

Great question - we will likely be looking at G Fonts alternatives as we are planning to revamp the entire website over the coming weeks/months.

As for "grace period", are you asking about URL/link previews and whether those have any effect on reading the secret? If so, the answer is no - the secret will only be read once the client-side JavaScript code is loaded and executed, only certain layout components are rendered server-side.

But I may have misunderstood your question, in which case please do not hesitate to ask again :)

Hi, yes we've got basic rate limits in place, as well as other protective measures as this is pretty much an open endpoint. Please let me know if you'd like to learn more about how we're protecting the API as this is indeed quite an interesting topic in itself. Thanks!

Hi, I am one of the core members at Sniptt - we recently made the decryption key part of the fragment precisely for the above reason. I believe the GIF in the README is outdated :) - the newer versions of the CLI ought to place the decryption key in the fragment, but please let me know if that's not the case! Thanks.

Thanks for asking. Loading the secret happens after the page is loaded, via client-side JavaScript, so social preview should not have any effect. Also, the URL does not actually generate any social preview at the moment, which is kinda by accident.