SJ0

Steve Jobs died in 2011, the headphone jack disappeared from the iPhone 7 in 2016.

The person who decided a headphone jack is superfluous should be found, tarred, feathered, and left naked and alone deep in the alaskan wilderness covered in pigs blood for the wildlife to enjoy.

One big difference between the json requests and a user callling for the site directly is your instance pulls all the data all the time, whereas a user only pulls the data they use themselves.

I think it depends a lot on the federated service.

For mastodon, you follow individual users, so if there's a million users or ten million or a hundred million, their instances will only be contacting other intances they're federating with so it's quite scalable.

For Lemmy, you follow communities, so every server pulls all the posts and comments the common community. This means that for an instance like lemmy.world hosting lots of different big communities, every new server hammers the one central instance.

A strategy for improving the situation I think would be to spread the load. Instead of everyone piling into megacommunities, if people spread out into smaller more tight knit communities over many different instances. Of course, this isn't really compatible with the purpose of having communities like that.

It does seem to suggest that ActivityPub isn't necessarily the most appropriate protocol for this purpose, even though it's what was used because it's the de facto standard on the fediverse.

Depends on the specific instance. Some services run where they are natively accessible through tor, but most don't.

Just remember that ActivityPub is a sharing protocol, and individual admins are fully capable of seeing everything. There is no end to end encryption, everything is stored in plain text.

In my country, you don't get free upgrades anymore. You have to put them on a plan that adds a bunch to your phone bill every month. I know I haven't even considered replacing a perfectly good phone after that (which is probably what things should be like anyway, but still....)

You don't need a local DNS server to set up https, but you do need a domain name. If it's something that you wanted to pick up, you can buy them at a number of different places and you'd have to set up a mechanism to make sure the IP address referenced is the correct one. You can either do that by having a static IP address or by setting up some form of dynamic DNS. Then you can use letsencrypt to set up https.

Okay so here's I think the core of your question though: the only way that someone outside of your network can access your nextcloud is if you have set up the server to be accessible from the outside world. You would have to go into your router and forward Port 80 to the local IP address of your nextcloud server. If you don't do that, then it will only be accessible to the people inside of your network. Rotors do something called Network address translation which lets many devices on your local network connect to the internet despite only having one external IP address. If you're accessing the server using a 192.168 address or a 10.x.x.x address you are already using the internal IP address and not your external Internet IP address so you're likely safe.

One neat trick because remembering IP addresses is a pain in the butt is the hosts file. On windows it's in c:\windows\system32\drivers\etc\hosts and you can set a hostname to immediately resolve to a certain IP address. It's particularly nice because it's free, it's fast, and once you set it you can forget it.

My websites are on the public internet, but I use the host to file to point them at the internal IP address because that way I can directly connect to my servers even when the internet is down.

I'm not entirely sure, but I'm in a very Northern climate and this variety is specifically capable of dealing with extremely low winter temperatures, like -30C. That's been one of the goals I have for this year, is to have my plants live until next year.

Almost guaranteed that's what it is.

A modern serial attached SCSI drive. It's been a standard on servers for years.

It's also sort of an egocentric action -- "I don't like some users over there, so nobody should be allowed to interact with any of the users over there"

The threadiverse will continue to grow, and there's going to be people of all kinds joining up. We need to figure out how to coexist as individuals because you can't just have every instance defederate with everyone else because there might be a bad user.

So there's 2 things, I think.

1. Does your bios allow you to boot from SD card? If so, then you can boot from the SD card and so you can install software onto the SD card directly.

2. If you can't boot off of the SD card, then perhaps you can install all the software on the SD card and then install a boot manager on the main drive. In this way, you boot off the main drive, then let the boot manager deal with loading the software.

You might be disappointed by the performance of software running off an SD card, mind you.