|
|
|
|
|
by JimDabell
41 days ago
|
|
> Thinking of it in advance does make it easier but it can definitely still break a business If privacy regulations can break your business, then I think there’s a very high chance what you are doing is exactly the sort of thing the regulations are explicitly designed to discourage. > now there's a whole CMP TCF2 protocol you have to implement. That’s exactly what I’m talking about. There’s no regulation saying you have to implement that. That’s a consequence of you making the choice to trade user data. Somebody who does not choose to do that has much less work to do. This is an example of the regulations working as intended. You’re supposed to see the friction and make better choices up front to avoid it, not make the same choices then complain about the friction. > eventually they screw the little guys more than they screw the bad actors. Little guys are often the bad actors. |
|
Anyway, the discussion was about the harms of regulations and why developers would resist these. I personally know several indie mobile developers that had games that their core business model was ad monetization, and the regulation made these businesses less viable, and it's likely that players who enjoyed these kind of games, will now see less of these indie games.
I personally think this regulation does more harm then good for small businesses and players alike. I think legeslation has to be super careful when it comes to regulating businesses, anytime I had to deal with compliance around accessibility, privacy, transparency etc. I saw how intentions were good, but execution was absolutely terrible, with so many holes that the ones who benefit the most are the big companies that can workaround these clauses, while good intentioned small businesses need to spend money on compliance before they even know if the business is going to be viable.