4 ms·
As long as you're willing to accept a company that is not growing in revenue due to new value created, you can build a system entirely dedicated to maintenance
by ebiester 4y ago
As long as you're willing to accept a company that is not growing in revenue due to new value created, you can build a system entirely dedicated to maintenance of existing features with a small group.
In Twitter's case, however, how long is it until they're sued for child porn (lack of moderation) or get 50 million euro fines for running afoul of Germany's Network Enforcement Act?
- orangepurple 4y agoImagine going to jail because someone uploaded a file to your computer
- madeofpalk 4y agoWhich, by the way, is exactly what "Section 230" prevents.
- jcranmer 4y agoChild porn is explicitly carved out from the section 230 immunity.
- bdcravens 4y agoI'd consider staff in those areas core to the product. Many of the dozens of projects at https://opensource.twitter.dev/projects/ https://opensource.twitter.dev/projects/, not so much. Staff whose job revolves around standing at booths at conferences and handing out swag, ditto.
- ebiester 4y agoHow many of those are active? How many of those were created for the purposes of twitter infrastructure and released as a side effect? I'm sure that you can stop supporting the open source section. However, how much of their platform team is core to the product? How much is still required?
- bdcravens 4y agoI'm sure many of those projects are out of date. Either way, they could probably make them all private for their purposes and stop accepting PRs (probably just turn them lose on the greater OSS community for those that still rely on them)