BartyDeCanter

deleted by creator

deleted by creator

Happy to help! And yes, I have no idea what they’re talking about. If you don’t have snapshots (commits) you don’t have version control.

Let me know when you get your game going, I’d love to check it out. I’m working on a few myself.

The biggest silicon wafer is going to be your CPU or GPU. The motherboard is mostly fiberglass and copper.

I don’t have an exact number, but backing from California to a Hetzner box in Germany via Borg has always been surprisingly fast for the price and that it’s going halfway around the world. I want to say 25-30MB/s? I think people in the EU are reporting getting over 100MB/s.

If you just want one point of truth, the minimal version is to create a bare repo somewhere that you have ssh access to or your local machine. Then you can clone/pull/push from it.

A bare repo is a special kind of repo meant for exactly this, but can be a bit confusing at first. A normal repo contains all of your current working files and a special .git directory that holds all the files/blobs/history that git needs to work. A bare repo is just the .git as a top directory with bare=true in its config. So you can use it as a remote, but it never has a working set. They are usually named something like my_repo.git.

Edit:

Here’s a basic example for setting it all up in a fully local way:

mkdir ~/bares  
git init --bare ~/bares/my_repo.git  
mkdir ~/code  
git clone ~/bares/my_repo.git ~/code/my_repo  

And then you have remotes as your main source of truth in ~/bares and your working copies in ~/code. If you want to access from another machine that has ssh access to the first, you can do:

mkdir ~/code  
git clone user@host:~/bares/my_repo.git ~/code/my_repo  

And then use git pull/push to keep it all in sync. Don’t use Syncthing on a git repo, it eventually goes badly.

The number one thing to remember about git is that you don’t need a full hosting service around it for basic functionality. If it’s just you, a single local repo will probably serve you just fine, maybe use a bare repo on your main machine or a Pi-level device if you like as a remote/backup. Just git init or git init --bare and you’re good to go. GitHub, Codeberg, Forgejo, and all the others exist to serve multi-contributor and/or public project-level needs.

The number two thing to remember is that it is based around graph theory.

Remember that Git is a distributed VCS, so no git repo is dependent on a central server. Everything else about the project might be heavily dependent on GH, but any active developer is going to have a full copy of the code with history on their main workstation.

That being said, it highly depends on the project, but I’d put it into a few buckets.

1. Un/barely maintained projects - This is by far the largest number of repos, and many of them are used as dependencies by all sorts of projects. The truly unmaintained ones would vanish, and I bet most of the barely maintained ones would as well. The most important of these would probably be resurrected since their code will be sitting on all sorts of drives, but it will be a mess. Take a look at https://nesbitt.io/2026/05/08/weekend-at-bernies.html for an idea.
2. Small individually actively maintained projects - There are a lot of these and many of them could continue to be just fine, depending on how much of the full GH feature set they use. They would lose all the PRs, wiki spaces, discussions, issues, and maybe even the project page itself that are hosted on GH. For most projects it would be an annoyance to have lost all that, but if it’s a small enough project that one person is maintaining it, it’s probably small enough to pull over to something else reasonably easily depending on how all in they are on GH tools and their use of type 1repos. And a project with only one main contributor is unlikely to fragment.
3. Mid-sized active projects - Probably the hardest hit. A lot of these are all-in on the GH tools, particularly issues and CI. Losing that would hurt a lot because the project is big enough to really need those tools and uses them at a volume that they can’t just host on the leads laptop. These are also going to take a lot of work to set up the project infrastructure elsewhere. And this would probably be the sort of thing to push and simmering tensions to erupt, leading to fragmentation.
4. The big projects - Probably the least hardest hit. Most of these are just using GH as a push mirror. The core team probably has a functioning private communication and governance system, their own issue tracker (even if it pulls from GH), documentation, and public discussion groups. Most of these run their own private CI. And they are the ones most likely for another host to step in and offer to help.

So the little stuff? Probably going to be annoyed or not care a lot. The big stuff? Same thing. But that middle group would be hurt.

1. CI runners - GH offers free CI runners for a variety of OSs. I can automatically test my code on Linux/Mac/Windows for free on GH. No one else offers that because it is very expensive. You need windows licenses and Apple hardware. And Codeberg only offers it on Linux after a back and forth discussion. Plus, while simple GH CI Actions move to Forgejo Actions pretty easily, more complex ones require a complete rewrite.
2. Better issue tracking - FJ’s issue tracking is pretty good, and perfetcly fine for small projects, but GH’s is better.
3. Better CLI - fj is decent and improving, but gh is better
4. Better project pages - Codeberg Pages is decent and improving, but GH Pages are better.
5. Lots of other small things - Codeberg is decent and improving, GH is better.

For most people, myself included, the only thing that really matters are the CI runners. But that is also the one thing that costs the most to support.

Two main reasons: history and network effects.

GitHub was an independent company for a decade that provided a vastly superior service to what it replaced, primarily SourceForge. And it was free for FOSS projects, while charging for closed ones.

The improvements paid for by the closed source customers trickled out to everyone. So, it became the best place for FOSS developers, large and small. And as more people moved to GH, the more reason there was to move to it.

Of course, it was constantly bleeding money and eventually had to do something. That ended up being selling to MS.

There was a lot of trepidation about this, but for the first few years they not only kept their promise about supporting FOSS, but actually made it better by allowing small private repos to get many of the services that were previously gated for open FOSS or paid repos.

And the alternatives were stil not as good, and just as importantly didn’t have the user networking that GH does.

Now, some FOSS people are starting to look elsewhere, Codeberg, self-hosted Forgejo, and others. They have come a long way and are nearing feature parity, particularly for smallish projects. But the network effects of discovery and reputation are strong, and GH still provides a few more useful features.

I’ve moved my private repos to self hosted Forgejo, but my public ones are still on GH as push mirrors. I’m not ready to give up the discoverability and Mac/Windows CI runners that I can get from GH for free. I hope to be able to some day, but not yet.

Updated!

I’m not certain, but I wish you the best of luck in finding it. 😅

You’re really going to have to define “plastics” to get a good answer to that.

Plastic in the material science definition means any material that can be permanently deformed without breaking. So, lots of materials created by living things meet that definition.

If you mean thermoplastics, which is the more common colloquial definition, well, several things meet that definition as well, including horn and many other types of keratin.

If you mean polymerized hydrocarbon based thermoplastics, which is what you probably are thinking of, chitin is the most common answer.

Bisexual - You’re over 35

Pansexual - You’re under 35

Omnisexual - You’ve spent way more time thinking about your sexuality than getting laid

Demisexual - You’re way more queer than you’re ready to admit.

Sapiosexual - You’re a straight guy trying to impress the cute barista by seeming cool and intellectual. You are failing. Or you are a woman on a dating app trying to stop the endless flood of low-effort “sup” introductions. You are also failing.

Edit: Forgot one!

Heteroflexible - Willing to touch someone of the same gender sorta sexually for an audience if you think it means you’ll get a threesome later.

While it seems like everyone here hates it, I’ve been looking for a minimal phone for when my current one dies. This seems to hit the exact sweet spot of functionality I want vs what I don’t want. As for the price, well, I’m spending at least that much on my next phone anyway so it seems fine by me.

And I have a huge nostalgia for flip phones and transparent electronics. So yeah, signed up to preorder.

1. Follow the Trash Guides exactly for your arr stack setup. Don’t try to get fancy or take a shortcut. If you’ve already set up something differently, just redo it. Better to spend a little time now than a lot later.
2. Set up Tailscale. The free tier is probably fine for you, but if you’re extra paranoid you can run your own Headscale server instead.
3. Take notes. What you set up, what your docker files and configs are, and add any troubleshooting info as it comes up.
4. Use a password manager and keep everything in it.

Sure, if that’s what you want to do. Though, you’ll probably find less references and expertise here. There is a reason that even Microsoft runs Linux on most of its own servers.

And if you don’t have any friends or a bank, put it in a double ziplock, then drop it in a Tupperware of water and freeze it.

I run Debian on a Thinkpad x130e. systemd bloat is basically a myth, and of all the things to work on reducing system resource use, it’s not quite last in line, but pretty close to it. In general systemd has been a complete, utter, unmitigated success.

Setup a PiHole and add them to the blocklist. Then make the PiHole password stupid long and write it down. Then take the paper, put it in a safe, and put it in the highest shelf in the back of your closet. Recurse safes and passwords as much as needed.