@brendt raised an issue this morning that is very likely true: the more users we add, the more important categorization becomes. once you arrive, you should instantly get connected to groups that talk about the topics you like, php, laravel, next, rails, all of those
we don't have a perfect idea for that yet.. if you have any, just drop them in the comments below
commit dbc4e5e
We can find all public repos of a users and pull their topics.
Those are topics
how about #hashtags and allow people to tag their own account profiles, so for example when you view #php you can see both a list of posts with that tag and also accounts where they've tagged themselves that way as well?
user categorized hash-tags (#php, #rails, #rust etc) and lists like on X would be a simple start.
Being able to create lists with users you like without following would be usefull. Dynamic lists generated by getting posts by hash-tag would be cool.
Show threadI think the nice thing about it at the minute is that we are all in the same pot so for latest we see all posts. Everyone is on a level playing field. It'd be good to keep that rather than an algorithm or something interfering with the true feed. But some sort of separate…
All commits are already embedded, right? so that vector already knows what a post is about, and you could maybe turn it into a list of topics people can follow
Find out most used languages on your GitHub profile and add you to communities based on that? 🤔
Embedding similarity: turn every post, group and topic into a vector, then tag each one with the topics it sits closest to.
on signup, pull languages and repo topics from their public GitHub, pre-fill a topic picker or "tune your feed" page, and then suggest the closest groups.
A topic selection, with suggestions based on the languages in your own repos could be a nice onboarding process (if you have that info of course).
Create an Interest Tab, then use existing semantic search for the topics of interest, all merged into a single
latest feed.