ItsABytecode

Silicon Valley's not alright

Edit: fixed silicone reference

Some of this is pretty good stuff, but I hope standardizing on a 128 item checklist doesn't discourage people from making websites

Heading says "no sintering". Text says "...lasers. Metal powder in, metal parts out"

I don't really understand the distinction here. Are you saying that it's not possible to harm someone by damaging their property?

Sure I destroyed their car and they weren't able to go to work and got fired, but I didn't physically attack them so no harm done.

I had a hard time parsing the title at first. I was like “I’m pretty sure vacuum robots have to be locally deployed”

I didn’t think the code I just merged was that bad

I think still need some moving parts for the build plate if you want to cure more than 1 layer of resin

Edit: from the MIT article, it sounds like the goal is to eventually use a hologram to cure the entire print at once. Related video: https://youtu.be/Ha0QA7iLGy8?si=wWSqex16ybyUDWxE

AWS is pretty aggressive about banning senders with high bounce/report rates. I know from working in an industry where customers had terrible email systems

This looks pretty neat. When I used SES at a previous company we had to do a lot of stuff like bounce tracking and monitoring ourselves so I definitely see the value.

One recommendation would be to use have customers create an IAM role and use cross-account role assumption to access SES on their behalf. That way you don’t have to deal with handling long-lived credentials

I think iMessage is a great example of “Embrace, Extend”. Apple didn’t build a standalone chat app because everyone (in the US) was already using SMS on their phones and “hey if you happen to be SMSing another iPhone user you get these extra features”

This hacking is more DMCA than CFAA

By “private API” do you mean undocumented public API?

So no 3rd party client software unless the company running the service gives explicit permission?

No 3rd party batteries in devices or 3rd party ink cartridges either

I feel like “email is dead as a decentralized protocol” is paradoxically a meme among Gmail users. Counter-anecdote: I haven’t touched Gmail in years and I still send and receive email fine

I’ve never really understood the difference between a gift economy with the expectation of reciprocity and a regular non-gift economy

“From a content discovery standpoint, I’m really interested in how we can seed conversations and seed experiences with really high-quality content — certainly, editorial publisher content”

I’ve been waiting so long for my mastodon conversations to be seeded with high quality editorial publisher content

Also, Let's Encrypt security is a joke - they issued fake certificate without serious checking. Using unencrypted HTTP for confirmation is a vulnerability

They can’t use HTTPS if you don’t have a certificate yet

They’re probably thinking of shared hosting environments that don’t have the SQLite library for PHP installed. That seems like a concern you could raise about any database connector, though

I do love telling users to RTFM as soon as they open the box. In some way I'd prefer that to today's "What manual? You don't need a manual"

Wait, to install this python package I have to have a working c, rust, and fortran compiler?

I can't really infer much from this demo since the documentation it reads and the API it calls aren't public

edit: I was wrong. The site just doesn't have a http -> https redirect

https://sampleapis.com/api-list/wines

I just use a web browser