Share good ideas and conversation.   Login, Join Us, or Take a Tour!
comment by doesntgolf
doesntgolf  ·  1349 days ago  ·  link  ·    ·  parent  ·  post: Hubski Update: Tags: a bit less personal

Sweet! I think I prefer it this way. Thanks for the update.

I've mentioned this idea before, but I'll bring it up again for sake of discussion. I think manually setting personal tags should be done away with, and users should be able to follow any combination of @user/#tag/.domain that they want (including all three in one follow). This would simplify the submission process slightly (since one wouldn't have to think in terms of personal tags and whether they'd like to use one), and give more flexibility in what a user can follow. I have no idea how feasible this is with the site architecture, but I think it'd be really cool to have.




mk  ·  1349 days ago  ·  link  ·  

Part of that last update was an effort in that direction. I'm definitely a fan of pull-based curation; however, we didn't find much evidence that people were looking to use it. Presentation is an issue too. insomniasexx has been working on a redesign, and in it she has a follow icon, which reveals a drop down list of things that can be followed. But, even then, things get pretty complex with such a schematic. Consider if I make a post linking to space.com, tagged #space and #mars:

  mk
  mk.space
  mk.mars
  mk.space.com
  #space
  #mars
  space.com
And that doesn't include a community tag.

There is also the issue that some people like to use personal tags for specific content. That is, I might want to use the tag #music.mk specifically for music that I want other people to hear, but not for articles that relate to music or the music industry. Of course, I could make #musicilike.mk. But, I think personal tags are more likely to be followed when they aren't created for every post, as they then suggest that the author is doing something with special intent.

caelum19  ·  1349 days ago  ·  link  ·  

I think the only time people will want something as specific as mk.space is when someone is compiling a list or like you said when you want to refer someone only to the posts you have about space.

I also prefer we keep the interface simple and uncluttered, so maybe it would be nice to be able to do filtering with URLs for example

hubski.com/?tag=[music, space]user=[mk, caelum19,eightbitsamurai]

or if you don't like my taste in music hubski.com/?tag=[music!(caelum19), space]user=[mk, caelum19,eightbitsamurai]

or if you only like eightbitsamurai's taste in music hubski.com/?tag=[music.eightbitsamurai, space]user=[mk, caelum19,eightbitsamurai]

mk  ·  1349 days ago  ·  link  ·  

You can build some URL filters, but we don't currently have an 'or' option for variables:

Here are all posts tagged with #music posted by ecib and shared by myself:

https://hubski.com/tag?id=music&author=ecib&shareby=mk

Here are all posts tagged with #bitcoin that I replied to that have more than two shares:

https://hubski.com/tag?id=bitcoin&replied=mk&over=2

This is all the #music posts that 8bit has shared:

https://hubski.com/tag?id=music&shareby=eightbitsamurai

caelum19  ·  1349 days ago  ·  link  ·  

Oh cool, didn't know that. Out of curiosity are these indexed?

mk  ·  1349 days ago  ·  link  ·  

No. :) We should probably add them to the primer page at the very least. Here's what we have:

  time shares over under author replied voteby shareby type
doesntgolf  ·  1349 days ago  ·  link  ·  

For design, I could see something like this in the upper right where the follow links are:

  follow @user | follow #tag1 | follow #tag2 | follow .domain | + more
With more being one of the cool popups with:

  follow... 
  @user#tag1
  @user#tag2
  @user.domain
  #tag1.domain
  #tag2.domain
  @user#tag1.domain
  @user#tag2.domain
Would definitely be less crowded with only one tag, but this would be mainly the same as it is now but with a "more" button. But, I will definitely concede that it would be a waste to implement if it weren't going to be used.

edit: I also completely agree with caelum19. A nice query string structure would be super nice to have, and I think it'd go well with more specific following options.