whiskey-one

This is really cool! Once you’ve gone to the trouble to be in k8s universe, might as well get some higher-layer primitives for the business logic as well.

The only weird part is the need to stand up a cluster to test individual trigger/flows function.

Any tips / online resources how to best utilize for defensive reviews?

Indeed, the user is the hardest part of the program to secure.

Very cool

In theory, yes you could iterate on architecture and potentially even come up with better one with agile approach.

In practice, so many aspects follow from it that it’s not practical to iterate with today’s tools.

Great timing too to ditch MacOS. Just instilled Fedora Asahi Remix 43 on may MacBook Pro M2, and both KDE and Gnome work great. So happy to be liberated form the increasingly sloppy Apple OS.

https://asahilinux.org/fedora/

Subsequently in PoI we see two imperfect super-intelligent AIs let loose in the real world fight each other for domination and their objectives.

For me, it’s a question of when, not if this happens in real life.

It is indeed painful to figure out all the Stripe events one needs to handle. However, for me it’s worth it to do it once, and then be able to handle the interactions between my app and Stripe directly, instead of adding more layers.

A reminder associated with the birthday can and should be changed if I change time zones. But the birthday date didn’t change so it shouldn’t move to a different day.

The concept is interesting but without charging it’s a non-starter for me. Also it’s a bit awkward and I’d prefer to use my phone or watch instead of adding a ring.

Is there a write up on the security of actions or equivalent that explains how they are secure both with direct and transitive dependencies? If this applies to Depot.

I left a large software corp last year to co-found a startup, launching myself in the world of OSS. I couldn't be more grateful to the HN community for introducing me to great concepts and tools!

Having to figure out which of the 100s of Stripe event types we need to handle and which ones overlap was the most stressful part of adopting their system. Simplification here is welcomed.

Can you elaborate on the fault tolerance advantage of micro services?

For context, my current project is a monolith web app with services being part of the monolith and called with try/catch. I can understand perhaps faster, independent, less risky recovery in the micro services case but don’t quite understand the fault tolerance gain.

Looks easy on the surface, but the problem is key rotation.

This is a really cool project! I would love to see a timeline view where the ads from particular decade are shown together, followed by subsequent ones!

A web app which we plan to be always free for personal use. It's called MyMirror 360 [1].

The goal is for you to get complete and honest feedback from the team you work with. The killer feature is we make it quick and easy. And your reflectors can never initiate the instance of giving of feedback, the system invites them; this avoids the "but I am angry now" situation.

You can add the team members you work with in any setting and specify how often you work together. Depending on that, they will get the chance to reflect on you between every four weeks and every eight weeks. A reflection takes literally seconds.

Sign up is invite-only atm but invites are handed out pretty quickly since we want the feedback! Just sign up for the wait list on the site [1]. It will be free because we have a business version [2] that will support it; and the personal app will hopefully generate interest in the company one.

You can send feedback to "admin" at the domain of the company one [2].

[1] Personal: https://www.mymirror360.com/ [2] Company: https://www.mirror360.org/

I understand interconnecting Cloudflare’s network and hosting their servers by ISPs builds a beefier Internet and that’s great, but isn’t it potentially problematic for a small number of vendors to become a significant part of the network? What happens if they go out of business? Are we no worse off than before, or do we worry about equipment that’s in limbo unless purchased by another business? Or is it potentially bad but inevitable since investing in growing the Internet requires deep pockets so it will always be the bigger corporations owning large chunks of the network?

Infra like Internet cables under the ocean are to me more obvious things to be purchased by other businesses. ISP-collocated content servers that came to be due to discovered mutual benefits of content and service provider seem to me more complex in terms of managing them in the face of business changes.

At our company we host our web app stack and services in a cloud provider, but we don’t use managed services other than Kubernetes. Then everything on top is open source services and apps we host. It’s a big overhead to setup and maintain but I feel once the learning cost is absorbed one time we have high degree of flexibility and also resiliency against random resources getting added behind the scenes and costing us money. The critical part is to stay on top of config & updates since a lot of the apps won’t update themselves or even report an update is needed, and ending up with a vulnerable dependency may be orders of magnitude worse than 1-5K incidental expense.

Really great post! It belongs on a reading list somewhere for everyone who is using Postgres independently or as a part of their stack.

It might make sense for a product that is hard to patch due to a more complex manufacture to drain supplies before updating. For a security product that is known to be vulnerable it is not forgivable to keep shipping.