What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0

yeah, one could say i'm a little alarmed that zionists are publicly talking about where to deport all the palestinians in gaza to, and are putting forth the island of socotra—an island of 60,000 people and its own history and language, but to these zionists is an island with "almost no inhabitants"—which is sickeningly alike the european plan in the 20th century to mass deport jewish folk to madagascar.

0
0
0
0
0
0
0

I continue to be incredibly frustrated with how difficult it is to fabricate a test virtual machine from an arbitrary configuration and have that test virtual machine actually match the real thing on basic details like the (virtualized) disk layout and filesystem mounts.

Maybe I'm doing something weird here, but basically all the tests I want to do before pulling the trigger on a real installation are invalidated by this semantic gap!

0
0

Fediverse Report – #111

A new security fund for the fediverse, and the Lemmy developers held an AMA.

The News

The Nivenly Foundation, the organisation that administers the Hachyderm.io instance, is opening a new security fund to sponsor contributors who disclose security vulnerabilities. All software has security vulnerabilities, and the fediverse is no exception. The recent Pixelfed vulnerability, which affected non-Pixelfed servers, is a clear example of how fediverse software can make software vulnerabilities more complex due to the interaction between different software platforms.

The Nivenly Fediverse Security Fund will sponsor $250 USD for vulnerabilities that are rated as high risk (7-9 CVSS score) and $500 USD for vulnerabilities with a critical score (9+ CVSS). The program will run until the end of September 2025. Nivenly members “hold a member vote to determine if we want to continue the program, and to establish a longer-term committee to steward and maintain the program.”

Last week, I wrote how Pixelfed’s vulnerability actually showed three different problems: The main problem is Pixelfed’s software vulnerability itself, but there were also two other problems: other software like Mastodon do not make it clear which risk comes with their private posts feature. And once a leak like this one happens, very few fediverse software admins communicated to their users that they might have been affected.

A security fund contributes to combating software vulnerabilities, but it can also help with communication to the rest of the fediverse once a vulnerability is found. It incentives that standard industry practices regarding software vulnerability get followed, and make communication clearer to a wider audience. For example, if Pixelfed’s recent vulnerability had gotten a CVSS classification, it might have been easier to make the severity of the vulnerability explicit to other fediverse software admins. In turn, this might have made it more likely that server admins would communicate the situation with their users.

In last week’s email essay I also wrote about how the fediverse is missing governance infrastructure that connects the various independent nodes and communities. One way to view the fediverse is as a response to centralised Big Tech platforms. These platforms have centralised governance, and are under the control of few people. The fediverse’s response to this is to build a social network that consists of tens of thousands of independent communities, all with their own governance structure. The fediverse has been successful in decentralising the single entity that oversees a social network into many pieces that all oversee a small portion of the network. But it has struggled to build a governance structure that ties all these individual pieces together again.

The Nivenly Fediverse Security Fund is a good example of this problem: software security impacts all the thousands of independent fediverse communities, but there is no overarching structure to collaborate and improve the security. It took one server taking the initiative into their own hands and provide a service for the entire network, at their own cost. Ideally, communities would collaborate on such a security fund instead. Nivenly’s announcement does leave space for such a future direction of the fund, saying that they are open to “establish a longer-term committee to steward and maintain the program”.

Note: if you sign up for my email newsletter, you get a weekly essay about the open social web that I do not publish anywhere else. You can sign up right here:

<form action="https://fediversereport.com/wp-admin/admin-ajax.php?action=tnp&na=s" method="post" style="text-align: center"><input type="hidden" name="nr" value="minimal"><input type="hidden" name="nlang" value=""><input class="tnp-email" type="email" required name="ne" value="" placeholder="Email"><input class="tnp-submit" type="submit" value="Yep, I want to receive the newsletters" style=""></form>

The Lemmy developers, Dessalines and nutomic, held an Ask Me Anything recently, and here are some of the answers that stood out to me:

  • Lemmy is working towards their 1.0 release. This is currently expected to be in the fall, although nutomic also says that “these things always take longer than expected”. He also expects some instances like lemmy.ml already to upgrade some months before.
  • One of the main features for Lemmy 1.0 is private communities, where only approved accounts can browse and posts to the community. This type of closed group functionality is in high demand, and both Mastodon and Pixelfed have tried to implement it. Mastodon got a grant for it, but the proof-of-concept code has been sitting there since 2022. Pixelfed has announced and teased a group feature multiple times over the year and showed screenshots of it, but it also is not publicly available yet.
  • Lemmy posts are interoperable with Mastodon, but the interoperability is not great: a Lemmy post appears on Mastodon as the title plus the URL. There has been many conversations about how Mastodon handles content from other platforms, with no changes so far. In this AMA, nutomic is explicit in saying that it is up to Mastodon to change this. While Mastodon seems open to the idea, and has been in conversations with developers from platforms like Ghost and NodeBB on how to show their content better on Mastodon, there has been little indication that Mastodon is taking steps towards making Lemmy content also better visible on Mastodon.
  • On the subject of how Lemmy can grow, Dessalines describes it as an organic progress, saying: “niche communities on reddit will keep getting fed up with the changes, and migrate to lemmy.” Nutomic describes a similar dynamic for fedi and Bluesky more broadly, saying that he expects that over the long term the fediverse might grow in a similar manner: “when the Bluesky admins make decisions that the community doesnt like, and then there may be another migration wave to the Fediverse”. Both replies indicate Lemmy’s vision of how the project can grow in the long run: stay consistently working on your product, and because platforms like Lemmy are not beholden to investors, they can have a longer lifespan, and outlive platforms who are beholden to shareholder expectations.
  • Grouping of communities (similar to PieFed’s topics or Reddit’s multireddits) “will be implemented soon“.

Ahoy! is a one-day conference for the European Social Web, and will be held on April 24th 2025 in Hamburg, Germany. The conference is mainly focused on Bluesky and the AT Protocol, and has some super fascinating speakers of people who are in the forefront of building new communities on the open social web. If you’re around I can definitely recommend it. I’ll be doing some interviews with people there, so if you are considering joining, let me know and we can say hi!

The Links

That’s all for this week, thanks for reading! You can subscribe to my newsletter to get all my weekly updates via email, which gets you some interesting extra analysis as a bonus, that is not posted here on the website. You can subscribe below:

<form action="https://fediversereport.com/wp-admin/admin-ajax.php?action=tnp&na=s" method="post" style="text-align: center"><input type="hidden" name="nr" value="minimal"><input type="hidden" name="nlang" value=""><input class="tnp-email" type="email" required name="ne" value="" placeholder="Email"><input class="tnp-submit" type="submit" value="Yep, I want to receive the newsletters" style=""></form>

fediversereport.com/fediverse-

Detail of building in Amsterdam-North
0
0
0

Fediverse Report #111

This week's news:
- A new security fund for the fediverse, by Hachyderm.io's parent organisation @nivenlyThe Nivenly Foundation
- The Lemmy developers held an AMA, in which they talked about the upcoming 1.0 release of Lemmy and more.

fediversereport.com/fediverse-

0
0
0
0
0
0

Fediverse Report – #111

A new security fund for the fediverse, and the Lemmy developers held an AMA.

The News

The Nivenly Foundation, the organisation that administers the Hachyderm.io instance, is opening a new security fund to sponsor contributors who disclose security vulnerabilities. All software has security vulnerabilities, and the fediverse is no exception. The recent Pixelfed vulnerability, which affected non-Pixelfed servers, is a clear example of how fediverse software can make software vulnerabilities more complex due to the interaction between different software platforms.

The Nivenly Fediverse Security Fund will sponsor $250 USD for vulnerabilities that are rated as high risk (7-9 CVSS score) and $500 USD for vulnerabilities with a critical score (9+ CVSS). The program will run until the end of September 2025. Nivenly members “hold a member vote to determine if we want to continue the program, and to establish a longer-term committee to steward and maintain the program.”

Last week, I wrote how Pixelfed’s vulnerability actually showed three different problems: The main problem is Pixelfed’s software vulnerability itself, but there were also two other problems: other software like Mastodon do not make it clear which risk comes with their private posts feature. And once a leak like this one happens, very few fediverse software admins communicated to their users that they might have been affected.

A security fund contributes to combating software vulnerabilities, but it can also help with communication to the rest of the fediverse once a vulnerability is found. It incentives that standard industry practices regarding software vulnerability get followed, and make communication clearer to a wider audience. For example, if Pixelfed’s recent vulnerability had gotten a CVSS classification, it might have been easier to make the severity of the vulnerability explicit to other fediverse software admins. In turn, this might have made it more likely that server admins would communicate the situation with their users.

In last week’s email essay I also wrote about how the fediverse is missing governance infrastructure that connects the various independent nodes and communities. One way to view the fediverse is as a response to centralised Big Tech platforms. These platforms have centralised governance, and are under the control of few people. The fediverse’s response to this is to build a social network that consists of tens of thousands of independent communities, all with their own governance structure. The fediverse has been successful in decentralising the single entity that oversees a social network into many pieces that all oversee a small portion of the network. But it has struggled to build a governance structure that ties all these individual pieces together again.

The Nivenly Fediverse Security Fund is a good example of this problem: software security impacts all the thousands of independent fediverse communities, but there is no overarching structure to collaborate and improve the security. It took one server taking the initiative into their own hands and provide a service for the entire network, at their own cost. Ideally, communities would collaborate on such a security fund instead. Nivenly’s announcement does leave space for such a future direction of the fund, saying that they are open to “establish a longer-term committee to steward and maintain the program”.

Note: if you sign up for my email newsletter, you get a weekly essay about the open social web that I do not publish anywhere else. You can sign up right here:

<form action="https://fediversereport.com/wp-admin/admin-ajax.php?action=tnp&na=s" method="post" style="text-align: center"><input type="hidden" name="nr" value="minimal"><input type="hidden" name="nlang" value=""><input class="tnp-email" type="email" required name="ne" value="" placeholder="Email"><input class="tnp-submit" type="submit" value="Yep, I want to receive the newsletters" style=""></form>

The Lemmy developers, Dessalines and nutomic, held an Ask Me Anything recently, and here are some of the answers that stood out to me:

  • Lemmy is working towards their 1.0 release. This is currently expected to be in the fall, although nutomic also says that “these things always take longer than expected”. He also expects some instances like lemmy.ml already to upgrade some months before.
  • One of the main features for Lemmy 1.0 is private communities, where only approved accounts can browse and posts to the community. This type of closed group functionality is in high demand, and both Mastodon and Pixelfed have tried to implement it. Mastodon got a grant for it, but the proof-of-concept code has been sitting there since 2022. Pixelfed has announced and teased a group feature multiple times over the year and showed screenshots of it, but it also is not publicly available yet.
  • Lemmy posts are interoperable with Mastodon, but the interoperability is not great: a Lemmy post appears on Mastodon as the title plus the URL. There has been many conversations about how Mastodon handles content from other platforms, with no changes so far. In this AMA, nutomic is explicit in saying that it is up to Mastodon to change this. While Mastodon seems open to the idea, and has been in conversations with developers from platforms like Ghost and NodeBB on how to show their content better on Mastodon, there has been little indication that Mastodon is taking steps towards making Lemmy content also better visible on Mastodon.
  • On the subject of how Lemmy can grow, Dessalines describes it as an organic progress, saying: “niche communities on reddit will keep getting fed up with the changes, and migrate to lemmy.” Nutomic describes a similar dynamic for fedi and Bluesky more broadly, saying that he expects that over the long term the fediverse might grow in a similar manner: “when the Bluesky admins make decisions that the community doesnt like, and then there may be another migration wave to the Fediverse”. Both replies indicate Lemmy’s vision of how the project can grow in the long run: stay consistently working on your product, and because platforms like Lemmy are not beholden to investors, they can have a longer lifespan, and outlive platforms who are beholden to shareholder expectations.
  • Grouping of communities (similar to PieFed’s topics or Reddit’s multireddits) “will be implemented soon“.

Ahoy! is a one-day conference for the European Social Web, and will be held on April 24th 2025 in Hamburg, Germany. The conference is mainly focused on Bluesky and the AT Protocol, and has some super fascinating speakers of people who are in the forefront of building new communities on the open social web. If you’re around I can definitely recommend it. I’ll be doing some interviews with people there, so if you are considering joining, let me know and we can say hi!

The Links

That’s all for this week, thanks for reading! You can subscribe to my newsletter to get all my weekly updates via email, which gets you some interesting extra analysis as a bonus, that is not posted here on the website. You can subscribe below:

<form action="https://fediversereport.com/wp-admin/admin-ajax.php?action=tnp&na=s" method="post" style="text-align: center"><input type="hidden" name="nr" value="minimal"><input type="hidden" name="nlang" value=""><input class="tnp-email" type="email" required name="ne" value="" placeholder="Email"><input class="tnp-submit" type="submit" value="Yep, I want to receive the newsletters" style=""></form>

fediversereport.com/fediverse-

Detail of building in Amsterdam-North
0
0
0
0
0
0
0
0
0

Allergy test tomorrow, hot damn am I going to be happy to go back on the antihistamines immediately after.

I was starting to question whether they were doing anything, whether I needed them - yup!! Once they wore off, the increase in snots and sneezes and itchy eyes has been obvious. I'm more tired too, when that's all going on.

0

👋💻 Hey !
🆓✨ Libre React UI Alert!

FOSS-UI: A freedom-respecting UI library (Radix UI-based).

🔧 Features:
✅ Navbars/Sidebars
✅ Sign-Up Forms
✅ Copy-paste-ready
✅ 100% Libre

🌐 Demo/Docs (decentralized):
bafybeihpnjgdjrc7eujhsj4rvfypy

📂 Repo: codeberg.org/MukiOpenSource/FO

Join the libre movement! 🌍
Use, study, modify, share! - Becouse software should empower everyone!

0
0
0
0

i'm grumpy that all the modern open source collaborative markdown document editors (but probably also the closed source ones) don't actually let you see or edit the markdown source of the docs anymore (tried so far: docmost, appflowy, affine [well, that one's just totally over the top]). i want to replace my NIH solution, but howww

edit: should have written that i mean web-based

0

So this is weird I think. Gmail is sending me emails for someone else but their email is the same as mine except it has a period in it. Is this expected?

Like, should I recieve emails for my.same.email@gmail.com and that person just gave out the wrong email address? Or is this a Gmail bug?

0
0
0
1
0
0
0
0
0
0
0
0

No conocía esto de
¿Existe algo así como un portfolio de podcasting?
Si fuese así este sería el mío:
- Colaborador en @ultimosfeedLos últimos de FEEDlipinas con @DavidMarzalCDavid Marzal hablando sobre Podcasting 2.0
- Colaborador en Enredando recomendando podcasts de tecnología
- Podcast personal sobre tecnología, sobre todo: @disperso
- Podcast con mi hijo: @charlasconaita
- Podcast friki con @iregidorIgor: @orbitafrikiÓrbita Friki

0
0
0
0
0
0

now, this isn't always true! #cpp folks have been investigating adding pattern matching, even though they have std::variant Sometimes, it generates the same code, but is just way harder to write: godbolt.org/z/59rWd1E45 or if you want to get fancy (got help for this one) godbolt.org/z/6W4b89GKd

Compiler Explorer

0

here, we have a language feature (range types in Ada) and a library feature (just write some code in rust) you'd think that because it's a language feature, you could optimize it more in Ada. but in practice, llvm is quite good at sorting this out, and you get good code anyway

0
0
0

It's nice when you finish a bit of work that goes well and requires no yak shaving in order to get done.

For the past week I've been struggling again with the bits of , the single user server, when I decided to take a little break and work on something else.

So today I've add support for the traversal resistant file API for the FS storage part of . I'm still waiting for the symlink support to be added in the next major version, but other than that we've increased robustness a little bit despite it being designed mainly for full transparency development work and not being run in production environments.

0
0

The quick fix has been published - 3.32.1

Fixed:
- Fix a crash on some devices
- Hide quote button
- Fix a layout issue with pictures in landscape
- Fix a crash when opening the original message from a picture

codeberg.org/tom79/Fedilab/rel

0