Word/tag filter option?

@augier Umm, I'm a bit confused with what you said and the way the pods work. I thought all the pods could talk to each other? Now, my confusion with what you said stems from my interpretation of what you said. Are you saying having a/the user(s) put up their own pods which will help them filter out content? But I thought... err... ugh... headache!! :(

https://www.youtube.com/watch?v=VW27kyh7PVM

Well AFAIK, the pods can exchange some informations like posts, mails, subscribed content, but not all of it. Particularly, in a matter of bandwith limitations, pods do not exchange content marked by tag, even though you subscribed to it.

The only way, you can recieve a tagged content from a user of another pod is having mutual relation. So, by having your own pod, you will nly recieve tagged content from your own pod.

Please correct me if I'm wrong.

Nevertheless, a feature I'd like to see is an option to display or not contents by aspects and by default on the flow section.

How do you mean @augier?

How do I mean ? You mean : what do I mean ? Well this discussion is meaningless... Wait ! I mean not your discussion being meaningless, more like my meaning is meaningles. Ow... I forgot What I wanted to mean... -_-

What I mean is : by default, in the flow section, all the posts of all the contacts are displayed. To show only the posts of certain aspects, you must go to "My aspects". It would be cool if we could parameterize which aspects being displayed on the flow section by default.

Sorry if what I mean isn't very clear, I'm french so... But hey, the end is more important than the means, isn't it ?

Why don't we do both? :P

redmatrix had similar issues and I've provided a word filter there and nobody has issues with it. It's entirely optional. We don't specifically filter "tags"; we match text that shows up in the stream - and provide a "click to open" wrapper around the post if the text was found. So nothing is removed from the stream, it's just collapsed.

The first step is a simple string match. Any string. You can also use regular expressions. Few do, but it's there for the geeks who want to fine tune it. The third option is to add an author qualifier such as "bob::img" (markdown might require something like "bob::/!(.?*)" - which will collapse any posts with images but only from from bob - (somebody who often posts nude girlie pics and there's a sensitive girl sitting behind me at work that can see my screen).

I didn't post this to debate implementations or projects - I'm just trying to give you some ideas to work with; that you may accept or reject as you wish. We've had zero complaints about the implementation. I use it to commonly filter certain video providers and certain polarised debates which re-occur often; as well as the occasional nudity that folks feel empowered to post; so that my colleagues and family don't see it. I might peek at some of these on my own time - or not.

We also provide a way to tag things #nsfw after the fact which others have posted. This also turns out to be an important tool - but takes a lot more implementation/development work. This feature has been known to ignite cross-project flame wars but again I'm not here to debate but just to present different ideas and implementations for working with non-censoring personalised filtering in an otherwise free network.

@augier - I see the use of filtering being in things like:

I want to be contacts with my friend. However, they've just had a new baby called James, and I really don't want to see endless posts about how wonderful their new baby is. So I can keep in contact with them but filter out any posts of theirs which contain the word 'baby', 'James' 'poo' (yes, I really did have a friend posting endlessly about their baby's poo....) and so on. That way I don't have to break the connection with them, I can still see posts they make on other subjects, which I might be interested in, but I don't have to get annoyed by their posts about this baby, which they are fascinated by but I have no interest whatever in seeing in my stream.

That's just one among a hundred examples. Sean raises another type of example. Porn and obscenities are other examples, although mentioning them can be a bit of a red herring because people's minds instantly go to censorship or protecting children and the vulnerable. This is not really anything to do with that - it's about having greater choice over what you see in your stream. And Diaspora is all about choice.

Diaspora's tag system is a type of post filter. It enables you to filter in posts by people who may not be among your contacts but which contain tags you're interested in. All this proposal is for is to extend the flexibility of Diaspora's filtering to enable you to filter out content that you don't see. It should be easy to do this for tags.

Doing it for ordinary text is a slightly different concept, but one I'd like to add, as it enables you much greater control over what you choose to read about. There's so much content in Diaspora even now, which will only increase as the network gets bigger, so it can only be a good thing to provide users with greater means of controlling the content they get to see, for whatever reasons they might want to include or exclude certain types of content.

There's actually a really nifty Javascript browser extension called SocialFixer, which gives users all sorts of controls over how Facebook appears and what content they see in their streams. Post filtering is very advanced in this extension, and there are lots of good ideas (although probably not code) that Diaspora can use from this.

Yes, of course there are greater priorities to do with the performance of the network (improving federation, database control and so on), but that doesn't mean that other ideas like this one aren't really important for the future development of this social network.

@mikemacgirvin Thanks for the suggestions, that's a great piece of insight. :)