Real world tackling the #geekproblem

With rebooting the #openweb we run headfirst into the #geekproblem, a recurring pattern where: Technically brilliant people build powerful tools …but those tools remain socially unusable …or solve only geek problems, not the needs of actual communities. It’s not malice, often it’s idealism, but it creates a dead-end culture of endless prototypes, abandoned standards, and empty tech demos. Meanwhile, the real-world crisis deepens.

The work we need is bridges building, let’s try this ere “P2P news app” built on #dat Hypercore/Hyperswarm is exciting. Yes, it’s similar to Nostr in structure: distributed relays, client-side aggregation, unstoppable flow. But as with Nostr tech isn’t enough. We are social creatures. A usable system needs:

Clear use cases rooted in human relationships – not just tech possibilities.
User-facing front-ends that invite participation, not gate it.
Interoperability with existing protocols (ActivityPub, ATProto, etc.) to avoid siloing.
Bridges between architectures – e.g. client-server ↔ P2P – so that real-world adoption is gradual and survivable.

The good news, the wider #OMN project is already a sane path forward, with a #KISS hybrid path. The plan is in bridging #P2P and client-server as a way out of this. Something like:

A lightweight server bridge that serves data to client-server users (ActivityPub, fediverse, legacy web),

While simultaneously feeding a P2P mesh, with each peer storing and distributing redundant objects,

So that over time, client-server becomes the bootstrapping layer, and #P2P becomes the long-term archive + resistance layer.

“Data is just object flows – how the user gets the object is irrelevant technically.”

This is the kind of thinking that gets us out of the traps, by moving from protocols to people. This isn’t just about code, it’s about culture. The #geekproblem won’t be solved by more architecture diagrams, it needs movements that embrace imperfection and prioritizes social use, visible, working front-ends people can contribute to and understand, documentation and tooling that builds capacity in others, not silos around the brilliant few.

What next? For the devs:

Can the p2p-news-app codebase be modularized to plug into #OMN projects as a data backend, even in a basic way?

Can we bridge shared data objects across protocols (e.g. post metadata flows from P2P → ActivityPub), even if janky at first?

Can we prototype a simple but cross protocol usable frontend, the examples is the work on #makeinghistory and #indymediaback, that lets non-geeks see and touch the network they’re part of?

Yes, for the movement, keep things messy but moving. Avoid dead ends by always asking:

"How does this empower non-technical users to organize, document, and publish together?"

Keep the tech grounded in the social fabric, the activists, journalists, organisers, and rebels this is all meant to serve. If you’re reading this and thinking, “I can help,” please step forward. There’s space in wider tech/social #OMN and #MakingHistory for everyone, coders, writers, designers, testers and storytellers.

Let’s build bridges, not silos, let’s build tools people can use, not just tools geeks can admire, let’s do this together.

Telegram messaging app is dieing

Telegram partnering with Elon’s #AI to distribute #Grok inside chats is a clear line crossed. This matters because private data ≠ training fodder, bringing Grok (or any #LLM) into messaging apps opens the door to pervasive data harvesting and normalization of surveillance.

This is an example of platform drift: Telegram was always sketchy (proprietary, central control, opaque funding), but this is active betrayal of its user base, especially those in repressive regions who relied on it.

Any #LLM like Grok in chats = always-on observer: Even if “optional,” it becomes a trojan horse for ambient monitoring and a normalization vector for AI-injected communication.

“Would be better if we had not spent 20 years building our lives and societies around them first.”

That’s the #openweb lesson in a sentence, that the #dotcons will kill themselves. This is what we mean by “use and abuse” of these platforms which have been driven by centralization, adtech, and data extraction, that they inevitably destroy the trust that made them popular. It’s entropy baked into their #DNA. As Doctorow calls this #enshitification, the tragedy is how much time, emotion, and culture we invested in them – only to have to scramble for alternatives once they inevitably betray us.

What to do now, first step, remove data from your account then delete telegram app, not just for principle, but for your own safety. Move to alternatives – #Signal for encrypted, centralized messaging (trusted but closed server). There are other more #geekproblem options in the #FOSS world but like #XMPP, #RetroShare, or good old email+GPG can work too, but they can be isolating, so stick to #signal if you’re at all #mainstreaming.

Then the second step, build parallel #4opens paths by supporting and develop alt infrastructure like the #Fediverse (Mastodon, Lemmy, etc.), #OMN (Open Media Network – decentralized media), XMPP and #p2p-first protocols, #DAT/#Hypercore, #IPFS, or #Nostr etc.

Yeah, things will get worse before they get better, what we’re seeing now is the terminal phase of the #dotcons era. These companies are devouring themselves and will eventually collapse under the weight of their contradictions. The question is, will we have built anything to replace them?

If not, authoritarian tech (like Elon’s empire) fills the void. That’s why we rebuild the “native” #openweb, even if it’s slow, messy, and underground. That’s why projects like #OMN and #Fediverse matter. If you’re reading this, you’re early to the rebuild, welcome, let’s do better this time.

User Story #makeinghistory

The “User Story #makeinghistory” outlines a process for digitizing the Campbell Family archive, which contains significant historical materials related to activism and political movements. Here’s a breakdown of the steps involved:

Setting up the Application: The archive sets up a desktop computer or a hosted VPS instance to install the #DAT based p2p application for “makeinghistory.”

Uploading Digital Files: They use the application to create an account and start uploading directories of digital files from the archive, adding basic metadata if possible.

Building a Community: The archive builds a community of users, including family members and wider activist groups, to seed an affinity group and encourage them to install the application on their devices.

Column Structure: Users see columns like “new” and “recent” along with others added by users working on the same accounts. These columns contain boolean logic lists of the data in the account.

Data Interaction: Users can interact with the data, adding metadata, information, and editing hashtags. They can swipe through items and modify data as needed.

Categorization: By editing hashtags and data, items move into category columns and into the recent columns.

Engagement: Users actively participate in categorizing content instead of passive scrolling. As others add metadata, it updates the feeds of other users, encouraging them to return and contribute.

Story Feature: Archived categorized metadata-enriched data flows are turned into cohesive narratives using the story feature, providing overviews and linking multiple items and categories.

Sharing History: The created histories can be shared with the wider world, providing grassroots quality history in addition to traditional top-down narratives.

Impact: People use these stories to inspire real and lasting social change, recognizing the importance of history in driving progress.

The “User Story – Resistance Exhibition” extends this concept to an exhibition setting, where visitors can participate in archiving and storytelling using a app installed at the exhibition. This creates a participatory space where people can engage with historical materials and contribute to ongoing projects. All data collected is public and available for use in other projects, emphasizing openness and collaboration.

The new and old #openweb protocols

The #nostr crew are the children of #web3 mess, they are a bit reformed, let’s see.
Then the #BlueSky are the reformed children of the #dotcons
The #fediverse is the child of the #openweb

Q. Where would you put #dat or #ssb and in general the #p2p post-web tools?

#dat is a child of the #geekproblem if it is reformed or not, you can maybe tell me?
#SSB was a wild child, now sickly/lonely with the #fahernable kids gathering round #nostr
#p2p was the poster child of the era of the #openweb it was caught in the quicksand of legal issues, the shadow that was left was eclipsed by “free to use” #dotcons Now finds it hard to come back due to mobile devices not having an IP address, thus most people not actually able to use p2p reliably.