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

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?


yes.


I've used 'private API' exactly how you did and some pedant told me it wasn't a real term so I empathize


HN is accessed via an undocumented public API that you are using every time you visit this site.


And I would suggest it's a bad idea to base your entire business off using that 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


It generally doesn't cost e.g. the printer manufacturer anything when you use a 3rd party cartidge. This is separate from the value/loss described above. I still think once you reach a certain size there need to be some interop requirements though but I can also see why many would say these points are unrelated to iMessage.


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

That's about the strength of it. Unless the protocol is open, paid or otherwise. iMessage is closed and undocumented.


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


Yup, I too receive spam just fine. Greylisting and SPF alone doesn't stop it now. If I want to send e-mail to someone on gmail or office365 it usually ends up in spam.


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


In a regular economy, every exchange is a two-way transaction. I give you something, you give me something (usually of perceived equal value).

In a gift economy. I gift you something. You gift someone something. That someone could be me, but if I don't need/want anything you need, then you just gift to someone else. If there are gifts going around all the time, all in good faith, then most people will receive what they need.

You see gift economies in families or friends all the time. People help others according to their abilities. My rich friend takes me out to an expensive dinner, poor me gets us lunch from that famous food truck. I nurse my uncle when he breaks his leg. He lets my brother's son to live with him for free during college. There is no accounting of how much anyone gave. Just give what you can.

I recommend reading Cory Doctorow's novel Walkaway which describes gift economies beautifully.


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

Search: