ajbourg

This is pretty close to what Taalas is doing.

I have long wanted a static blog with a backend content manager that runs serverless. Love seeing this, but we will see if Cloudflare maintains it in the long run.

Not because people don't value their personal data but because they, rightfully, value those promises as worth approximately nothing.

It's fine if you're starting from nothing.

But we wouldn't be starting from nothing. There's a large group of people who would lose income and who will lobby against that.

Seems like it's mostly AWS' answer to Cloudflare D2, but using Postgres as the frame of reference instead of sqlite. (I'm not really sure what to call Postgres in this situation since it's so limited it's clearly not any full version of Postgres in any respect. Postgres-ish)

Your blog is amazing, I would love to keep up by adding it to my feed reader but I'm not finding any RSS/Atom feeds.

Oh my goodness, I had the exact same experience with Home Depot. But then they responded to the chargeback and said it was delivered and no going back and forth with American Express would get them to help. I closed my AmEx card and am deeply skeptical of doing business with Home Depot.

What actions would you propose when Twitter has turned off their API access and basically ignored all requests by developers, users and the media for an explanation?

I have a similar desire, I'm considering trying out AWS' RDS Aurora Serverless v2. (ugh, that's a mouthful) Full Postgres/MySQL but extremely quick scale up and down so as long as you have small use, it shouldn't cost a ton.

I'm also super interested in Cloudflare D1, looking to get my hands on it and try it out.

I was referring generally to the general desire for "the system" to preserve the privacy of kids in care. I think you have to look at it holistically and not just social media. We also signed agreements that we would be very careful with the information we received about our placements, they don't deserve their story being blasted around (even to close friends and family) unless it is needed for the benefit of the child, and even then only to the degree necessary.

I've been in doctor's appointments where the nurse is quizzing me on my family medical history and I've had to stop them with, "We're not biologically related and I don't know the biological history". No need for them to know the whole story.

I feel privacy for kids is really important, for a number of different reasons. (preventing kids from being exploited for likes by foster parents, preservation and ownership for them to tell their story in their way when they are ready for it, privacy, sometimes protection from relatives that don't have their best interests at heart, and probably a dozen other reasons I have never thought of.) The best default is really to keep everything private in my opinion, but obviously not every agency or foster parent will agree to all the same specifics as me.

Speaking as a foster parent: my agency like many have rules against posting foster kids to social media. Usually intended to help protect kid's privacy. I think the motivation comes from a handful of places, protecting kids from being exploited for likes, keeping kids privacy, but a big one in foster circles is so that people don't know you're a foster kid unless you say so. Most adults in the system take great care to not acknowledge kids if they run into them in public to avoid situations where kids have to explain to their friends, "Who is that?" and then having an awkward situation where they have to say something like, "That's my caseworker/therapist/whatever".

> Every person that generates their own electricity stops paying their fair share of maintaining the grid

This isn't true, at least not in Colorado. I pay a number of fees for maintaining the grid and these aren't going away when I have my net meter installed later this week. (hopefully)

Yes, this is one of the best reasons to use network ACLs. (You can also achieve this with routes)

I think the idea is that separate teams with different responsibilities can manage the two different layers. Your app team may manage the security groups but the security team manages network ACLs which limit what can go into or come out of a subnet.