Hacker Newsnew | past | comments | ask | show | jobs | submit | ItsABytecode's commentslogin

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


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: