If you add support for kbin, you'll probably going to add support for kbin's microblogging feature. If you added support for kbin's microblogging, might as well add mastodon support. Heck, might as well add pixelfed support to the mix, why not? Voila, now you have a super federated app.
It's not 3rd party app developers fault that kbin didn't have any stable api yet. Now that they fast track the api development, I think we can expect more 3rd party apps coming soon.
Also consider the possibility when the other, more popular projects got enshittified. Now the fleeing users have an option to switch to your project. It actually happened on one of my side project. I made it because I want to try building my own version of X. It got ~2000 users, but later down the road, X got sold to a new shitty owner that waste no time to enshittify it, and my side project suddenly grow to 20,000 users overnight.
uBlock Origin is already less effective when running in Chrome than in Firefox. For example, it can't detect CNAME cloaking on Chrome, while it can do that in Firefox. When Chrome finally enforce manifest V3, uBlock Origin will be even more neutered in chrome due to limited number of blocking rules.
I just checked my AMD box and tailscale there can consume ~15% of cpu time when the tunnel is under active use. When it's not used it's ~1.5%. But it's a low power old AMD cpu though (AMD G-T56N), so I'm not use if it compares to Ryzen 5. On my intel machine, it's ~5% when under active use, and idle at ~0.5%.
I got curious so I start digging into how mastodon do it. It's more like a hack, really. Mastodon uses WebFinger to resolve user account, so when you change domain, you can leave the old domain up so your federated servers can still resolve your users and realized the domain has been changed and update their federation data. But it turns out you can't exactly retire the old domain either because it's still tied to user account internally. So if you lose control of your old domain, you're probably as screwed as fmhy.ml.
On my machine it's consuming about 0.5% - 1.0% of cpu time, which is higher than zerotier in the same machine (almost zero).
Tailscale does a lot more things than just tunneling though. For example, on default installation it'll catch all outbound dns request on the machine and route them through MagicDNS (100.100.100.100).
Whelp, nextcloud isn't known for being fast. I don't have hundreds of thousands of emails yet so I can't comment on that, but one thing for sure is as you put more and more data on it, you'll have to add more CPU and RAM to it or it'll getting more and more sluggish.
I haven't noticed any performance issue so far. I think they use wasm which help with speed. Too bad it's not open source, but the fact it's developed by a single guy working on it full time is actually very interesting, considering the webapp is actually work better than some apps developed by bigger teams. It can even edit PDF and gif!
I think using container instead of VM should be better for maximizing resource utilization in a raspberry pi. Instead of partitioning your tiny 8gb RAM into 3-4 VMs with even tinier RAM each, you can run a dozen of containers and probably still have some free RAM.
I always look for excuses to get more servers, so if you ask me, I'd say yes, get that new server. There's no such thing as having too much servers since there are so many things I want to self-host.
I also regularly tear down my servers and see how fast I can set it up again. Keep my deployment scripts up to date.
It has happened before with the .ly domains about a year before the US invasion of Libya. Tech companies were scrambling to find a solution back then. Presumably they struck a backroom deal with the Syrian government.
If you add support for kbin, you'll probably going to add support for kbin's microblogging feature. If you added support for kbin's microblogging, might as well add mastodon support. Heck, might as well add pixelfed support to the mix, why not? Voila, now you have a super federated app.
It's not 3rd party app developers fault that kbin didn't have any stable api yet. Now that they fast track the api development, I think we can expect more 3rd party apps coming soon.
Revolt!? That dog is fucking embrace it!
Who cares if it already exists, just make it.
Also consider the possibility when the other, more popular projects got enshittified. Now the fleeing users have an option to switch to your project. It actually happened on one of my side project. I made it because I want to try building my own version of X. It got ~2000 users, but later down the road, X got sold to a new shitty owner that waste no time to enshittify it, and my side project suddenly grow to 20,000 users overnight.
Investors: shut up and take my money!
As the CEO of a company that run several major social networks, he know the importance of privacy and choose to use a virtual background.
uBlock Origin is already less effective when running in Chrome than in Firefox. For example, it can't detect CNAME cloaking on Chrome, while it can do that in Firefox. When Chrome finally enforce manifest V3, uBlock Origin will be even more neutered in chrome due to limited number of blocking rules.
I just checked my AMD box and tailscale there can consume ~15% of cpu time when the tunnel is under active use. When it's not used it's ~1.5%. But it's a low power old AMD cpu though (AMD G-T56N), so I'm not use if it compares to Ryzen 5. On my intel machine, it's ~5% when under active use, and idle at ~0.5%.
I got curious so I start digging into how mastodon do it. It's more like a hack, really. Mastodon uses WebFinger to resolve user account, so when you change domain, you can leave the old domain up so your federated servers can still resolve your users and realized the domain has been changed and update their federation data. But it turns out you can't exactly retire the old domain either because it's still tied to user account internally. So if you lose control of your old domain, you're probably as screwed as fmhy.ml.
I'd like to think FMHY was true to their name and didn't pay for the domain.
.ee is owned by Estonia. Just pray Estonia wouldn't do the same shenanigan and cause your instance to go down.
On my machine it's consuming about 0.5% - 1.0% of cpu time, which is higher than zerotier in the same machine (almost zero).
Tailscale does a lot more things than just tunneling though. For example, on default installation it'll catch all outbound dns request on the machine and route them through MagicDNS (100.100.100.100).
Who know deleting a power user account could DDOS the entire federation?
Whelp, nextcloud isn't known for being fast. I don't have hundreds of thousands of emails yet so I can't comment on that, but one thing for sure is as you put more and more data on it, you'll have to add more CPU and RAM to it or it'll getting more and more sluggish.
I haven't noticed any performance issue so far. I think they use wasm which help with speed. Too bad it's not open source, but the fact it's developed by a single guy working on it full time is actually very interesting, considering the webapp is actually work better than some apps developed by bigger teams. It can even edit PDF and gif!
I think using container instead of VM should be better for maximizing resource utilization in a raspberry pi. Instead of partitioning your tiny 8gb RAM into 3-4 VMs with even tinier RAM each, you can run a dozen of containers and probably still have some free RAM.
Believe it or not, NextCloud. It actually can work as an email client. And it can sync calendars, contacts and todo list too.
At least for Lemmy, you can "force" it to sync a particular post or comment by pasting the url into your instance's search bar.
I always look for excuses to get more servers, so if you ask me, I'd say yes, get that new server. There's no such thing as having too much servers since there are so many things I want to self-host.
I also regularly tear down my servers and see how fast I can set it up again. Keep my deployment scripts up to date.
It has happened before with the .ly domains about a year before the US invasion of Libya. Tech companies were scrambling to find a solution back then. Presumably they struck a backroom deal with the Syrian government.