@WeAreAllSatoshi112
918,615 sats stacked
stacking since: #133445longest cowboy streak: 149 verified stacker.news contributorSatsAllDay
I meant to reply to this but forgot...
I wondered how you guys were handling the influx of PRs, balancing that with your ongoing work. I can see how it is nice to let other folks worry about smaller chunks of work, allowing you to focus on longer-running items. But I also know that context switching can be hard, especially if you're doing a lot of code review and actually checking out other people's code, running locally, etc.
I saw the commit to remove him from the footer but figured there would be some kind of announcement at some point. I did briefly share the commit in the dev chat but quickly deleted it because I didn’t want to be nosy
Day 135 of posting mining earnings from the day before: 297 sats on 30Apr2024!
Running total: 87,952 sats!
This is a really enjoyable write up! It’s basically leveraging docker’s platform to broaden an attack surface for more potential victims. But ultimately it has nothing to do with docker technology itself, if I understand correctly
Also, the link to satistics is taking me to @satistics, which I assume is unintentional
What is your take on how the OSCARs are performing? An opinion on the return for investment? I was going to make my own post, but it’s more appropriate to ask in this context.
Also, great update! Go team!
Also, holy shit, you can just spam the S3 URL with garbage and drive up someone’s bill? Better hope you keep your URLs secret.
@ek do we proxy through the SN API for S3?
Day 134 of posting mining earnings from the day before: 303 sats on 29Apr2024!
Running total: 87,655 sats!
I shared this yesterday, too: #522401
I'll open a GitHub issue today