APIs for content sites must be free
61–70 of 300 posts
Re: APIs for content sites must be free
#62Earlier quoted context omitted.
but you can access every single shitpost from the website, so why not from API? it's lighter
Most of the time you dont just expose your internal api routes to the world. You need to write curated public facing routes that dont include certain schema or records. Takes time to write and maintain that different set of endpoints
Re: APIs for content sites must be free
#63I've found myself resisting posting comments on Reddit recently - things like answers to simple questions people have about SQLite - partly because I don't want to cross the picket line but also because I realize that I was relying on a very light social contract that was in place there: I would share my knowledge for free, in exchange for which I knew that I was contributing to a larger dataset that myself and other…
This was never a social contract so I actually wonder how you or the original blog poster ever got to that idea. In fact, it's explicitly not the social contract if you ever read the Terms of Service of sites like Twitter and/or Reddit.
Re: APIs for content sites must be free
#64I've found myself resisting posting comments on Reddit recently - things like answers to simple questions people have about SQLite - partly because I don't want to cross the picket line but also because I realize that I was relying on a very light social contract that was in place there: I would share my knowledge for free, in exchange for which I knew that I was contributing to a larger dataset that myself and other…
Re: APIs for content sites must be free
#65Re: APIs for content sites must be free
#66I've found myself resisting posting comments on Reddit recently - things like answers to simple questions people have about SQLite - partly because I don't want to cross the picket line but also because I realize that I was relying on a very light social contract that was in place there: I would share my knowledge for free, in exchange for which I knew that I was contributing to a larger dataset that myself and other…
> I was relying on a very light social contract that was in place there This was never a social contract so I actually wonder how you or the original blog poster ever got to that idea. In fact, it's explicitly not the social contract if you ever read the Terms of Service of sites like Twitter and/or Reddit.
Re: APIs for content sites must be free
#67I've found myself resisting posting comments on Reddit recently - things like answers to simple questions people have about SQLite - partly because I don't want to cross the picket line but also because I realize that I was relying on a very light social contract that was in place there: I would share my knowledge for free, in exchange for which I knew that I was contributing to a larger dataset that myself and other…
There was quite a lot of pushback since the consensus was many comments aren't just for the benefit of the OP but everyone (in fact sometimes the OP doesn't even appreciate the comments they receive but are nevertheless useful to others).
So Reddit walked it back but it does show many of the site's users are conscious of the broader utility of comments outside of just the smaller contextual interactions.
Re: APIs for content sites must be free
#68Earlier quoted context omitted.
> I was relying on a very light social contract that was in place there This was never a social contract so I actually wonder how you or the original blog poster ever got to that idea. In fact, it's explicitly not the social contract if you ever read the Terms of Service of sites like Twitter and/or Reddit.
You're thinking of a legal contract. A social contract is what two sides do in practice in order to not piss the other off.
Re: APIs for content sites must be free
#69An ad-supported website has to get paid. On the web there is at least some stuff they can do to detect ad blockers, or show ads in sneaky ways that change over time and are hard to block.