Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filters #18

Open
tobbeanderberg opened this issue Aug 18, 2012 · 2 comments
Open

Filters #18

tobbeanderberg opened this issue Aug 18, 2012 · 2 comments

Comments

@tobbeanderberg
Copy link

Since it is possible already to tag your updates with #tags (something that we simply have to start doing) a natural feature would be to have filters (better than search) to filter your own stream. Activating a filter would be sort of like an equivalent to a FB-page.

A follow up feature would then be to enable filters to be stored for later reuse. This would be an equivalent to FB-likes.

The final step would be to distribute the filters (giving users the possibility to see what filters their friends have stored). That way you would see your friends likes and interests.

@jancborchardt
Copy link
Contributor

I’m actually not sure about tags. As we see from Identi.ca, Twitter and Diaspora, this can lead to #tag spam. Also, tagging is extra work people need to do to make stuff computer-readable. It’s not very pleasant to read »Message text #tag #tag #tag« or »Message about #stuff and #things«.

Instead, a simple stream search would be a good filter (it’s most annoying that Twitter can’t do that).

@brolund
Copy link
Contributor

brolund commented Aug 18, 2012

I agree we should be able to filter/search, and I think filter streams would be great. Since you always filter stuff locally anyway, we actually don't need the tags for a central server to understand what to index. Less messy text than e.g. twitter, more powerful searches (in your accessible data).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants