adkadskhj

I dabble in "life storage" and your comment made me think that some sort of executable shipped alongside backup locations to read the data, if in some deduplicated backup form, seems valuable.

Eg Camlistore/Perkeep had the premise of using JSON to store data. However some random person isn't going to write code to parse all that data, pull files out, etc. A lifeboat .exe might be interesting.

Though doing it in the most simple, least configurable, least breakable way seems.. necessary. Yea some baked in UI would be cool, but more moving parts means less likely to work.

`

How useful would that book (IPv6 Address Planning) be to someone not working specifically in networking/ops? I like developing applications and i manage, of course, my home network.

I'd love a book that gives me everything i need to know about IPv6. From justifications, to things to know when working with it, implementing it, using it in my local network, etc.

I don't perhaps need or care to learn it at a super low level, but i do want a complete understanding of it for my specific use cases. Applications and home networks, i imagine. For a novice in networks, to be clear.

Thoughts?

Hash Map/Set keys is a common one, for example.

So i agreed with you until:

> I'd certainly classify that as addictive behavior -- i.e. when a healthy young man is more interested in what's on his phone than he is in the attractive woman sitting across the table from him. Something is very wrong there.

We can definitely debate online life vs "in the flesh" - but it seems small minded to me for you to suggest someones preferences for experience are only the result of unhealthy addiction.

Many would argue your allowance of modern life, from TVs to cars to in city restaurants/etc. That you (or that person, i guess) didn't make a home cooked meal, or go experience nature together - to be an addiction to the modern and lacking in down to earth, honest and real connections.

Not that i agree with any of that of course. My point is that i think there is a perfectly valid possible course where someone prefers to experience their life in cities, in the woods, or in more virtual spaces.

The reality though, and where i agree with you - is that i don't think we actually have a virtual space that _isn't_ fueled entirely be addiction. Powered by highly financed and motivated teams of people.

I just think we need to be cognizant of alternative life styles. Just because commonly certain lifestyles result in unhealthy behavior doesn't inherently mean that lifestyle shouldn't be followed at all. If that was the case i think this argument should probably switch to avoiding much of modern life. As it is full of unhealthy habits and poor balances. We'll be living in the woods pretty soon if we can't recognize the possible healthy and balanced ways to live in the unhealthy-unbalanced minefield that is so many alternate forms of life.

I don't know much about Starlink, but isn't one point of Starlink that eventually it could even beat wired connections for distance latency? Ie it's a shorter and more direct trip to use Starlink to get from US West to US East, for example.

Though this is quite a ways out i imagine.

Best of all this idea works in current tech, and can get even better with future tech when Starlink starts going Satellite <-> Satellite, avoiding unnecessary land hops.

I'm interested in Starlink for all use cases, once they get more satellites up.

It's not a security risk. The security risk was removed, and the provided feature is an expensive workaround to avoid the security risk.

You're right, i'm sensitive to load times and exaggerated by approximately 4x.

I just (loosely) timed it, it took ~10-12s to open a backlog selected issue card _with cache_ from refresh. I used that example because it highlights the list i gave before.

1. The page loads, a bit slow in general.

2. The dom has loaded, so now backlog issues are loading.

3. The backlog issues are loaded, so now the selected component opens.

4. The selected issue component starts loading data.

5. Your data is now finally visible.

The ~10-12s is loosely evenly spread through the entire steps 1-5. This is on Jira Cloud, no "toaster NAS" unless you want to blame Jira Cloud for running a toaster, in which case i'd agree.

The problem in my mind isn't the servers. Opening the network tab, you see requests responding a bit slow, maybe 50-500ms, but not _terrible_. I'd like to see all requests below 300ms personally.

The problem is the UI design. Everything executes dynamically and sequentially. The URL indicates exactly what sort of page i want to see, but nothing is loaded until the JS loads, renders, makes a request for whatever data that individual component needs. Any sub-components to this then get rinse and repeat once they are actually loaded.

When you stack components on components on components that all need to sequentially load data a 1-2s load time starts to stack up, fast. And best of all, network requests are slowed down by how fast your DOM renders? Ugh.

I could agree with you from a UX-flow perspective, but the tech is so shoddy that i loathe it. Everything is a "web 2.0" monstrosity of load times and popin. Open the wrong link and it takes you 40 seconds for components to popin, pull data, render, move to the highlighted component, it to popin, pull data, render, and finally you get what you want.

The UX-flow might be good, not sure, but the tech is so bad it actually inhibits users. The use of independent components might be neat when loading a Jira card from Bitbucket pull requests (which works), but it makes loading Jira cards from... Jira, terrible. Imo.