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.

Im no world leading expert but as far as I understand, coupled with events, if an unimportant service goes offline for 5 min (due to some crash, ie "fault"), its possible to have a graceful degradation, meaning the rest of the system still works, maybe with reduced ability. With events, other systems simply stop receiving events from the dead service. I agree you can achieve a lot of this also in a monolith with try catch and error handling, but I guess there is an inherent decoupling in having different services run on separate nodes.

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

I didn't know about this problem but was already thinking it sounds even harder. And the resulting IDs are probably quite large.

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!

Thank you, will do!

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/

Any company that doesn't want to use this is sus.

Looks like a great way to collect honest, accurate feedback - love the anonymous aspect!

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.