The video that started this clippy campaign mentioned that. The message is that those sort of transgressions seem so minor compared to what companies bot only do, but get away with now
Clippy was hated at the time, but an annoying useless assistant that doesn't send anything to the Internet, let alone your personal data, seems like a dream now.
I think I get more of what you mean, now. I’m sure that there are technical issues to solve, like you said from the start, but that doesn’t mean they can’t be solved.
Realistically that single sent packet is going to get copied multiple times in order to re-route it just to the subscribers. We're not all one one big LAN.
What mechanism causes a single sent packet to get to all the subscribers (and only them)?
Assuming that we all have a static IP for simplicity, a sent packet needs to be routed to the subscriber IPs (via their ISPs). Where is that table stored? Is it sent with each packet so that it can be routed on the way? That would be a huge bloat of the packet size.
BTW, I do remember life before VCRs. Pre internet, I downloaded QWK packets from BBSs.
I get the appeal of removing communication from the hands of FB etc, but I don't see how switching to a broadcast system that increases unreliably would help. And I don't see how the broadcast would work on the Internet that we have.
So when a video is created it is immediately sent to subscribers?
In that case, for things to be sent once, it relies on the receivers always being online. That doesn't work if my laptop is closed at the time.
That's why I'm thinking that it needs online caching to work. Or everyone has a cloud server that handles sending and receiving while they're not online.
In fact, that starts to sound like everyone running their own personal lemmy-like instance, to which their friends subscribe.
And in that case it wouldn't matter if messages were sent more than once, each person's server would handle it.
I see I misunderstood how you mean this to work, that routing would handle sending data only to subscribers. I was imagining that it mean a simple LAN broadcast using a packet with the subnet bits all set (e.g. 192.168.255.255). I think that it's more analogous to a mailing list distribution, but for general data/streams?
But your earlier example of downloading the cat video still fails unless many people request the video at the same time (otherwise you're multicasting to one). What happens if I watch the video on my phone while out, then watch it again on my laptop at home? It will still need sending twice.
Wouldn't a more efficient approach just be to have something like ipfs with lots of local caching?
Yes, GPS works by measuring your distance from several GPS satellites (based on the timing of the signals they send). If a few distances are known, it narrows it down to a point (the satellite orbits are known so you know where they are at any time).
I've owned several stand-alone GPS receivers before phones started to include the feature.
You can download offline maps to phones so that you can navigate without any phone signal.
In my experience (some games in z80 and 68000 in the early 90s), version control wasn't considered until mid-90s sometime, and at first wasn't trusted. There were network backups, but I don't know if they had revisions.
Merging seemed like it couldn't possibly work well, so we would try to have separate ownership of different files. Although there would be only a handful of programmers on a team, so that was easy.
Prior to that, backup and versioning was manually handing a floppy or two to someone each week.
I just thought that as the ultimate authority on memes, he might take more of an interest.