Preferably image the whole disk to some file on another disk so you can unfuck anything that gets fucked.
I’m Hunter Perrin. I’m a software engineer.
I wrote an email service: https://port87.com
I write free software: https://github.com/sciactive
Preferably image the whole disk to some file on another disk so you can unfuck anything that gets fucked.
Because it is. Who wants to pay $120 a month on streaming services you barely use?
Wow, you weren’t kidding.
I didn’t say basic. I said bad. HTTP 1 is a good protocol. ActivityPub is not. Read both the specs if you don’t believe me. I have.
There’s not a single point in HTTP 1 that I thought, “what the fuck does that mean?” There are several in ActivityPub. ActivityPub also has several areas that are ambiguous. Ambiguity is bad in a specification.
ActivityPub tries to support everything, and has no defined behavior for when a client doesn’t support whatever thing it just received.
It also uses JSON-LD, which isn’t necessarily bad, but defeats the purpose of JSON by making it too complicated to easily write by hand.
This is not easy to write, read, or parse, or build:
{
"@context": {
"name": "http://xmlns.com/foaf/0.1/name",
"homepage": {
"@id": "http://xmlns.com/foaf/0.1/workplaceHomepage",
"@type": "@id"
},
"Person": "http://xmlns.com/foaf/0.1/Person"
},
"@id": "https://me.example.com",
"@type": "Person",
"name": "John Smith",
"homepage": "https://www.example.com/"
}
Imho, ActivityPub is a bad protocol that tries to accomplish everything, and ends up being bad at all of it. The spec is also ambiguous in a lot of areas. And major implementations don’t always follow the spec. All in all, it’s a miracle the fediverse even works as well as it does.
I use Nephele through Nginx Proxy Manager.
Fedora, but I wouldn’t say I’m in love with it. It frustrates me the least. No Linux distro is perfect, but they’re all better than Windows.
That’s not who I wanted to see dead at 74.
This is amazing and I love it.
Ha! That’s awesome!
Ok, hear me out.
We find the users with the slowest internet and start sending them all the data. They don’t have to keep anything on disk. Then they send it all back and forth between each other. Any time a user makes a request, we just wait for one of the slow nodes to come across the data and send it out.
We use the slowest wires for all the storage. It’s fool proof.
Is it possible for me to get an account? How would I go about doing that?
Oh, that sounds really cool! Thank you for the explanation.
Based on my experience with how destructive a robot vacuum can be, there is 0% chance I would let a Tesla developed robot exist in my house.
What does it do?
Meanwhile, Tesla is showing off pretend robots to serve drinks to Elon stans. Don’t look behind the curtain.
Their sales figures seem to show that the majority of people don’t care. For my needs when I’m using my MacBook, I’m one of those people who don’t care. That’s probably because it’s not my main PC, so I use it for the things most people probably use it for (browsing, watching media, some light work).
The cheapest one I know of is about $8 a month, so it should be affordable, even on a tight budget.
You can buy a super cheap cloud VM and use a (self hosted) VPN so it can access your own PC and a reverse proxy to forward all incoming requests to your own PC behind your school’s network.
It’s arguable whether this would violate their policy, since you are technically hosting something, but not accessible on the internet from their IP. So if you wanna be safe, don’t do this, otherwise, that could help you get started.
This really depends on how you installed. Some partition types are easier to resize than others. The most important thing to do is backup everything important before you do anything.
Then boot to a live CD and you can use something like gparted or KDE Partition Manager to delete the NTFS partition and resize your Linux partition.
If you have a spare drive with enough space, it’s a great idea to take an image of the whole disk using Gnome Disks. That way if anything goes wrong, you can restore to the point you took the image.
Look up a tutorial on how to resize specifically your partition type (luks, ext4, btrfs, etc) with KDE PM or gparted. That should inform you of any caveats you should be aware of beforehand.