They want to know where the holes are so that they can show a loading state.

You don't need templating ($1 etc.) for that as long as you can describe the holes somehow, which can be done out-of-band.

If we imagine a streaming protocol of key/value pairs that are either snapshots or deltas:

    event: snapshot
    data: {"topPost":[], "user": {"comments": []}}
    pending: topPosts,user.comments

    event: delta
    data: [17,{"comments":[{"body":"hello world"}]},"user"]
    pending: topPosts

My guess is the JSON serializer uses strings for int64s to avoid loss of precision.

> Stripe gets 99.999% uptime on top of a MongoDB-like database

Isn’t it actually MongoDB? They describe it as an “extension” [1] but it sounds like they added cluster management without changing the database itself.

[1]: https://stripe.com/blog/how-stripes-document-databases-suppo...

Stripe runs a ton of Mongo replication clusters and uses home-grown proxy services on top of Mongo that manage and control where data lives, so the services don't have to think about that side of things. I'm not sure what changes have been made to Mongo itself but for the most part it's standard Mongo 4.

If you take open source MongoDB and add 10 lines of custom proprietary code, is it still MongoDB? What about a hundred, or a thousand, or a million? What if you change the interface? Ultimately you can give the modified service any name you want, and whether it is "actually MongoDB" or not is a subjective judgement.

OIDC is what fixes the “dog breakfast” criticism. With OIDC you (in theory) don’t have to write custom modules per provider anymore.

It would fix a lot of the provider specific aspects of OAuth2, if the spec would be more strict on some claim (attribute) names on the jwt ID token. Some provide groups, some don't. Some call it roles or direct_groups. Some include prefered_username, some don't. Some include full name, some don't and don't get me started on name and first_name.

If you implement OIDC you must certainly provide a configurable mapping system for source claim name to your internel representation of a user object.

That sounds bad. Why would they under specify all that??

It’s hard / impossible to write a perfect spec maybe?

Or OAuth2 had a specific use case but has since been wrestled to do anything auth related

And chance this is open source?

I’m building something similar and I can’t decide on the relationship struct tag syntax to use. Would be neat to see how others are thinking about it.

Most cloud providers will accept a cloud init cloud config file. Sometimes they call it a “script” but they still accept the Yaml file if it has the `#cloud-config`.

There are modules for setting up ssh, adding users, installing packages, etc.

https://cloudinit.readthedocs.io/en/latest/index.html

It is used by grist (https://www.getgrist.com) to sandbox Python formulas.

Buncombe honestly did a much better job than the surrounding counties. Up here in Madison County most of the updates were only posted on Facebook. A lot of the updates from here and surrounding counties were posted on Facebook as photos of text or videos with no caption.

I get that these counties don’t have the budget or the technical staff for this but it’s really unfortunate.

You can listen without a license. I was able to hear everything on a $15 handheld and it was immensely helpful.

In an emergency you are allowed to transmit without a license. There were plenty of unlicensed calls going to the Mt. Mitchell repeater.

All that being said, I am definitely getting my license once this is over.

> You can listen without a license

You can also talk without a license, who's going to stop you? Especially in an emergency situation.

I don’t know anything about this topic, so forgive me if I’m wrong.

Would there be any risks associated with increased “free for all” amounts of radio traffic going around during a natural disaster like this? Couldn’t specific channels become cluttered to the point where signal is too disrupted to read, or is that not quite how it works?

I think there are thousands of frequencies. Traffic can split up into those.

Go is simple like C is simple. Add a garbage collector and concurrency and it’s easier to do some things but the simplicity of the language means you have to intimately understand more of the runtime to not shoot yourself in the foot.