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

2026 への移動を最高にするためのスポンサーイベントを開催します。お申し込みいただくだけで、無料で「さんふらわあ」にご乗船でき、何十人もの Rubyist と一緒に苫小牧まで海路で向かうことが出来ます。昨年ご好評をいただいた でご都合が悪かった方も、是非今回でリベンジしていただければと思います。 https://gmo.connpass.com/event/384252/

0
0
1
0

summerofcode.withgoogle.com/pr

GIMP has again been accepted as part of the Google Summer of Code project - see the link for details and some project ideas.

We have a no-AI policy: in particular we need people who will understand the code they write :-) and write code that we can maintain.

Feel free to get in touch - see gimp.org/discuss.html

0
2
0
0
0
0

@rakoo @ricciRob Ricci have a read of Lauren's article: connectedplaces.online/where-d

Yes, community on AT Protocol is a nascent concept still, but the separation of identity + data from applications makes it possible to experiment and have one social graph or many.

One project doing community spaces on AT Protocol is: github.com/collectivesocial/op

@thisismissemEmelia 👸🏻 @ricciRob Ricci

yes, if we're looking at mastodon and the model it has created that all microblogging apps have copied, then community doesn't really exist in the technical parts but must be artificially built up. The more interesting example is the threadiverse where communities are literal spaces: people congregate towards one or any number, they are independent from your server and from your identity. This, to me, feels closer to how communities start to create: pick an obvious topic, make obvious-y rules about what is on-topic or not to guide what people can talk about, then possibly graduate from there to another form (maybe a specific, closed community with your people). I do think more visibility should be given to the threadiverse rather than microblogging, or even mastodon, because of all the problems you have listed. And the future direction of AP should definitely split the server from the usage and build apps on the client only !
0
0
3
0
0
0
0
0
0

You think web page size bloat is bad on some things? oh boy.

Good afternoon to everyone, except bumn.go.id (an Indonesian government website) for having a (at least) 3GB web page because of embedded MP4's with uncompressed audio and video seeming straight from the camera...

This must cost so much for them, like a single page load could cost at least $0.15 in cloud egress fees alone

ql64389Pkg2BXLw4Pn.png
0
0

Yup. In the short term markets are about as rational as that bearded guy in a bathrobe shuffling around in his slippers under the freeway underpass shouting at imaginary greebles. Reminder: In the long run irrational stuff ends up getting washed out of markets as it gets out-competed, thus the "rational markets hypothesis". But in the long run we're all dead.

@mhoye 8d

To spell this out clearly, the reason RAM has quadrupled in price
is that a huge quantity of RAM that hasn't been produced yet has
been bought with money that doesn't exist to populate GPUs
that also haven't been produced to go in datacenters that haven't
been built powered by infrastructure that may never exist to meet
a demand that doesn't exist at all to make profit margins that
mathematically can't exist while economists talk about this thing
they call the "rational markets hypothesis".
0
5
0
0
4
0
0
0

Sup is meant for those who use Snapchat, Whatsapp and Messenger daily, but also brings a clean and refined experience to people who prefer other protocols.

The modular nature of Sup separates identity from protocols to connect you to your people, wherever they are, with push notifications, dark mode, and even video chat!

This should exist, but it would be difficult to grow from scratch...

Unless you had two platforms you could integrate with first class support.

😎

0
0
1
0

RE: hachyderm.io/@mekkaokereke/116

Mekka's take on the methodological implications on the (lack of) cross-tabs on this study are on point, but there's another thing to look at here: our definition of "platforming". So much discussion of "platforming" is conducted from the perspective of "are these ideas dangerous, is it OK to let people hear these dangerous ideas". That's not what is happening. The speech acts involved are not "conveying ideas" and letting people analyze them.

0

Reading a post that predicts redundancy of 50% of white collar jobs in the next 5 years due to AI. This is a pro-AI post. Ignoring what seems to me some questionable reasoning, the author does not seem to acknowledge that this may have some pretty negative effects on a societal level.

0
0

Donkeys: Whatchu doin goofy human?

Me: Well, I’m taking your picture to try to ease the sorrows of humanity.

Donkeys: We’ve got some sorrows you could ease.

Me: Oh yeah?

Donkeys: Yeah, like, we broke one of our toys and one of us has probably swallowed a large piece of it, but you could get us a new one. And then maybe call the vet.

Two donkeys, up close, peering intently into the frame of the camera, ears up, noses down.
0
4
0
0

🕐 2026-02-20 18:00 UTC

📰 クラウド型コーディングエージェントの時代がまた来る (👍 99)

🇬🇧 Local coding agents hit cognitive limits. Cloud-based agents like Devin may return as the solution to handle complexity beyond local tools.
🇰🇷 로컬 코딩 에이전트가 인지 부하 한계에 도달. Devin 같은 클라우드형 에이전트가 복잡성 해결사로 재부상할 전망.

🔗 zenn.dev/ubie_dev/articles/925

0
1
1
0
0

One way to know Claude is a joke is it can’t even get right questions about itself. Asked it how could I tell it to stop asking if it could do any read operation on a directory. It told me how to configure it. I asked it the change needed restarting or if it would pick it up. It told me it would pick it up, there was no need to restart, changes were immediately. After asking several times for more permissions and I insisting to not ask, it finally admitted it required a restart.

0
0
0
0
1
0
9
0
0

new from me: FR#154 - Search and Community

@HolosSocial shut down their fediverse search engine, over concerns that some users have the flag for being indexable turned on without consciously enabling it.

If the consent flag Holos relied on frequently doesn't represent consent, that's a problem, because Mastodon's FASP project relies on the same.

connectedplaces.online/reports

0
0
0
0
0
0
0
0
0
4
0
0

FR#154 – Search and Community

Last week, Holos Social quietly shut down Holos Discover, a fediverse search engine built on ActivityPub. It had put in serious effort to allow for user consent, it only indexed public posts from accounts with the indexable flag enabled, appeared as a visible follower, processed deletions and edits in real time, and excluded accounts that were locked or had in their bio. This is about as close you can get to building a consent-respecting search engine in the current fediverse.

Community members pointed out that the indexable flag is enabled by default on many instances, which means that a significant number of accounts with the flag set never made a deliberate choice to be indexed. The flag that’s supposed to signal “this person consents to being searchable” frequently signals “this person’s server admin didn’t change the default”, and on a protocol-level, there is no difference between these two options.

Search and indexing projects on the fediverse tend to end the same way, from early full-text indexing attempts through Searchtodon‘s careful experiment with personal timeline search in 2023, to FediOnFire‘s relay-based firehose display earlier this year. Not all of this resistance was unjustified: Maven imported over a million fediverse posts without notice and ran AI sentiment analysis on them, which is a far cry from what Holos was building. But the community response has rarely distinguished between projects that deliberately violate consent and projects that try to respect it. Bridgy Fed survived a similar cycle by shifting to an opt-in model, but it’s the exception. The norm against search was established during periods of intense community backlash that sometimes crossed into coordinated harassment. These backlashes have grown less intense as people seem to have largely moved on. See for example how Searchtodon got an intense backlash in early 2023, and I explicitly flagged an offline-first client that could do effectively the same in fall 2025 that did not get any backlash. Still, the expectation for backlash persists as internalized caution.


The community correctly identified that the indexable flag doesn’t reliably represent individual consent. Helen Nissenbaum’s work on contextual integrity makes the case that privacy isn’t about secrecy but about appropriate information flows: posting on Mastodon carries an implicit norm about who will encounter that post and why, and violating that norm is a privacy breach even if the post was technically public. Daniel Solove and Woodrow Hartzog make a similar legal argument, saying that publicly available data is still regularly protected by privacy law, and that accessibility alone doesn’t license arbitrary downstream use.

But the only available response to discovering that the indexable flag is unreliable, treating all defaults as non-consent, has some major side effects. It removes the possibility that a server admin could legitimately say “our community values public discovery, so we set defaults that support that.”The protocol has no way to represent whether a default was set deliberately or by inertia. So the community norm treats them the same, which in practice means that a server admin who says ‘our community is about public discovery’ gets treated identically to one who never looked at the settings page. This results in a view of fediverse servers that only contains individual choices, and where a community deciding collectively to be discoverable is not an available category.

This is a strange outcome for a network that’s supposed to enable governance diversity across communities. Mastodon published a blog post this week where Executive Director Felix Hlatky says the mission is to “connect the world through thriving online communities”. But this current structure for how to signal consent for data processing can only recognise the individual, and has no mechanism for a community to signal anything.

There is also something patronizing about the framing that treats defaults as equivalent to non-consent. If we take seriously the idea that servers are communities with governance, then an admin who configures their server for public discovery is making a governance decision on behalf of their community, not failing to notice a checkbox. Treating all defaults as non-consent refuses to recognize that decision as legitimate, which undermines exactly the kind of community-level agency that a decentralized network is supposed to enable. As I argued in another article this week, where community lives in these networks is an open question, but it can’t be answered if the architecture only recognizes individuals.

Meanwhile, there are about half a dozen ways to harvest fediverse data with no accountability and no opt-out attached, and all of them are effectively condoned because they happen out of sight. What the current setup actually does is push practices for data gathering out of sight, where no opt-out mechanisms exist, instead of creating conditions where accountable tools can be built in the open. The current system is better at protecting the community’s idea of itself as a place that takes consent seriously, than it is at actually protecting users.


Mastodon’s Fediverse Discovery Providers project, or Fediverse Auxiliary Service Providers (FASP), is building a specification for pluggable search and discovery services that any fediverse server can connect to, funded by an NGI Search grant. It aims to solve the same problem as Holos, providing discovery infrastructure that can be used by other servers.

The FASP specification explicitly states that providers will “only ingest content from creators who opted in to discovery in the first place” and will “respect this setting,” referring to the same indexable signal that Holos relied on. The spec is well-designed in other respects: it is decentralized, allows servers to choose among competing providers, separates content URIs from content fetching in ways that limit data exposure, and requires signed fetch requests so servers can identify and block specific providers. But the problem is that the consent mechanism at its foundation is one the community has already explicitly said it doesn’t trust.

If the Holos episode established that the indexable flag is insufficient because it can’t guarantee individual deliberate consent, then FASP’s privacy model has the same hole. It shows that the lack of search and discovery is a governance problem, not a technical problem. Holos and their experience building a search engine shows that the ‘indexable’ flag is not sufficient. The technical infrastructure for discovery is being built, but the governance infrastructure for consent, a way to distinguish deliberate community choices from defaults, is not discussed at all.

connectedplaces.online/reports

Doors of an electricity dispatch building
0

22日のコミティアへ参加させていただきます☆彡

「COMITIA155」
2026年2月22日(日)
場所:東京ビッグサイト
配置:東5ホール こ-06a

*参加サークル名:マタタビMIX

・・・+お品書き +・・・
▼新刊
「ノスタルジックソビエト」400円(2026/2/22発行)

▼既刊
「おくすりの時間」400円(2025/11/24発行)/他
・・・・・・・・・・・・

ギリギリになりましたが、新刊は赤い本になりました 。.☆.:*

新刊「ノスタルジックソビエト」
0
0

ていうか技術革新とかどれだけあっても一向に労働時間が減る気配がないのはなぜかをまじめに考えようとしてるのが『ブルシット・ジョブ』ですたぶん(6割まで読んだ

0