I feel like there's a lot of knowledge or information that we're "leaving on the plate". For instance, the sites we visit, the files we edit, the branches and PRs we create, etc etc. All of that is related, but it feels like that context is being lost or discarded. An example might be: I have to include new AWS resources in a deployment, so I look up information about them, find examples and read about potential prob…
Show HN: An extension to track your Wikipedia adventures
31–40 of 73 posts
Re: Show HN: An extension to track your Wikipedia adventures
#32I feel like there's a lot of knowledge or information that we're "leaving on the plate". For instance, the sites we visit, the files we edit, the branches and PRs we create, etc etc. All of that is related, but it feels like that context is being lost or discarded. An example might be: I have to include new AWS resources in a deployment, so I look up information about them, find examples and read about potential prob…
Working on something like that, but there’s still a good amount of work to do
Re: Show HN: An extension to track your Wikipedia adventures
#33It seems likely that the extension could be customized to any Mediawiki instance? As an admin I'd love to be able to use it elsewhere. This looks like it could be a great tool working with test users on stuff like information architecture, to see the path of how they found information. (I know there are better tools for that, but something that focuses tightly on wiki interactions would be useful to me.)
Re: Show HN: An extension to track your Wikipedia adventures
#34Re: Show HN: An extension to track your Wikipedia adventures
#35A few years ago I did a university project where we looked into (internet) research and how information discovery and gathering could be improved. (https://www.kaimagnus.de/projects/halo)
There we had the concept of a similar looking tree. Users could then come back to their exploration and take notes, prioritize and sort.
It was only a concept back then, so it’s nice to see it in action.
Re: Show HN: An extension to track your Wikipedia adventures
#36I feel like there's a lot of knowledge or information that we're "leaving on the plate". For instance, the sites we visit, the files we edit, the branches and PRs we create, etc etc. All of that is related, but it feels like that context is being lost or discarded. An example might be: I have to include new AWS resources in a deployment, so I look up information about them, find examples and read about potential prob…
I've had similar thoughts but over time you'd just end up with a private copy of the internet. You'll still have to search for the information anyway, so I'm not sure what the benefit is. Searching your knowledge base for "the thing I did yesterday" vs "how to sync Azure to AD" seems basically equivalent to me. You're just creating yet another thing to search.
Seeing relevant bookmarks when I'm viewing a specific note in my database could be useful though. And finding pull requests related to a subject might also be useful.
So the idea would be to reduce the number of searches performed by the human. Automate and enhance rather than dump and forget.
Re: Show HN: An extension to track your Wikipedia adventures
#37I feel like there's a lot of knowledge or information that we're "leaving on the plate". For instance, the sites we visit, the files we edit, the branches and PRs we create, etc etc. All of that is related, but it feels like that context is being lost or discarded. An example might be: I have to include new AWS resources in a deployment, so I look up information about them, find examples and read about potential prob…
Re: Show HN: An extension to track your Wikipedia adventures
#38I feel like there's a lot of knowledge or information that we're "leaving on the plate". For instance, the sites we visit, the files we edit, the branches and PRs we create, etc etc. All of that is related, but it feels like that context is being lost or discarded. An example might be: I have to include new AWS resources in a deployment, so I look up information about them, find examples and read about potential prob…
Re: Show HN: An extension to track your Wikipedia adventures
#39Re: Show HN: An extension to track your Wikipedia adventures
#40Have you tried out a tangled-tree visualization? [1] I've found it to be super useful when visualizing these sorts of relationships in a compact way, and it naturally sorts the data topologically. [1] https://observablehq.com/@nitaku/tangled-tree-visualization-...
> A tree with multiple inheritance (sometimes called tangled tree) cannot be represented by using a classic tree visualization. It is technically a directed acyclic graph (DAG) with one (or more) nodes identified as root.
What is the difference between a DAG and a tangled tree? Isn't any DAG a tangled tree? I don't see immediately why a new definition is required.