

Great link, and I fully agree. If it’s possible anyways.
Great link, and I fully agree. If it’s possible anyways.
Yes, but that shouldn’t explicitly opt in, and they shouldn’t marry that product to Gmail and Google Drive if they are going to push it to enable by default.
Again, it’s really insidious. They push it so aggressively I had to disable it on my personal device twice, and I can’t just not use Google Photos app because it’s tied to the camera itself on pixel phones.
The absolutely criminal dark patterns that they pull on people via Google photos auto backup is insane.
Just in my own orbit 2 of my friends wives, my parents, and my in-laws all wound up paying Google because they thought they had to or lose all their photos. We helped most of them disconnect the autobackup (that they didn’t even know was activated) and move it to offline safely. But that was the most downright evil shit Google has ever done and literally a fire in me for manipulating the elderly and less tech savvy so blatantly.
I responded above, but my point kind of was that it doesn’t work that way, but as we rethinking content delivery we should also rethinking hosting distribution. What I was saying is not a “well gee we should just do this…” type of suggestion, but more a extremely high level idea for server orchestration from a public private swarm that may or may not ever be feasible, but definitely doesn’t really exist today.
Imagine if it were somewhat akin to BitTorrent, only the user could voluntarily give remote control to the instance for orchestration management. The orchestration server toggles the nodes contents so that, lets say, 100% of them carry the most accessed data (hot content, <100gb), and the rest is sharded so they each carry 10% of the archived data, making each node require <1tb total. And the node client is given X number of pinned CPUs that can be used for additional server compute tasks to offload various queries.
See, I’m fully aware this doesn’t really exist on this form. But thinking of it like a Kubernetes cluster or a HA webclient it seems like it should be possible somehow to build this in a way where the client really only needs to install, and say yes to contribute. If we could cut it down to that level, then you can start serving the site like a P2P bittorrent swarm, and these power user clients can become nodes.
I realize that is not how the fediverse works. I’m not speaking about the content delivery as much as the sever orchestration.
That’s why I’m saying if somehow it could work that way, it would be one way to offset the compute and delivery burdens. But it is a very different paradigm from normal hosting. There would have to be some kind of swarmanagement layer that the main instance nodes controlled.
My point was only that, should such a proposal be feasible one day, if you lower the barriers you could have more resources.
I myself have no interest in hosting a full blown private instance of Lemmy or mastodon, but I would happily contribute 1tb of storage and a ton of idle compute to serving the content for my instance if I could. That’s where this thinking stemmed from. Many users like me could donate their “free” idle power and space. But currently it is not feasible.
Provided there is an “upper limit” on what scale we are talking, Ive often wondered, couldn’t private users also host a sharded copy of a server instance to offset load and bandwidth? Like Folding@Home, but for site support.
I realize this isn’t exactly feasible today for most infra, but if we’re trying to “solve” the problem, imagine if you were able to voluntarily, give up like 100gb HDD space and have your PC host 2-3% of an instance’s server load for a month or something. Or maybe just be a CDN node for the media and bandwidth heavy parts to ease server load, while the server code is on different machines.
This kind of distributed “load balancing” on private hardware may be a complete pipe dream today, but it think if might be the way federated services need to head. I can tell you if we could get it to be as simple as volunteers spinning up a docker, and dropping the generated wireguard key and their IP in a “federate” form to give the mini-node over to an instance, it would be a lot easier to support sites in this way.
Speaking for myself, I have enough bandwidth and space I could lend some compute and offset a small amount of traffic. But the full load of a popular instance would be more than my simple home setup is equipped for. If contributing hosting was as easy as contributing compute, it could have a chance to catch on.
No, the mistake was the complete corruption of US politics through naked graft and a FPTP voting system leading to extremist views being the only rallying opposition to reasonable stances.
The government needs to get purged of lobbyists and money.
Extremely cool. I would love this if it had some persistence. Letting users host workspaces could be great.
True, in a broad sense. I am speaking moreso to enshittification and the degradation of both experience and control.
If this was just “now everything has Siri, it’s private and it works 100x better than before” it would be amazing. That would be like cars vs horses. A change, but a perceived value and advantage.
But it’s not. Not right now anyways. Right now it’s like replacing a car with a pod that runs on direct wind. If there is any wind over say, 3mph it works, and steers 95% as well as existing cars. But 5% of the time it’s uncontrollable and the steering or brakes won’t respond. And when there is no wind over 3mph it just doesn’t work.
In this hypothetical, the product is a clear innovation, offers potential benefits long term in terms of emissions and fuel, but it doesn’t do the core task well, and sometimes it just fucks it up.
The television, cars, social media, all fulfilled a very real niche. But nearly everyone using AI, even those using it as a tool for coding (arguably its best use case) often don’t want to use it in search or in many of these other “forced” applications because of how unreliable it is. Hence why companies have tried (and failed at great expense) to replace their customer service teams with LLMs.
This push is much more top down.
Now drink your New Coke and Crystal Pepsi.
Tech companies don’t really give a damn what customers want anymore. They have decided this is the path of the future because it gives them the most control of your data, your purchasing habits and your online behavior. Since they control the back end, the software, the tech stack, the hardware, all of it, they just decided this is how it shall be. And frankly, there’s nothing you can do to resist it, aside from just eschewing using a phone at all. and divorcing yourself from all modern technology, which isn’t really reasonable for most people. That or legislation, but LOL United States.
I’m not worried about me. I can manage. But I had to intervene and make it a Project for my immediate family. Which is always unfun, because who wants to expose all their personal data that way, especially photos.
Crazy that Google just screwed over GrapheneOS like this.