140 karma · joined February 28, 2012
Migrating users off twitter seems like it might be simple (ie 1 click migration via oauth and apis to migrate tweets and followers I'd imagine). I think the carrot doesn't need to be all that big these days as twitter splits up their user base with paid and unpaid users as well as far too many ads in all streams (sans add blockers).
Heck I think you might even be able to post back to Twitter if the user migrated to keep un-migrated followers in the loop. (Although it's been a while since I've looked into their API).
I don't really know how you would motivate the cross section of people who have ad blockers though as I think this is the critical part (ie what is less friction).
You also need to probably have some relevant marketing (ie the Opera/Aston effect) to pull in the significance to start the fire too (this might be organic given the generational "not your parents thing")
Come to think about it. If you could overlay the graphs you might not need to assimilate but be a valid competitor making it less of a winner takes all.
Although come to think about it in that case I think perhaps APIs would be shut down to close this vector of competition.
Thanks for also pointing this out.
A move to devcontainers helped this but dictated some ide behaviours (majority of devs are tried and true jetbrains people) so changing they way they use their tools made this a 'no sale' so again like the wiki my scripts sit idle. But I dream for the day a `curl ${url} | bash` can solve these teething issues
To be specific I wish I didn't have to forward a developer to an already obsolete wiki page then nod and smile as they complain/tussle with the experience/vernacular/context of a document that has no owner.
I think this is a bigger problem (which could be mine and mine alone as everyone seems to really like wikis) but I think being able to seed the developer environment with all the tooling config could help stave off (some of) this pain.
So my thoughts: a simple cli related flow gen tool which could generate this interactively. (And could also verify correctness)
Tools that I can think of from the top of my head that need to be configured to handle user config and private repo location(s) are git, docker and mvn/gradle/npm (etc, I figure all package management tools usually need this).
I like the way https://github.com/trailofbits/algo Works to collect configuration in this respect (Using ansible) as well as how eslint does it (I think using https://github.com/gkz/optionator) For setting up base config in the cli.
Anyway hope this helps seed an idea or at least might identify a problem (not sure how lucrative it would be though)
I feel an obligatory 'Joe Exotic' reference should be considered here (but goes against the housecat vibe)
I should review the technical issues that were discovered as it felt like a good direction based on comments read across related hn comments.
(After a quick google I found https://lists.apache.org/thread/9gby4nr209qc4dzf2hh6xqb0cn14... which provides some high level details)
This is a hard balance to make. Technical choices influence the kinds of staff you would want working for you but you also need to prolong/balance the interests of said staff from moving onto the next thing. (I'd love to know how businesses do this beyond just more money and share schemes but maybe this kind of thing just needs to be built into the plan)
(Scanned the Oscar Toledo github/site and found this for anyone else interested https://nanochess.org/chess4.html)
Also wanna throw Mike Pall & Arthur Whitney in there as an honourable mentions (productive gods/100x)
Nice work mate.