Brian Campbell
@unlambda.hachyderm.io.ap.brid.gy
Working on eVTOLs at Beta Technologies. Python, C, Rust.
Too many hobbies, but right now spending the most of my time learning to fly.
[bridged from https://hachyderm.io/@unlambda on the fediverse by https://fed.brid.gy/ ]
Too many hobbies, but right now spending the most of my time learning to fly.
[bridged from https://hachyderm.io/@unlambda on the fediverse by https://fed.brid.gy/ ]
@xgranade You could try publishing it here: https://grebedoc.dev/
Grebedoc
Static site hosting for Git forges
grebedoc.dev
January 31, 2026 at 1:18 AM
@xgranade You could try publishing it here: https://grebedoc.dev/
@whitequark Yeah, I wasn't really trying to say that the full Fediverse model is perfect, just that the way it allows sharing resources to reduce overhead, while also allowing flexibility for choosing between big instances or self hosted.
On the forges front: yeah, depending on something in […]
On the forges front: yeah, depending on something in […]
Original post on hachyderm.io
hachyderm.io
January 27, 2026 at 8:16 PM
@whitequark Yeah, I wasn't really trying to say that the full Fediverse model is perfect, just that the way it allows sharing resources to reduce overhead, while also allowing flexibility for choosing between big instances or self hosted.
On the forges front: yeah, depending on something in […]
On the forges front: yeah, depending on something in […]
@whitequark So, I think it's not always a choice between "one single centralized host" and "everyone hosts their own."
You can have providers shared by a number of users, giving you that economy of scale, while having a sufficient number of such providers that no one central one can take […]
You can have providers shared by a number of users, giving you that economy of scale, while having a sufficient number of such providers that no one central one can take […]
Original post on hachyderm.io
hachyderm.io
January 27, 2026 at 7:54 PM
@whitequark So, I think it's not always a choice between "one single centralized host" and "everyone hosts their own."
You can have providers shared by a number of users, giving you that economy of scale, while having a sufficient number of such providers that no one central one can take […]
You can have providers shared by a number of users, giving you that economy of scale, while having a sufficient number of such providers that no one central one can take […]
Reposted by Brian Campbell
@dalias @whitequark this is not only obvious but literally, empirically, true https://arxiv.org/abs/2305.18150
Understanding the Helpfulness of Stale Bot for Pull-based Development: An Empirical Study of 20 Large Open-Source Projects
Pull Requests (PRs) that are neither progressed nor resolved clutter the list of PRs, making it difficult for the maintainers to manage and prioritize unresolved PRs. To automatically track, follow up, and close such inactive PRs, Stale bot was introduced by GitHub. Despite its increasing adoption, there are ongoing debates on whether using Stale bot alleviates or exacerbates the problem of inactive PRs. To better understand if and how Stale bot helps projects in their pull-based development workflow, we perform an empirical study of 20 large and popular open-source projects. We find that Stale bot can help deal with a backlog of unresolved PRs as the projects closed more PRs within the first few months of adoption. Moreover, Stale bot can help improve the efficiency of the PR review process as the projects reviewed PRs that ended up merged and resolved PRs that ended up closed faster after the adoption. However, Stale bot can also negatively affect the contributors as the projects experienced a considerable decrease in their number of active contributors after the adoption. Therefore, relying solely on Stale bot to deal with inactive PRs may lead to decreased community engagement and an increased probability of contributor abandonment.
arxiv.org
January 27, 2026 at 2:28 AM
@dalias @whitequark this is not only obvious but literally, empirically, true https://arxiv.org/abs/2305.18150
Reposted by Brian Campbell
@whitequark Nothing says fuck you to community like a stalebot threatening to close issues.
January 23, 2026 at 1:58 PM
@whitequark Nothing says fuck you to community like a stalebot threatening to close issues.
@bagder Makes sense to end the paid program, given the quantity of slop it was receiving. It's too bad because paid bug bounties can be helpful in surfacing real problems, but it makes sense given the circumstances.
Kind of unfortunate to use an AI slop header image along with it, though, don't […]
Kind of unfortunate to use an AI slop header image along with it, though, don't […]
Original post on hachyderm.io
hachyderm.io
January 26, 2026 at 4:01 PM
@bagder Makes sense to end the paid program, given the quantity of slop it was receiving. It's too bad because paid bug bounties can be helpful in surfacing real problems, but it makes sense given the circumstances.
Kind of unfortunate to use an AI slop header image along with it, though, don't […]
Kind of unfortunate to use an AI slop header image along with it, though, don't […]
@myrrlyn.net Also UCC. https://www.ucc.org/it-is-time-to-return-peace-to-our-nations-cities-rev-karen-georgia-thompson-issues-statement-and-prayer-following-2nd-fatal-ice-shooting-in-minneapolis/
But yeah, Episcopal, Quakers, UU, UCC, you've got to be able to find a woke church near you. I've […]
But yeah, Episcopal, Quakers, UU, UCC, you've got to be able to find a woke church near you. I've […]
Original post on hachyderm.io
hachyderm.io
January 25, 2026 at 4:43 AM
@myrrlyn.net Also UCC. https://www.ucc.org/it-is-time-to-return-peace-to-our-nations-cities-rev-karen-georgia-thompson-issues-statement-and-prayer-following-2nd-fatal-ice-shooting-in-minneapolis/
But yeah, Episcopal, Quakers, UU, UCC, you've got to be able to find a woke church near you. I've […]
But yeah, Episcopal, Quakers, UU, UCC, you've got to be able to find a woke church near you. I've […]
Reposted by Brian Campbell
things will get better
January 22, 2026 at 1:25 AM
things will get better
@futurebird Of course, looking through some photos of it, it becomes obvious why there was so much confusion about the name; depending on the angle, "EVERGREEN" or "EVER GIVEN" might be the more prominent text that you see.
January 22, 2026 at 2:35 AM
@futurebird Of course, looking through some photos of it, it becomes obvious why there was so much confusion about the name; depending on the angle, "EVERGREEN" or "EVER GIVEN" might be the more prominent text that you see.
@futurebird The confusing part is that despite the name of the ship being Ever Given, the company is Evergreen and that's what's painted in large letters on the side.
January 22, 2026 at 2:23 AM
@futurebird The confusing part is that despite the name of the ship being Ever Given, the company is Evergreen and that's what's painted in large letters on the side.
@xgranade Heh, this got me looking into the LIT file format and tools that already deal with it.
One of them is "Convert LIT" for stripping DRM off of LIT files, which had to provide two links to download the source because back in the bad old days of no HTTPS […]
[Original post on hachyderm.io]
One of them is "Convert LIT" for stripping DRM off of LIT files, which had to provide two links to download the source because back in the bad old days of no HTTPS […]
[Original post on hachyderm.io]
January 19, 2026 at 11:12 PM
@xgranade Heh, this got me looking into the LIT file format and tools that already deal with it.
One of them is "Convert LIT" for stripping DRM off of LIT files, which had to provide two links to download the source because back in the bad old days of no HTTPS […]
[Original post on hachyderm.io]
One of them is "Convert LIT" for stripping DRM off of LIT files, which had to provide two links to download the source because back in the bad old days of no HTTPS […]
[Original post on hachyderm.io]
@whitequark There's also the "Made with ♥️ by ." in GitHub readmes. Sorry, corporations are incapable of ♥️, so you straight up know that they are lying here.
It's also common enough that it shows up in a lot of LLM generated READMEs, so the other common alternative is that […]
It's also common enough that it shows up in a lot of LLM generated READMEs, so the other common alternative is that […]
Original post on hachyderm.io
hachyderm.io
January 16, 2026 at 3:26 PM
@whitequark There's also the "Made with ♥️ by ." in GitHub readmes. Sorry, corporations are incapable of ♥️, so you straight up know that they are lying here.
It's also common enough that it shows up in a lot of LLM generated READMEs, so the other common alternative is that […]
It's also common enough that it shows up in a lot of LLM generated READMEs, so the other common alternative is that […]
Ah, the status page is finally reflecting that there's another incident.
January 15, 2026 at 5:30 PM
Ah, the status page is finally reflecting that there's another incident.
January 14, 2026 at 10:44 PM
@xgranade So, this seems to mirror fairly closely the long term distinction between the copyleft folks, who want to utilize the copyright system in order to prevent enclosure, and the permissive license folks, who just think that sharing is a good thing or it's a better way to develop and […]
Original post on hachyderm.io
hachyderm.io
January 14, 2026 at 6:13 AM
@xgranade So, this seems to mirror fairly closely the long term distinction between the copyleft folks, who want to utilize the copyright system in order to prevent enclosure, and the permissive license folks, who just think that sharing is a good thing or it's a better way to develop and […]