@session do you have plans to be available on F-Droid?

Finance stuff 

@jbauer that's way too much money for a single person.

with U$800 we survived the whole month, family of 2 adults + 1 kid. full with proteins, carbs, vegetables & fruits (including 🥑s).

but if you don't cook and are used to buy 🥪 x U$17 or 🥗 x $15... then is OK, the. numbers are correct.

The Joel Test (still good advice 20 years later):

1. ✅
2. ✅
3. Nope. I don't have to. This is not C-land.
4. Sentry is love. We also have an APM too :)
5. Sometimes, we have something called `priorities`
6. Don't know that Pokémon
7. Yeap
8. Let's not talk about that. ❌
9. Goto 5. Prefer to use & contribute to OSS
10. That would be nice.✳
11. Sure, we have giant Gatekeepers to ensure nobody stole our jobs.
12. Goto 5.

@garritfra I use keepassXC to keep track of my PGP keys and subkeys. They are backed up within the KeepassXC backup and the filesystem backup done with restic.

@garritfra I consider the idea of "One X to rule them all" weak when involve security or protection. That's the reason, for example why I don't limit myself on how many virtual credit cards, passwords, email alias or SHH|PGP keys I do use as long as my management potential allows me (and use additional software just for that).

@garritfra TL;DR use as many keys a and subkeys as you can organize.
my take is to use a subkey per case: a new computer for example, the expiration should be required regardless the case.
But not only use a single key, but using a key for other cases, for example: use one key to sign commits, other to communication, and subkeys per computers. This way I can have a main key for git, and use one subkey in my personal computer and other subkey in the one for work, I add them on the git host.

@baldur I was witness of all the show with the license issues and yanked versions on the gem registry (rubygems) and it was exhausting. why? Since our main project would be potentially affected if we need to add or update any other piece of our ruby bundle (i.e security reasons), so I was:

- Reviewing Rails main discussion on GitHub and other channels
- Same for mimemagic
- check all possible technical alternatives
- work with legal about the license impact
- test all

what a week!

@jbauer sorry but I though we had this discussion settled:

pizza is a toast

I'm not the one doing the claim. is documented science:


No, don't worry. You are welcome.

@garritfra more than knowing for remote git host I was meant also the config of any git repo:

> Some Porcelain commands use this command to perform a light-weight garbage collection from time to time. The default value is 6700.

I'm not sure about Github, but sourcehut does run `git run` periodically:


@garritfra it's kind of relevant, tho. People think (as I did years ago) that commits live forever, but sometimes the git host may run `git gc` on their servers so its a bad idea to threat you (free?) git host as a backup.


> If you accidentally delete a branch, the commits will stay where they are

Unless you do git gc, then they are gone.

@jbauer I'm paying $15 /mo with 4GB, in USA. I can't even think how I was used to pay ~$25 to Google for basically nothing.

@garritfra I've tried evil mode in the past, but when using with org mode tends to be kind of not intuitive then I had to use evil-org. But found myself in a not ideal place so I force myself to not use vim when use emacs, it's kind of difficult at the beginning but I think is worthy.

@garritfra org mode to the rescue.
I use Orgzly on mobile and sync folders to use eMacs in desktop.
Full disclosure: I use vim for any other text manipulation because I love vim.

@jbauer the economic landscape is different, tech is different, companies are now invested on and supported by FOSS.

Fork is not a synonym of "Bad thing" or failing anymore.

@jbauer nowadays you can count multiple projects surviving forks. Backs in the 90s we had hundred of small projects with great potential walking into the oblivion because personal (and/or employer) interest get in the middle.

So, the passage was valid in the 90s - 2000s. It was very catastrophic toned because it was like that, maybe we should documented better. My memory is very bad trying to remember all the cases.

@jbauer the forks back them was not the GitHub button, no. Fork was the "I'm taking all my marbles and all my friends are coming with me", then the code was inconceivable, no way to port or patch once the leaders decide to leave the project and create their own derivative. There was multiple examples of projects splitting and eventually die.


@jbauer a the Cathedral has a way different world 20 years ago.
Back then the world was still on the war open source vs free software. We, the developers advocated to any of them were still pushing to bring more people into the projects: LAMP was a thing.
That passage was more a cautionary idea to avoid more fraction: if we fork, we will split effort; please create your fork only if this is absolutely necessary (like in abandoned projects)

Show older

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.