redcalcium

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 spoofing 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).