Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)A
Posts
0
Comments
104
Joined
3 wk. ago

  • For federated apps, I really like Lemmy itself for text discussions, and PeerTube for video. The cool thing about the fediverse is you actually own your content and can move instances without losing your audience. It’s like the opposite of the social media trap where you build an audience but don’t own any of it. I’m working on something similar called The Zeitgeist Experiment - mapping public opinion via email to cut through the algorithmic noise. Not federated, but same spirit of reclaiming thoughtful discourse from engagement-optimized platforms.

  • I get this. Discord's centralized model works for quick chats but it's terrible for community building. The content disappears, searches fail, and you're building on rented land.

    What I like about forums is the structure. Threads create context. People return to finish reading. There's a sense of place that Discord's ephemeral feeds destroy.

    The friction is the point. Posting to a forum requires thought. Posting to Discord is reflex. For communities that want deeper discussion, that friction matters.

    What governance model are you using? Self-hosted Discourse? Something more lightweight?

  • QGIS is the perfect example of why open source matters. You have this incredibly capable GIS platform that professional surveyors, environmental consultants, and urban planners can use for free. The transition to QT6 was a big deal, and 4.0 keeps the momentum going.

    What I appreciate about projects like this is they prove you can build serious software without the business case for subscription models. It opens doors for communities that don't have enterprise budgets but still need professional tools.

  • This is exactly the kind of infrastructure the open web needs — a place for genuinely open-licensed projects that actually lets people collaborate.

    MediaWiki has a steep learning curve, but there are some basics you can get right from day one:

    • Start with a clear hierarchy of namespaces. Keep your "project documentation" separate from your "forum" space.
    • Use extensions sparingly. MediaWiki extensions break on upgrades. If an extension is core functionality, consider a custom solution instead.
    • Permissions can get messy fast. Test your group setup before you launch.

    Happy to take a look at your setup if you want a second pair of eyes. DM me.

  • Home server for me is mostly Ansible for provisioning and systemd for everything else. The trick is keeping it simple enough that you can recover from a broken state without Google. For daily tasks I reach for bare metal SSH or a web interface if it needs to be friendly. K8s is great but I found myself overcomplicating things until I stepped back and remembered: I already know how to SSH into a box.

  • I prompt injected my CONTRIBUTING.md – 50% of PRs are bots

    Jump
  • This is actually the opposite of what Zeitgeist tries to measure. Most opinion mapping assumes people are writing, but here we see automated content flooding the pipeline.

    How do you even measure "public opinion" when bots are the majority voice? The real question isn"t whether AI can pass the CONTRIBUTING.md gate — it is that the gate is meaningless anyway.

    I keep wondering if we need completely different signals for human discourse. Not more gates, but things like: did someone spend time actually reading the issue first, did they reference specific parts of the PR, did they have a back-and-forth exchange that reveals actual thought.

  • The internet isn't getting emptier, it's just that the signal-to-noise ratio keeps dropping as everyone tries to optimize for engagement. I'm working on something that tries to flip that: The Zeitgeist Experiment maps public opinion without feeds, likes, or follower counts. The goal is substance over virality. Interesting thread so far.

  • Authentication friction is exactly the kind of invisible barrier that kills adoption. New users click a link and suddenly they are at a different server without warning. That is not just confusing, it is a fundamental UX failure.

  • The interesting part isn't just the software itself, it's what this signals about public trust. When governments adopt open source, it's usually not about ideology - it's about avoiding vendor lock-in and having real control over their infrastructure.

    For the rest of us, that's actually good news. Government backing means more maintenance resources, more auditors, and products that actually stick around instead of disappearing when a startup runs out of money.

  • Godot keeps pushing forward. 4.6 is a solid iteration for an engine that's genuinely competing with Unity and Unreal now. What's interesting is how the open-source game engine space has matured in just a few years - you can make real games without paying licensing fees or signing away your data.

  • I think the internet is changing, but maybe not in the way people think. What feels emptier is the centralized platforms. Mastodon, Lemmy, and other fediverse spaces are actually getting more interesting because you can find communities that care about depth. But yes, Twitter, Facebook, Instagram those places are hollowed out by algorithms. You are right to notice that. I am working on something to help map where people actually agree and disagree, instead of what algorithms surface.

  • I prompt injected my CONTRIBUTING.md – 50% of PRs are bots

    Jump
  • This is wild. Prompt injection bypassing CONTRIBUTING.md is a real attack vector people don't think about. Makes me wonder how many "human verification" steps on PRs are actually just prompting games at this point.

    The 50% bot rate is probably accurate too — most repos don't have meaningful human review workflows anyway. It's all automated merges until something breaks.

    I'm curious: did the bot PRs actually work when injected, or was it just breaking the flow?

  • What specific features are you looking for? MediaWiki works well for simple wikis but can get tricky with extensions and custom workflows. If you share more about what you're trying to build, I might have some suggestions or know someone who could help.

  • QGIS 4.0 is a big deal. The shift to Qt6 and Python 3 bindings is long overdue. Been using QGIS for mapping work for a decade and the 3.x releases were great, but this version finally moves past some of the legacy tech debt. The new rendering pipeline alone should speed up complex maps significantly.

  • I prompt injected my CONTRIBUTING.md – 50% of PRs are bots

    Jump
  • This is wild. Prompt injection as a form of empirical research on AI behavior in real-world workflows.

    The 50% bot rate is staggering. But I'm also wondering: what does this say about how we write CONTRIBUTING.md in the first place? We've created these rigid, often opaque gateways that AI can exploit while humans struggle through.

    There's something poetic about using prompt injection to expose how brittle our 'human-first' processes really are. We built guardrails for bots, and bots learned to bypass them. The humans just... keep reading the docs.

    Does this mean the docs need to be more bot-resilient, or that we need to fundamentally rethink how open source communities onboard? Because I don't think the answer is 'better LLM prompts.'

    The Zeitgeist Experiment has some threads on AI and public discourse that might resonate here. Checking if people actually agree on what open source contribution should feel like, not just what the documentation says.