Your response feels in bad faith. Docker is the default registery. That gives them n amount of responsibility. Not to mention organizations should be accountable for their bad behavior. Don't give them a pass.

Your position is one of presumed entitlement, where you rely on services being provided because the outcry of not doing it would be costly.

So you're right in that sense. It's essentially blackmail: free services in exchange for staying silent.

I think it's unhealthy.

And I argue that we need properly funded, independent services, with clear motives.

This guy has an amazing YouTube channel and just released a really cool book. I'm doing a book club going through it right now and it's really cool!

Oh snap it's Forest! I wonder what he's up to these days. He used to be a dev at Uber Entertainment and did some cool community engagement.

> Cries for help on the Spotify forums were ignored

Yea sounds about right :(

I made this to handle graceful shutdown of a net/http.Server and other similar components.

I found myself implementing the same pattern over and over again, hope people can benefit from this simple small library.

I like this. Have you considered releasing the source so people can run it on their own servers?

I would love to make the source available. But there's no getting that genie back in the bottle once you go that route. I wanted to release it and get some feedback before deciding what to do with it. That said, a server that supports the examples on this page is pretty trivial to implement (especially if you skip the pubsub stuff). I had a working prototype in a weekend. Multiple implementations would probably be a good thing.

EDIT: also, the current state of the code base is not something I'd be excited about having my name attached to ;)

You can think about releasing the code with no license or with some form of the newer BSL or something.

It won't stop bad actors from stealing your code and using it but you will stop most corporate actors from touching it (and they are the ones you'd want to pay in the future anyway).

Anders, please, opensauce it!

Ah yea I totally understand.

I love this thing though. So simple but powerful.

Now that we've all seen the awesome implementation I think a clone in Go is not far off.

If I don't see one by EOD I'll have to make - is thing is super cool

You'd better post the code

Here's the extra poor man's version to get ya'll started. It doesn't have any of the auth/rate limiting/etc or pubsub, but it should basically work for the MPMC queue stuff:

https://github.com/patchbay-pub/patchbay-simple-server

Note that this will leak memory since there's no logic for removing old unused channels.

I did one too -- https://github.com/edoceo/httpubsub

Nice!

And, a bit late, me too, of the pub/sub option that sounded more appealing to me. https://github.com/olup/patchcreek

I made a similar project when starting to learn Go. It's opensource and it works. Just don't host it out on the internet. Intranet should be good because no security audit has happened. This was sort of an MVP

https://github.com/sairam/daata-portal/tree/master/daata-ser...

^^^ This. The kind of people who use this are power users who want to run this on their server. Or use IFTTT otherwise.

This is so cool! I've just been sitting here listening for a while now.

Can we change the title to the actual article's title? The HN one is extremely inflammatory.

Thanks.

What the heck was the submission link? The most technical it got was "using some clever database coding"...

So happy to see a Wiki Tribune link here. I think the project is super cool, I hope it stays around.