#b4 — Public Fediverse posts

B4 - инструмент обхода разноуровневых DPI на Go с удобной веб-мордой. Работает на уровне ядра Linux через NFQUEUE - перехватывает сетевые пакеты и применяет к ним техники обхода.

https://habr.com/ru/articles/1055056/

#b4 #proxy #go

B4 - инструмент обхода разноуровневых DPI на Go с удобной веб-мордой. Работает на уровне ядра Linux через NFQUEUE - перехватывает сетевые пакеты и применяет к ним техники обхода.

https://habr.com/ru/articles/1055056/

#b4 #proxy #go

B4 — сетевой мультитул по обходу блокировок

С момента написания первой статьи о B4 прошло полгода. Казалось бы, не очень много времени, но софтина получила ну очень большое количество фич, о которых хочется рассказать подробно. Не буду скрывать: хабраэффект сделал своё дело, и благодаря большому интересу после первой статьи очень многие не разочаровались в отсутствии какого-то функционала, а активно помогали - коммуникацией, запросами, тестированием, - благодаря чему все эти фичи в B4 и появились. В итоге на сегодняшний день B4 - это не инструмент для обхода блокировок (коим и задумывался изначально), а полноценный сетевой мультитул с гибкой и продвинутой маршрутизацией таргетированного трафика.

https://habr.com/ru/articles/1055056/

#golang #netfilter #nfqueue #b4 #zapret #dpi #rkn #tspu #packet #sni

Our Table has just started playing B4 - The Lost City (Goodman's 5e version).
Our GM has *finally* got around to putting his long-awaited Mystara campaign together, and we're using this is a starting point.
I'm playing an Elf Wizard out of Glantri.
So far, we've entered the Pyramid, and encountered a swarm of Giant Fire Beetles!
Will our Heroes emerge victorious, or be defeated by the 1st Foes?
Stay tuned...

#rpg #Dnd #B4 #ttrpg

Our Table has just started playing B4 - The Lost City (Goodman's 5e version).
Our GM has *finally* got around to putting his long-awaited Mystara campaign together, and we're using this is a starting point.
I'm playing an Elf Wizard out of Glantri.
So far, we've entered the Pyramid, and encountered a swarm of Giant Fire Beetles!
Will our Heroes emerge victorious, or be defeated by the 1st Foes?
Stay tuned...

#rpg #Dnd #B4 #ttrpg

sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

#kernel #maintainer #b4 #mainline #patchwork #foss

sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs

I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility

the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it

#kernel #maintainer #b4 #mainline #patchwork #foss

Getting more comfy with the email patch workflow again.

I also wrote some utilities for applying patchsets with #notmuch and #b4 -> https://codeberg.org/matthiasbeyer/notmuch-scripts

Getting more comfy with the email patch workflow again.

I also wrote some utilities for applying patchsets with #notmuch and #b4 -> https://codeberg.org/matthiasbeyer/notmuch-scripts

#b4 seems to be on a really good path to be _the_ tool you want to have for reviewing in an email-patch based workflow. I think it looks awesome!

#b4 seems to be on a really good path to be _the_ tool you want to have for reviewing in an email-patch based workflow. I think it looks awesome!

B4 — обход DPI с веб-интерфейсом

B4 - инструмент обхода DPI на Go с веб-интерфейсом. Хотелось сделать инструмент, который можно поставить на роутер или любой другой linux-девайс, открыть в браузере и получить работающий результат без возни с десятками аргументов командной строки.

https://habr.com/ru/articles/982498/

#go #dpi #dpiсистемы #typescript #nfqueue #netfilter #b4

Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

I mean, I don't care for your 5 person project, do what you want.

But for large projects, that really is the only way to develop that truly scales.

Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

#git #github #shithub #gitlab #shitlab

Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

I mean, I don't care for your 5 person project, do what you want.

But for large projects, that really is the only way to develop that truly scales.

Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

#git #github #shithub #gitlab #shitlab

I want to process 4714 message-id's to collect some patch stats for the last year. I could collect with #b4 which uses the #lore archive but I wonder does it cache or will I end up with lots of redundant mbx files? Worse still would I just be hammering an overloaded server? I guess I should check out the #PublicInbox docs.

I want to process 4714 message-id's to collect some patch stats for the last year. I could collect with #b4 which uses the #lore archive but I wonder does it cache or will I end up with lots of redundant mbx files? Worse still would I just be hammering an overloaded server? I guess I should check out the #PublicInbox docs.

#b4 #linux Having gotten through using "b4" once now, I generally like it. It pulls together all the things needed for sending a patch to one of the Linux development groups, making it much more difficult to forget something!

#b4 #linux Having gotten through using "b4" once now, I generally like it. It pulls together all the things needed for sending a patch to one of the Linux development groups, making it much more difficult to forget something!

#b4 #emacs #magit #python

I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".

After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:

import os; os.environ['TMPDIR'] = os.getenv('PWD')

This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!

5/5

#b4 #emacs #magit #python

I installed "b4" using "pipx", which sets up a virtual environment for the "b4" code and its dependencies. I looked for a way to set TMPDIR to the current working directory when running "b4".

After some research, I found I could create a "foo.pth" file in the pipx virtual environment's site-pakages directory, which a 1 liner:

import os; os.environ['TMPDIR'] = os.getenv('PWD')

This did the trick! b4 prep --edit-cover now works with emacsclient and Magit!

5/5

#b4 #emacs #magit #linux

I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.

Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.

4/5

#b4 #emacs #magit #linux

I'm not sure why Magit really cares. I tried using advice to get around this, but didn't quite get it to work.

Looking at the "b4", I found the Python code for editing the cover letter. It creates a temporary directory and then "COMMIT_EDITMSG" in that directory. Looking at the documentation for tempfile.TemporaryDirectory suggested using an environment variable like TMPDIR. Okay, this is another idea, set TMPDIR to the current working directory.

4/5

#b4 #emacs #magit

The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.

3/5

#b4 #emacs #magit

The file is showing in Emacs. I tried to exit the emacsclient session with C-x #, and it asked if I wanted to create the directory where the file lived. Sure, I say. But at this point its useless. So I looked for ways to work around or fix this problem. With Emacs, I suspect Magit was involved. Looking at the source code, I found the places where this error was triggered. There was no easy way to get around this, other than put the file in the repository directory tree.

3/5

#b4 #emacs #magit #linux

"b4 prep --edit-cover" uses the EDITOR environment variable to figure out which editor to use. Apparently the default for bash on Fedora 42 is to set EDITOR to /usr/bin/vim. While I'm quite versed in vi (the predecessor to vim), I prefer to use Emacs. So I set EDITOR to emacsclient and tried again. But this time I got an error about the file not being in a Git repository, and b4 said the file hadn't changed.

2/5

#b4 #emacs #magit #linux

"b4 prep --edit-cover" uses the EDITOR environment variable to figure out which editor to use. Apparently the default for bash on Fedora 42 is to set EDITOR to /usr/bin/vim. While I'm quite versed in vi (the predecessor to vim), I prefer to use Emacs. So I set EDITOR to emacsclient and tried again. But this time I got an error about the file not being in a Git repository, and b4 said the file hadn't changed.

2/5

#b4 #emacs #magit #linux

I recently found a small typo in some Linux kernel documentation, and posted a patch to get it fixed. There were some problems with the patch, and it was suggested I use a tool called "b4" https://b4.docs.kernel.org/en/latest/index.html. I started using it for my next patch revision, but ran into a snag when editing the patch cover file.

1/5

#b4 #emacs #magit #linux

I recently found a small typo in some Linux kernel documentation, and posted a patch to get it fixed. There were some problems with the patch, and it was suggested I use a tool called "b4" https://b4.docs.kernel.org/en/latest/index.html. I started using it for my next patch revision, but ran into a snag when editing the patch cover file.

1/5

Today, I presented the b4 tool to the Linux council at our office (talk was geared towards developers only though).

My colleagues frequently encountered patch corruption issues with mail servers. They were impressed when I introduced the concept of web endpoint submission.

Thanks to @monsieuricon for such a wonderful tool.

#b4 #kernel

I've created a guide on using the b4 tool to submit patches upstream. Here's the link:

https://www.nayab.dev/opensource/tools/b4-contributors

#Linux #b4 #git #opensource #linuxtools

Audi RS2 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #audi #rs2 #avant #stationwagon #p1 #80 #b4 #8c #turbocharged #inlinefive #cylinder #quattro #permanent #fourwheeldrive (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576625223

Audi RS2 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #audi #rs2 #avant #stationwagon #p1 #80 #b4 #8c #turbocharged #inlinefive #cylinder #quattro #permanent #fourwheeldrive (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576625223

Audi RS2 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #audi #rs2 #avant #stationwagon #p1 #80 #b4 #8c #turbocharged #inlinefive #cylinder #quattro #permanent #fourwheeldrive (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576625223

Audi RS2 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #audi #rs2 #avant #stationwagon #p1 #80 #b4 #8c #turbocharged #inlinefive #cylinder #quattro #permanent #fourwheeldrive (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576625223

Just finished watching B4 (2012), will try to drop some thoughts or review in the comments. #justwatched #watched #cinemastodon #plex #whattowatch #moviedon https://trakt.tv/movies/b4-2012 #B4 #trakt

Audi RS2 #photography #autoworldbrussels #belgie #belgien #belgium #brussels #museum #auto #bruxelles #brüssel #car #cars #highlight #audi #rs2 #avant #stationwagon #p1 #80 #b4 #8c #turbocharged #inlinefive #cylinder #quattro #permanent #fourwheeldrive (Flickr 20.12.2022) https://www.flickr.com/photos/7489441@N06/52576625223

TIL that you can pass lore links to b4 shazam 🤯

#b4 #linux #kernel

b4 tool for code contributors:

The #b4 tool offers features that simplify the process for code contributors submitting patches. Currently, it is increasingly utilized in the #Linux kernel development workflow.

Below are the commands to install and use it for the development workflow for developers.

# Installing on Debian based Linux systems
sudo apt install b4

# Creating separate work branch
b4 prep -n <patch_series_name> -f <commit_id>

# Preparing the cover letter
b4 prep --edit-cover

# Retrieve recipients' email addresses
b4 prep --auto-to-cc

# Set the email subject prefixes
b4 prep --set-prefixes "RFC RESEND"

# Verify the patch before sending
b4 send -o /tmp/presend
b4 send --reflect

# Sending the patch
b4 send
b4 send --resend v2

# Updating the commit with review tags
b4 trailers -u

Detailed explanation:

• b4 tool for code contributors

References:

• Linux Kernel b4 docs
• Do more with lore and b4 - Video

#debian #opensource