Kushan

joined 2 years ago
[–] Kushan@beehaw.org 1 points 2 years ago

What are you even saying? What has nostalgia got to do with phones dropping removable batteries as a feature?

[–] Kushan@beehaw.org 0 points 2 years ago (2 children)

That's just not true. I've always been an android user and it's non-trivial to change the battery, hasn't been easy for years.

[–] Kushan@beehaw.org 2 points 2 years ago (14 children)

I'm all for this. The big argument against it is that it makes it harder to waterproof but I'll take that over a phone I have to replace every 18 months because the battery is shit.

[–] Kushan@beehaw.org 1 points 2 years ago

Big instances surfing up content from smaller instances is invariably going to cripple them unless larger instances start locally caching that content.

[–] Kushan@beehaw.org 4 points 2 years ago (1 children)

That's true if of any power plant though. It'll still be cheaper and safer (if it ever works).

[–] Kushan@beehaw.org 1 points 2 years ago* (last edited 2 years ago)

Ultimately, you need some way of routing the traffic to the correct place. Having all 3 services on the same domain, listening on the same ports is going to be a nightmare to manage because something needs to be clever enough to route the traffic to the right service without any information to go off of, other than maybe headers. Expensive firewalls can technically do this but it's not fun to configure and is really brittle.

As inferred, you could use the same domain but you'd have to configure your services to listen on a different port so you'll end up with something like https://domain.tld:8443 for Mastodon and https://domain.tld:8444 for lemmy.

You can technically use subfolders, i.e. domain.tld/mastodon and domain.tld/lemmy but you're not going to get the results you want and I can't say for sure that the software will deal with it nicely.

This is why we tend to use reverse proxies and configure them to route all traffic from subdomaina.domain.tld to one service and subdomainb.domain.tld to another service. It's just easier.

[–] Kushan@beehaw.org 1 points 2 years ago (1 children)

The main goal of these sites is link aggregation. It wouldn't be overly difficult for a federated server with its own /c/Technology community to see other posts from other communities linking to the same thing and combining the discussions into a single view.

The tricky part there is moderation, but even that's manageable by allowing moderators to remove content from a federated view within their own instance, it'll just be difficult when a small instance is dwarfed by a larger one.

[–] Kushan@beehaw.org 6 points 2 years ago (2 children)

This won't be possible. Best you can do is use something like waybackmachine to get a cached version of the page.

[–] Kushan@beehaw.org 0 points 2 years ago (1 children)

I know you've written off home assistant, but I'd strongly recommend reconsidering it. You can get something like Home Assistant yellow, which will serve as a hub for just about everything you could ever make smart. Home assistant is good for just giving you a dashboard of all your smart home stuff, you don't have to lean into the heavy automations or anything like that.

[–] Kushan@beehaw.org 9 points 2 years ago (6 children)

Freedom of speech is never freedom of consequence. And if that consequence is that nobody wants to listen to you, well that's on you.

[–] Kushan@beehaw.org 12 points 2 years ago (1 children)

What could be more important than being a shitty person?

[–] Kushan@beehaw.org 2 points 2 years ago

I think this is true but I think it has always been the case. The question is were there more bots than usual and I'm unconvinced there was.

view more: next ›