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.
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!
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%.
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.
Believe it or not, NextCloud. It actually can work as an email client. And it can sync calendars, contacts and todo list too.
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.
photopea.com is actually pretty great, much easier to use than gimp with similar (or even better) feature set.
Heck, I haven’t been able to get a comment deleted in ALL instances so far. Instances that don’t directly federate with my instance doesn’t seem to process deletion reliably.
Interestingly, edits seem to propagate more reliably. So if you want to make sure your comment deleted, just edit it to replace the content before actually deleting them.
Here is the documentation, pretty bare though: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/oauth2.html
I use keycloak. Pretty steep learning curve, but once properly set up, it can do pretty much anything.
But if you’re in a pinch, NextCloud can act as an OIDC auth provider out of the box.
Does ssh works? If yes, you can use autossh
to create persistent ssh tunnel to your VPS.
Lemdro.id seems to be all about android stuff.
Looks like they won’t publish a timelapse video after it’s all over like last year.
Red Hats / IBM did this to themselves when they decided to kill CentOS. There are rumors that said Red Hat/ IBM was pissed that Rocky won a NASA contract, so they decided to pull the rug, stop releasing RHEL source code to non paying customers, and add clauses to their ToS to terminate contract with customers that redistribute the source code.
But you know what, if Red Hat/ IBM didn’t kill CentOS, Rocky wouldn’t exist. That NASA contract would’ve gone to Red Hat. Oracle Linux wouldn’t be as popular (because people would use CentOS), and SuSE wouldn’t provide free support to Rocky and Alma. Red Hat would still be the open source darling of the linux community, and IBM would still made a buttload of money.
Instead, they got greedy and think that all those CentOS downloads equals to lost RHEL sales (classic piracy equals to lost sales fallacy) and decided to kill CentOS to increase short term profits, which sprung Rocky and Alma (which truly eating their lunch because they also offer enterprise support). Red Hat didn’t learn it’s lesson and double down, and now have burned all of it’s remaining good reputation in the open source community.
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.