Funny enough, I’m a Vietnamese person from Portland and was doing this exact same analysis in Paris (highest density of overseas Vietnamese population) visiting a dozen places last month.
People visiting for a few days go with a “10 restaurants you have to try in Portland” which are just mediocre chic restaurants you can find in every other city.
They don’t realized how underrated Asian food in Portland is. One, Google Maps and Yelp reviews are negative signals of for Asian food. Restaurants that highly rated above 4.5 are so for the “ambience” rather than the food. Two, the restaurants are dispersed rather than being concentrated around a Chinatown or Little Saigon.
(I don't know of any T-shirts saying "we don't accept pull requests". That sounds made up. We very much did accept pull requests... a great many of them).
I don’t think that has anything to do with not being able to buy a house or have a child. TCG cards are the perfect mixture of consumerism and gambling, and Gen Z has been submerged in both for the entirety of their lives
PinkBike used to be the go-to place for uploading media for further embedding in off-site forums (SouthernDownhill, SingletrackWorld, RideMonkey, NSMTB, VitalMTB) - for example, race reports, sales (when forums had limited storage capacity for users), etc.
Your media was watermarked and made available in different resolutions (a unique feature at the time on a bike specific website!)
I would bet a large chunk of those 5M visitors were hotlinks as I don’t remember their forums being too busy —- but I do remember them being very fragmented with too many subforums.
Unfortunately Facebook Groups has killed off the almost tribal online MTB communities now :(
If you’re using TypeScript then you have a build step and package manager like NPM, which means packages and libraries are published in the NPM package registries.
This website was from/for an era where you hotlink the scripts.
SaaS can provide “open core” or better yet simply sell a hosted version of their fully open source code. If the provider fails to provide, you can fall back to self hosting.
The API equivalent would be open sourcing the data. This is the OpenStreetMap model. If the API provider fails to provide, you can fallback to the underlying data.
That's asking too much. SaaS should give an option for you to export all your own data in a simple, parseable format (like JSON). That's about it. They don't owe anyone their source code, and they don't owe any ethically sourced data (such as employees researching and manually entering).
API access needs better terms. Like guaranteed access for X years at $Y price with Z days notice if there's a change, where Z > 3 months or so.
This was the hope behind the StackExchange data dumps, that the community at large could always take their contributions elsewhere if the service jumped the shark.
Well, before the SE organization tried to kill the data exports off in an attempt to commercialize it towards AI companies, but thats a whole other issue.
