A problem I could see with that would be a sort of information overload. Say I'm a programmer, but I only work in Java and C++? Wouldn't subscribing to /t/programming mean I also end up seeing all the content from /t/python and /t/django as well, even though they're irrelevant to my interests? If Python is more popular than C++, wouldn't it flood out /t/programming? And a post in /t/CanadianNews – say, a story about the results of the transit referendum in Vancouver – wouldn't necessarily interest readers of /t/WorldNews, but Canadians who also want to read news stories of global importance could subscribe to both. I think generally, content posted to more specific tribes is accordingly specific, while things posted to the more popular tribes are necessarily more broadly applicable.
I know you said readers could tailor it, but I'm not really sure what you're imagining that's significantly different from the multi-posting. One nice modifier that's already in place is that snaps move up in their respective tribes based on how many votes they get in that tribe, not in total.
It's a cool idea, but the idea as it is sounds really complicated both to implement and to use.
I was also going to mention multi-posting in response to this. With this fantastic feature, a user must always make the decision to post it in the appropriate tribes. My Python snap may also be relevant to general programming enthusiasts, so if I have evaluated it as such, I still have to make an active choice to post it to /t/programming. This way there is an extra layer of quality assurance.
Perhaps some kind of separate multi-tribe (a la multireddits) or individual custom user 'mash ups' would work better.
A problem I could see with that would be a sort of information overload. Say I'm a programmer, but I only work in Java and C++? Wouldn't subscribing to /t/programming mean I also end up seeing all the content from /t/python and /t/django as well, even though they're irrelevant to my interests? I
Yes but you could pick how much of them you want to see. By default, I would go with some of the first level tribes (so some Python in your Programming) and none of the second level (so no Django). But you could vary how much you want to see of all of that.
I know you said readers could tailor it, but I'm not really sure what you're imagining that's significantly different from the multi-posting. One nice modifier that's already in place is that snaps move up in their respective tribes based on how many votes they get in that tribe, not in total.
The problem I see with multiposting to fix that is that some subtribes would be barely visible while they should be and some would just be too heavyweight. Therefore, some tuning would be left to the user while if you multipost it's one size fits all.
It's a cool idea, but the idea as it is sounds really complicated both to implement and to use.
A lightweight idea to start could be to name « sister tribes » which would contribute to make things more discoverable.
A lightweight idea to start could be to name « sister tribes » which would contribute to make things more discoverable.
That's true – for readers, a mention in the sidebar/description might suffice, but it'd be nice to have a (more accurate) way to find potentially-related tribes when you're posting something, too. Hopefully that will improve on its own as Snapzu adjusts to the huge new influx of users.
Just curious, how do you browse right now? I'm really enjoying using the "tribe feed," which shows me everything from the tribes I've joined in chronological order (newest first).
That's true – for readers, a mention in the sidebar/description might suffice, but it'd be nice to have a (more accurate) way to find potentially-related tribes when you're posting something, too.
Making it official means it's machine readable and that brings lots of interesting possibilities. :)
Hopefully that will improve on its own as Snapzu adjusts to the huge new influx of users.
If we want one, we just have to advertise as such : Snapzu, where you can edit titles. :)
Tribe feed / directly going to the tribe / frontpage.
I have a sub I moderate on the other site I'd like to bring here, I'm starting with the people who are both unsatisfied with reddit and compatible with a more snapzu approach.
True, but isn't that just complicating the issue rather than simplifying things? Too many unnecessary features and things start to get bloated – in my opinion, it's much better to have to add functions than remove them – simpler systems should be the default.
A problem I could see with that would be a sort of information overload. Say I'm a programmer, but I only work in Java and C++? Wouldn't subscribing to /t/programming mean I also end up seeing all the content from /t/python and /t/django as well, even though they're irrelevant to my interests? If Python is more popular than C++, wouldn't it flood out /t/programming? And a post in /t/CanadianNews – say, a story about the results of the transit referendum in Vancouver – wouldn't necessarily interest readers of /t/WorldNews, but Canadians who also want to read news stories of global importance could subscribe to both. I think generally, content posted to more specific tribes is accordingly specific, while things posted to the more popular tribes are necessarily more broadly applicable.
I know you said readers could tailor it, but I'm not really sure what you're imagining that's significantly different from the multi-posting. One nice modifier that's already in place is that snaps move up in their respective tribes based on how many votes they get in that tribe, not in total.
It's a cool idea, but the idea as it is sounds really complicated both to implement and to use.
I was also going to mention multi-posting in response to this. With this fantastic feature, a user must always make the decision to post it in the appropriate tribes. My Python snap may also be relevant to general programming enthusiasts, so if I have evaluated it as such, I still have to make an active choice to post it to /t/programming. This way there is an extra layer of quality assurance.
Perhaps some kind of separate multi-tribe (a la multireddits) or individual custom user 'mash ups' would work better.
Yes but you could pick how much of them you want to see. By default, I would go with some of the first level tribes (so some Python in your Programming) and none of the second level (so no Django). But you could vary how much you want to see of all of that.
The problem I see with multiposting to fix that is that some subtribes would be barely visible while they should be and some would just be too heavyweight. Therefore, some tuning would be left to the user while if you multipost it's one size fits all.
A lightweight idea to start could be to name « sister tribes » which would contribute to make things more discoverable.
That's true – for readers, a mention in the sidebar/description might suffice, but it'd be nice to have a (more accurate) way to find potentially-related tribes when you're posting something, too. Hopefully that will improve on its own as Snapzu adjusts to the huge new influx of users.
Just curious, how do you browse right now? I'm really enjoying using the "tribe feed," which shows me everything from the tribes I've joined in chronological order (newest first).
I actually suggested a feature to formally link tribes earlier. :)
Making it official means it's machine readable and that brings lots of interesting possibilities. :)
If we want one, we just have to advertise as such : Snapzu, where you can edit titles. :)
Tribe feed / directly going to the tribe / frontpage.
I have a sub I moderate on the other site I'd like to bring here, I'm starting with the people who are both unsatisfied with reddit and compatible with a more snapzu approach.
[This comment was removed]