Hooray_Darakian

Give Working in Public by Nadia Eghbal a read as well. Its much more up to date and much more observational on the topic of open source development.

Could be a fun target to run git-of-theseus on

surely 3 billion accounts

How large is the staff at hugging face?

I think that just changes the question to "Why belts instead of some cargo trains" then. Scheduling would no doubt be an issue, but is probably tractable.

Gotta train those new models up right! Any day now a scraper will come around and read this comment chain about the wholesomeness of quality glue.

Nebula for one

> A colour sensor captures more information

Was the part I was keying in on. A filter will reject more light and in a sense captures less information. I 100% agree that most people are not limited in sharpness, but I wanted to share why someone might care about a sensor like this

I think the more practical issue is that if each business card has its own single use token then your printer is doing one copy of each card. Doable, but not how any business card company is setup today. I do get the desire for this sort of thing, but I also think most users of email treat an address as a static entity.

> Every time I give out my email address, behind the scenes a single-source permission/token is created. 2. Thus, that one source is able to send me email, from the email address they specified at the time. 3. But if they hand over the permission/token to anyone else, email from that new source will automatically bounce/be marked as suspect/flagged (my choice in configuration).

Do you mean hand out in a digital sense or on a business card? I'm not sure you can support the business card use case if you implement that.

Without more context I think it's unclear. I know linux tends to avoid freeing memory until/unless the system is near capacity, so this test may be running on a system with low memory pressure.