@sabbatical@zero recommend-a-follow sounds awesome. just an annotation w/ a list of user IDs. someone could aggregate those and build a tool to tell you who you should follow. i know @adrianus is interested in this stuff...

@adrianus Yeah, that's the foundation, but I don't just want the topics to be arbitrary. I want them to be affinity groups for people based on things they've declared in their profiles. And I like @sabbatical's idea about letting users vet each other.

@ablaze@adrianus@berg@sabbatical@zero I love the rooms to join idea, that way you can chat on a topic in real time and perhaps choose not to muddy up your main feed bombing your followers with a ton of posts.

@johngordon There's no reason post objects can't use these. However you'd need to tag your post when posting, as there's no editing on ADN after the post is submitted. Maybe the permissive messaging stuff will be mutable. /cc @orian@berg@mthurman#llama

@johngordon@ryantharp If you use an ontology list I'd suggest a small set of categories rather than trying to really represent posts. The problem is the if you have too many the UI for any casual use becomes unwieldily. I'd skip the big ontology lists.

@johngordon@ryantharp Having a more exactly ontology would be nice but the reality is you'll never get anyone to tag things. That would leave bayesian or rule based tagging which is a pain and wouldn't work well with 256 character posts.

@johngordon We have come up with a way to tag posts even though they are immutable like @ryantharp says. You make a special machine only post as a reply and store the tag there. We have not yet implemented metaposts, but I intend to.

@clarkgoble@duerig Editing can be implemented in clients by using a delay before post as @dalton has pointed it out before. However no client has done this, including my own as it would take some reworking. Those typos sure are annoying. =]

@clarkgoble@duerig Yes, we're going to focus on the tags users are actually requested and using. However overtime, when we switch the UI from check boxes to a more traditional text-based auto-complete tag UI that should help out a bit.

@clarkgoble@duerig Possibly. I'm also looking into auto-categorization, I've done some work with this in the past. Luckily auto-categorization won't require writing anything to the API or having to share across clients.

@ryantharp Well one reason they don't is because adding an additional half hour rtt between messages in a conversation would be awful. Not to mention what would happen if the user closed a browser window before the time was up. Best to think of it as email

@ryantharp@duerig Let me know if you need any help. I'm swamped for at least an other month and a half and then my time opens up. I have a categorizer I'd written during the height of the .com boom which did a lot.

@ryantharp@duerig It was optimized for queries/ontologies that were megabytes in size. Had some huge contracts with it in the financial markets until the crash happened then all our clients were bankrupt. Has some nice ways to combine bayesian & rules.

@duerig I'm still on the fence about using ADN for data journaling. Those system will be hard to maintain over time as response time decreases and more data is required to load in. I think @q's QC design with it's own DB is the way to go /cc @orian@berg

@duerig Very true. Though I'm sure 60 seconds would be the recommendation maximum. My own thoughts were more towards 30 secs or so, and I'd might tweak after implementation. See how it felt. Can use a server side queue to hold it for the browser closing.

@duerig@ryantharp Don't know the ADM backend so I can't speak. Modify the database entry and then send a signal out it changed. Most forums and even WP plugins do this now. Question is scaling which is probably real issue. Has to be done by ADM though.

@ryantharp I would at the least want to see how messages work before trying that. But metaposts don't work like that. They are a post about a post by a third party. So you may read a post w/o caring about metaposts but they are useful in discovery or tags.

@johngordon Right now we're merging that ontology system I developed 10 years ago with an underlying text database engine we'd originally started developing for a bid to run eBay on. We'd put it on the back burner for a few years but are getting it going.

@fields@johngordon I agree here, the plan was to show the top five tags per post (easy to compute, easy for users), allow auto-complete on any tag. Duplicates of a tag for a post given by different users would equate to a +1. //@ryantharp@duerig

@jdscolam I think any forward progress on tagging would be worthwhile whether it be server or metapost-based. I ended up getting into the patter/vidcast stuff so lost forward momentum on it myself. :/ So much to do here. cc/ @johngordon@ryantharp