s5fs
Joined 14 years ago
Joined 14 years ago
Parental controls for EA games are shit.
Parental controls for Amazon are shit.
Parental controls for Netflix are shit.
Parental controls for YouTube are shit.
Parental controls for Roblox is especially shit. They have games like "Gay Test" and "Femboy Test" marked as All Ages which is bananas to me.
The end result is that my kids can't use these services without an adult present, which defeats the purpose of having Parental Control in the first place.
This confused me for a while, having two separate "products" which are sold differently, but can be used by the same tool.
I encourage you to peek at their changelog (https://www.sudo.ws/releases/changelog/) for more insight into why this project is still under active development.
1. Do you support tagging resources?
2. You mention provisioning Pulumi resources, are you "simply" a wrapper around Pulumi? If so, are you relying on Pulumi for state management or does Stelvio have it's own state manager?
3. Do you support cloudfront? Imo this is a vital service for building even small production apps, esp if you are serving static assets out of S3.
4. I saw references to API Gateway v1, do you also support v2?
5. One of the cool features is that you're able to handle all the IAM stuff, but can that also be easily modified? Like, if I want to create a new lambda that interacts with an existing dynamodb table, how would I describe that with Stelvio?
Sorry for the pile of questions lol but you got my attention :) You have a lot of competition in this space and I'm curious to see how your project will evolve. Best of luck!
Same story with data models, let's say you have the same data (customer contact details) in slightly different formats in 5 different data models. Which one is correct? Why are the others different?
Ultimately someone has to solve this mystery and that often means pulling people together from different parts of the business, so they can eventually reach consensus on how to move forward.
I was a camp counselor at node camp three years in a row. He created such a magical experience that I cried when I got home, I wanted to live in nodecamp forever. I still do.
Seeing some of the folks posting in here makes it hurt worse. I have so many memories, like I remember all of us riding the bus back and forth to the camp, so much laughter and fucking around. Hanging at each others houses, going to meetups, and just being part of something special. Talking shit thru pull requests. Late night dorking around on meatspac.es etc etc etc I could go on for days.
Thank you Mikeal for all the good times.
I crave novelty and have a love for bad technology. I was an early nodejs adopter and loved es4 but newer versions of the language is too easy to use lol!
Based on the information provided, it seems highly unlikely to me that a guy who passed up an easy payday for a baseball would get an attorney friend to lie for what is likely going to be a very small claim. He still attended the game, and another game a couple days later, which likely rules out substantial suffering. So, given the low potential payout what would be his motivation? Simplest explanation is the guy just fell through an ill-maintained bridge. Could happen to anyone, really!
One year my buddy decided to get serious gear and fish for oversized sturgeon. This was purely catch-and-release, barbless hooks. We would sit on the edge of the shipping lanes because that was the deepest part of the river.
(incoming fisherman story)
One day we hooked a gigantic fish, we were in a 24 foot boat and I swear it was longer than that. We pulled it near the boat to unhook it and the thing was amazing! It was covered in battle scars from boat propellers or something, but the weirdest part was that it had a ton of fishing line hanging out of it's ass. Over the years it must've swallowed hooks and line, and it was just swimming around with literally feet of the stuff.
We retrieved our hook and watched it swim back into the depths. I never went oversized fishing after that, but it was incredible to think how old that fish was, what it had been through, etc.