#b4 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #b4, aggregated by home.social.
-
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... -
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... -
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... -
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... -
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... -
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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 im Harz: Unbekannte schießen mit Schusswaffe auf Blitzer
Stand: 05.03.2026 11:32 Uhr Laut Polizei wurde die Technik in der Radaranlage stark beschädigt. Auf der B4 bei…
#Braunschweig #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #"Blitzer" #Aktuell #B4 #Braunlage #Germany #Goslar #Niedersachsen #Oderteich #Polizei #Schusswaffe
https://www.europesays.com/de/845258/ -
#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 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 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-девайс, открыть в браузере и получить работающий результат без возни с десятками аргументов командной строки.
-
B4 — обход DPI с веб-интерфейсом
B4 - инструмент обхода DPI на Go с веб-интерфейсом. Хотелось сделать инструмент, который можно поставить на роутер или любой другой linux-девайс, открыть в браузере и получить работающий результат без возни с десятками аргументов командной строки.
-
B4 — обход DPI с веб-интерфейсом
B4 - инструмент обхода DPI на Go с веб-интерфейсом. Хотелось сделать инструмент, который можно поставить на роутер или любой другой linux-девайс, открыть в браузере и получить работающий результат без возни с десятками аргументов командной строки.
-
B4 — обход DPI с веб-интерфейсом
B4 - инструмент обхода DPI на Go с веб-интерфейсом. Хотелось сделать инструмент, который можно поставить на роутер или любой другой linux-девайс, открыть в браузере и получить работающий результат без возни с десятками аргументов командной строки.
-
Công cụ b4 dành cho các nhà phát triển kernel Linux đang thử nghiệm giao diện người dùng dạng văn bản (TUI) để hỗ trợ kiểm tra mã bằng trợ lý AI như Claude Code. Mới đây, công cụ này đã tự review chính các bản vá của mình — một bước tiến thú vị. Tính năng là tùy chọn, giúp tăng hiệu suất và phát hiện lỗi ẩn, nhưng không bắt buộc sử dụng. #b4 #LinuxKernel #AIReview #ClaudeCode #OpenSource #Linux #KernelDevelopment #AIAssistant #DevTools #CôngCụPhátTriển #NhânLinux #TrợLýAI
https://www.phoronix.c
-
Schwerer Unfall auf B4: 53-Jähriger weiter in Lebensgefahr
Stand: 28.10.2025 20:08 Uhr Nach einem schweren Unfall auf einer Brücke über dem Mittellandkanal bei Braunschweig mit drei…
#Braunschweig #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #B4 #Feuerwehr #Germany #Hubschrauber #Mittellandkanal #Niedersachsen #Rettungsdienst #Unfall
https://www.europesays.com/de/533664/ -
Unfall bei Braunschweig: Auto stürzt in Mittellandkanal – drei Tote
Stand: 27.10.2025 18:33 Uhr Zwei Tage nach dem tödlichen Unfall bei Braunschweig hat die Polizei neue Erkenntnisse veröffentlicht.…
#Braunschweig #Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #B4 #Feuerwehr #Germany #Hubschrauber #Mittellandkanal #Niedersachsen #Rettungsdienst #Unfall
https://www.europesays.com/de/531085/ -
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?
-
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?
-
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?
-
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?
-
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?
-
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.
-
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.
-
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 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
-
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
-
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
-
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
-
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