K. Ryabitsev 🍁
@monsieuricon
Moderator
Posts
2041Following
230Followers
2517This account is for Linux/Kernel/FOSS topics in general: #linux, #kernel, #foss, #git, #sysadmin, #infrastructure.
For my personal account, please follow @monsieuricon@castoranxieux.ca.
Montréal, Québec, Canada 🇨🇦🇺🇦
K. Ryabitsev 🍁
monsieuricon
@brauner There's actually code in b4 that converts GH PRs into an mbox file that you can git-am. It's not well documented because I don't think anyone's ever used it, but if you're interested in trying it out, I'm happy to provide more info.
0
0
1
K. Ryabitsev 🍁
monsieuricon
FYI, I'm working with @tbr@society.oftrolls.com to figure things out. Standby. :)
1
0
2
K. Ryabitsev 🍁
monsieuricon
If you're wondering why you can't follow society.oftrolls.com accounts from social.k.o, it's because we can't actually talk to them -- we can only do TLS1.2 maximum due to still being on RHEL7 for a little while longer, and they only allow TLS1.3.
3
1
4
K. Ryabitsev 🍁
monsieuricon
@captainepoch neomutt is awesome and has spiffy integration with powerline!
0
0
0
K. Ryabitsev 🍁
monsieuricon
Do you like Soviet Synthwave?
Show content
Because I have some awesome Soviet Synthwave for you.
https://www.youtube.com/watch?v=X-4dtCxd-2U&list=OLAK5uy_nLbqzK3bX1lqRRNpgHiiaS0zimM01bOy4
https://www.youtube.com/watch?v=X-4dtCxd-2U&list=OLAK5uy_nLbqzK3bX1lqRRNpgHiiaS0zimM01bOy4
0
1
0
K. Ryabitsev 🍁
monsieuricon
@jbowen I would say "the Dude Abides" — it was certainly a bumpy ride for it over the past ten years as it was basically kept on minimal life support by Yahoo. However, it's still alive and hopefully SmugMug folks manage to inject second life into it by making it speak Fediverse.
0
0
0
K. Ryabitsev 🍁
monsieuricon
@vbabka it should be entirely possible. E.g. this page is statically rendered already: https://social.kernel.org/notice/AQ4reII29sqhY7P57I
When we archive off the thread, we'll just set up a redirect to its public-inbox threaded view (e.g. with a message-id notice-AQ4reII29sqhY7P57I@social.kernel.org).
At least that's how it looks in my head.
When we archive off the thread, we'll just set up a redirect to its public-inbox threaded view (e.g. with a message-id notice-AQ4reII29sqhY7P57I@social.kernel.org).
At least that's how it looks in my head.
0
0
2
K. Ryabitsev 🍁
monsieuricon
My plan is to migrate my personal instance (castoranxieux.ca) to Akkoma some time this week. Should be fun, and I'm liking the concept of bubbles.
I know that Pleroma upstream has had... interesting times in the past few months, but I didn't want to go with a fork for social.k.o -- at least not yet. We'll see how Akkoma and re:Based are doing over the next few months, and how the upstream is doing. Switching my personal instance to Akkoma seems to be the right way go to in terms of kicking tires.
I know that Pleroma upstream has had... interesting times in the past few months, but I didn't want to go with a fork for social.k.o -- at least not yet. We'll see how Akkoma and re:Based are doing over the next few months, and how the upstream is doing. Switching my personal instance to Akkoma seems to be the right way go to in terms of kicking tires.
0
1
4
K. Ryabitsev 🍁
monsieuricon
@sugar Are you sure it's wise? If they could feel pain, one has to assume they would be able to feel vengeance.
0
0
2
K. Ryabitsev 🍁
monsieuricon
@ihabunek Do you really want to eat the soup that they are *paying* you to take? :)
0
0
0
K. Ryabitsev 🍁
monsieuricon
I'm considering an archiving scheme for social.kernel.org that would automatically add all public statuses to a public-inbox archive -- not right away, but maybe after a month or so. This should allow us to remove them from the database while still keeping them publicly accessible. From what I've read elsewhere, pleroma's database backend organization is not great, so after a while they start to experience database performance problems. Removing old entries should allow us to avoid this fate while still preserving the conversation record.
1
1
3
K. Ryabitsev 🍁
monsieuricon
@drewdevault I should try wrapping my servers in a blanket, thank you for the suggestion! I wonder if they have to be wool blankets, or will polyester ones do just fine. ;)
0
0
0
K. Ryabitsev 🍁
monsieuricon
@jan @kernellogger I try not to suggest solutions that generate more questions for me down the line. ;)
0
0
3
K. Ryabitsev 🍁
monsieuricon
@vegard @legoktm I just wish that notes weren't so fragile. They are good for annotating commits that were merged and are unlikely to change, but WIP branches that get rebased a lot are always in danger of losing the notes if the branch isn't properly configured to copy them post-rebase. There are other problems, too: they live in a separate ref, so developers need to remember to push them separately from their code branches; they can result in merge conflicts in shared repos; they scale non-linearly because they are effectively just a bunch of files.
So, in general, people who dislike git-notes generally have good reasons for that — which doesn't mean that they aren't a useful auxiliary tool, of course.
So, in general, people who dislike git-notes generally have good reasons for that — which doesn't mean that they aren't a useful auxiliary tool, of course.
0
0
1
K. Ryabitsev 🍁
monsieuricon
@nathanchance it's not really "ansible or terraform" as much as "ansible and terraform". They generally swerve adjacent tasks — get the VM and all the networking bits deployed with TF and then configure the OS and apps with Ansible.
0
0
2
K. Ryabitsev 🍁
monsieuricon
@captainepoch I'll follow up via email for sure, I was just wondering if I missed an existing way of doing it. Thanks!
1
0
0