51–60 of 73 posts
That's cool. I do find it ironic though that wikipedia is one of the major sites with the least amount of user tracking, and then users decide to implement the tracking themselves.
That is funny, though this is more tracking-by-users than tracking-of-users
Have 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-...
Very cool! One small point of pedantry: > 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.
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…
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.
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…
I like these pieces of my digital footprint to not be connected. There is no need to track everything.
Earlier quoted context omitted.
This is tracking the user's trajectory through the site, necessarily a tree, not the network structure of W itself.
How is the user journey through the site necessarily a tree? What prevents the user to create loops through their journey?
Earlier quoted context omitted.
I like these pieces of my digital footprint to not be connected. There is no need to track everything.
Do you not want them connected, or do you not want the connections shared and potentially used against you?
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…
If it's not...then there's really nothing "left" on the table — if ever turns out to be valuable, you'll probably come across it again, when needed.
I constantly get a similar feeling. I'm speeding around from task to task, just grasping enough to get the current task done so I can get to the next one and the next one...
And somehow this is value-creating? Apparently it is, but it seems almost accidental, at that rate.
I'd rather slow down and appreciate the value as it moves through me, into whatever I'm doing.
I usually get more from the process, at the same time.
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…
My thoughts on this are to slow down and document and explore that knowledge and information. If it is really valuable, the "loss" in efficiency from slowing down will be offset by the gain in skill/utility from really grokking the stuff. If it's not...then there's really nothing "left" on the table — if ever turns out to be valuable, you'll probably come across it again, when needed. I constantly get a similar feeli…
Reminds me of a floating point number. The bigger or smaller they get, the less accurate they become.
If you're chunking on a ton of data and tasks, you're getting less out of it. At a certain point, none of it even seems to enter your brain at all.
Earlier quoted context omitted.
My thoughts on this are to slow down and document and explore that knowledge and information. If it is really valuable, the "loss" in efficiency from slowing down will be offset by the gain in skill/utility from really grokking the stuff. If it's not...then there's really nothing "left" on the table — if ever turns out to be valuable, you'll probably come across it again, when needed. I constantly get a similar feeli…
It's like...if "less is more," then "more is less." Reminds me of a floating point number. The bigger or smaller they get, the less accurate they become. If you're chunking on a ton of data and tasks, you're getting less out of it. At a certain point, none of it even seems to enter your brain at all.