by StanAngeloff on 10/15/23, 5:10 AM with 45 comments
by NicoJuicy on 10/15/23, 9:11 AM
1. Vercel shipping Indie hackers projects ( their customers) as "app templates" as a host, for marketing purpose
https://twitter.com/nico_jeannen/status/1712749652133683632?...
2. The mentioned infringement of a Vercel employee, mentioned here ( he seems to be fired)
https://twitter.com/nico_jeannen/status/1713139186474406206?...
3. Very broad ToS -> Vercel may delete your app for no reason at all
https://twitter.com/bk_7312/status/1713197808264839479?t=h1T...
by koopuluri on 10/15/23, 6:13 AM
This combined with their marketing strategy of copying popular indie products and turning them into NextJS templates creates paranoia in the minds of builders who trust Vercel with their codebases, analytics, and often even their data (via Vercel's storage products).
It seems that an enterprising Vercel employee has a goldmine of data to help inform their next "side project".
by hubraumhugo on 10/15/23, 6:11 AM
At every decent sized company I've worked for, topics like production data privileges, data classification (public, sensitive, confidential, etc.), data masking, and data anonymization for testing have been top priorities. And these policies are sometimes a true pain in the ass for developers, but they exist for a good reason.
I guess you shouldn't miss the timing to go from "move fast and break things" to "ok we're now a serious business".
by hipadev23 on 10/15/23, 6:20 AM
Is there some tech incubator clause buried in their TOS and this is all okay?
by jlund-molfese on 10/15/23, 5:34 AM
by lloydatkinson on 10/15/23, 6:55 AM
by mdhb on 10/15/23, 6:42 AM
by throwaway290 on 10/15/23, 5:30 AM
by pc_edwin on 10/15/23, 10:53 AM
We are talking about an employee who has access to the customers personal information as part of their job doing something unethical.
I would be extremely surprised if Vercel didn't have industry systems and practices in place for security.
This is an edge case which can only be avoided by building Google-esque systems and practices. I don't think you guys really understand what your asking for here.
This will cripple them in so many ways, it makes so much more sense delay it as long as possible. Not because they can save a bit of money, but because they UX will fall of a cliff, feature velocity will ground to a halt and the product will drift further away from stuff we really want.
by osbulbul on 10/15/23, 10:15 AM
by jatins on 10/15/23, 6:27 AM
I am sure a half motivated employee at your favorite cab service could see which addresses you frequently commuted to in first few years of that service's existence