Loading Profile...
User-defined splitting of large sites
Currently, all of Wikipedia is tracked as a reference/search site. That's not entirely true :) I would like to know how much time I spend editing Wikipedia and how much I just use it for reference. A few simple regular expressions, such as en.wikipedia.org/*[Tt]alk:* or looking for action=edit, would do the trick ...
Wouldn't it make sense to let users split up sites themselves?
Wouldn't it make sense to let users split up sites themselves?
I’m otherwise very impressed.
1 person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?It would!
Categories are necessarily imperfect, but are easy. We have tagging, which allows you to classify sites on a more granular and/or subjective level.
In terms of splitting, that would be nice-- for 3rd level domains that's easy -- RescueTime treats them as unique entities. For what you're talking about, we'd need to treat each page/view as an entity in our database. I'd love to do that. The challenges are:
1) Doing that in such a way that our servers down melt.
2) Doing that in such a way that is easy to use and easy to understand.
#2 is easier than #1.
It IS something that we'll continue to explore, but it's not a short-term effort. ;-)
I’m thankful
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Thanks for the quick reply. I understand that this is not a high priority. However, in the case of Wikipedia, splitting it into two "sites" -- 1) Wikipedia and 2) Wikipedia (editing) -- would only require matching simple strings in the URLs. Isn't that, more or less, how you already distinguish subdomains of google? Perhaps a more sensible approach would be to allow users to collectively define sub-domains similar to how categories are set by voting. Once a subdomain gets enough votes, it is installed in the database... -
Inappropriate?Tony said:
"1) Doing that in such a way that our servers down melt.
2) Doing that in such a way that is easy to use and easy to understand.
#2 is easier than #1. "
I'm not sure about that. Actually I think #1 is easier than #2. As ..:
I'd like this tagging to be local. I know that this is more difficult to debug and it's more difficult to help the user setting it up and it's more difficult to user the power of the crowd, when everyone is doing it locally.
For all of that: You can have my local script and change it from the website. And recommend scripts to me on the website. But I want to be able to locally change "https://twitter.com/Scobleizer" into "https://twitter.com/fun" and I want change "https://mybank.com/asdfkasfdg/asl#asd.asdfawer3" into "https://mybank.com" locally. I'd be happy for you to know all my scripts (regular expressions) but I'd be much happier if I could choose whether you ever got into your server whose twitter pages I look at.
I’m scared about handing over even more information
EMPLOYEE
