home.social

#buildingthefuture — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #buildingthefuture, aggregated by home.social.

  1. From Digital Neofeudalism to Sovereignty: How I Built My Own Knowledge Operating System

    Most of us live today in a state of digital neofeudalism. We have become digital sharecroppers: our notes, thoughts, and technical documentation are "leased" from large SaaS corporations. If Notion goes down, your knowledge disappears. If Evernote changes its terms and conditions, your data becomes hostage.

    I decided to say "enough." I built a system that is 100% mine, self-documenting code, and works the way I think: nonlinear.

    🧠 Knowledge Architecture: A Network Instead of a List

    A traditional blog is a list. My knowledge base is a graph. I use Markdown and the Zettelkasten approach to create a network of connections. Thanks to Hugo (@gohugoio), each note knows who links to it.

    How does it work?

    One article contains reasons, which are the titles of separate publications. These, in turn, have backlinks like "this motivated me to...".

    graph TD
    A[homelab.md] -->|why?| B[digital-neofeudalism.md]
    A -->|business model| C[digital-sharecroppers.md]
    B -->|solution| A
    C -->|motivation| A

    I use transclusion (include) to inject fragments of technical documentation where they're needed. No more "copy-paste."

    🏗️ Hardware: Division of roles in the ecosystem

    My homelab isn't one big server. It's specialized units:

    | Machine | Role | Characteristics |
    | --- | --- | --- |
    | R3930 | Workhorse | heavy containers, databases. |
    | Wyse 5070 | Guardian | DNS (Pi-hole), Proxy, SSO (Authelia). |
    | DELL GB10 | AI Accelerator Cluster | LLM. |
    | Laptop | Command Center | This is where the code is written, and this is where Ansible runs. |

    Why is the Gateway (Proxy/SSO) on a small Wyse? Because it's quiet, energy-efficient, and supposed to run 24/7, even when the "workhorse" is resting.

    🛠️ Infrastructure as Code (Ansible)

    I don't configure servers manually. Everything is defined by SSoT (Single Source of Truth) in YAML. One file describes the entire lab:

    services:
    - id: "technical-docs"
    name: "Wiki"
    fqdn: "docs.lab.arpa"
    target_host: "R3930"
    is_private: false
    category: "Knowledge"

    Ansible takes this list and:

    1. Deploys the container on the appropriate host.
    2. Configures nginx-proxy on the Wyse to route traffic to R3930.
    3. Injects authorization rules into Authelia.
    4. Updates the Homepage dashboard.

    🔒 Security: SSO and Custom CA

    Let's Encrypt has no place on the .arpa network. I built my own Certificate Authority (Own CA) based on Smallstep.

    • Authelia (SSO): One login and password (plus 2FA) to access all private services.
    • Smallstep SSL: Every service in the *.lab.arpa domain has a "green padlock." Ansible ensures that my laptop and all servers trust my Root CA.

    Development Challenge: Automating SSL via the ACME protocol on my own network is pure magic. Nginx automatically requests a certificate from the local CA server. Without accessing the internet.

    📊 Result: Dashboard

    The end result is the Homepage – a dashboard that generates automatically. I can see every service, its status, and information about which physical hardware it currently resides on.

    🚩 What's next?

    My knowledge operating system is growing, but it has one weak point. If the Wyse DNS server goes down, I'm out. So in the next post, we'll cover DNS2 redundancy and data synchronization using Gravity Sync.

    Homelab isn't a goal, it's a process. And you? Are you still working your tail off in the cloud?

    #DigitalIndependence #OpenSource #SelfHosting #DataPrivacy #TechFreedom #BuildingTheFuture
    #DigitalNeofeudalism #DigitalSharecroppers #KnowledgeOperatingSystem #Ansible #Homelab

  2. From Digital Neofeudalism to Sovereignty: How I Built My Own Knowledge Operating System

    Most of us live today in a state of digital neofeudalism. We have become digital sharecroppers: our notes, thoughts, and technical documentation are "leased" from large SaaS corporations. If Notion goes down, your knowledge disappears. If Evernote changes its terms and conditions, your data becomes hostage.

    I decided to say "enough." I built a system that is 100% mine, self-documenting code, and works the way I think: nonlinear.

    🧠 Knowledge Architecture: A Network Instead of a List

    A traditional blog is a list. My knowledge base is a graph. I use Markdown and the Zettelkasten approach to create a network of connections. Thanks to Hugo (@gohugoio), each note knows who links to it.

    How does it work?

    One article contains reasons, which are the titles of separate publications. These, in turn, have backlinks like "this motivated me to...".

    graph TD
    A[homelab.md] -->|why?| B[digital-neofeudalism.md]
    A -->|business model| C[digital-sharecroppers.md]
    B -->|solution| A
    C -->|motivation| A

    I use transclusion (include) to inject fragments of technical documentation where they're needed. No more "copy-paste."

    🏗️ Hardware: Division of roles in the ecosystem

    My homelab isn't one big server. It's specialized units:

    | Machine | Role | Characteristics |
    | --- | --- | --- |
    | R3930 | Workhorse | heavy containers, databases. |
    | Wyse 5070 | Guardian | DNS (Pi-hole), Proxy, SSO (Authelia). |
    | DELL GB10 | AI Accelerator Cluster | LLM. |
    | Laptop | Command Center | This is where the code is written, and this is where Ansible runs. |

    Why is the Gateway (Proxy/SSO) on a small Wyse? Because it's quiet, energy-efficient, and supposed to run 24/7, even when the "workhorse" is resting.

    🛠️ Infrastructure as Code (Ansible)

    I don't configure servers manually. Everything is defined by SSoT (Single Source of Truth) in YAML. One file describes the entire lab:

    services:
    - id: "technical-docs"
    name: "Wiki"
    fqdn: "docs.lab.arpa"
    target_host: "R3930"
    is_private: false
    category: "Knowledge"

    Ansible takes this list and:

    1. Deploys the container on the appropriate host.
    2. Configures nginx-proxy on the Wyse to route traffic to R3930.
    3. Injects authorization rules into Authelia.
    4. Updates the Homepage dashboard.

    🔒 Security: SSO and Custom CA

    Let's Encrypt has no place on the .arpa network. I built my own Certificate Authority (Own CA) based on Smallstep.

    • Authelia (SSO): One login and password (plus 2FA) to access all private services.
    • Smallstep SSL: Every service in the *.lab.arpa domain has a "green padlock." Ansible ensures that my laptop and all servers trust my Root CA.

    Development Challenge: Automating SSL via the ACME protocol on my own network is pure magic. Nginx automatically requests a certificate from the local CA server. Without accessing the internet.

    📊 Result: Dashboard

    The end result is the Homepage – a dashboard that generates automatically. I can see every service, its status, and information about which physical hardware it currently resides on.

    🚩 What's next?

    My knowledge operating system is growing, but it has one weak point. If the Wyse DNS server goes down, I'm out. So in the next post, we'll cover DNS2 redundancy and data synchronization using Gravity Sync.

    Homelab isn't a goal, it's a process. And you? Are you still working your tail off in the cloud?

    #DigitalIndependence #OpenSource #SelfHosting #DataPrivacy #TechFreedom #BuildingTheFuture
    #DigitalNeofeudalism #DigitalSharecroppers #KnowledgeOperatingSystem #Ansible #Homelab

  3. At RS Solar CAD Group, we stand by strong values - fairness, responsibility, and a dedication to shaping a brighter future. Our journey towards a sustainable world through precise solar design and engineering underscores the power of purpose and action in driving real change.

    Together, let's advance with respect, collaboration, and a collective dedication to progress.

    #MLKDay #Leadership #Equality #Integrity #Sustainability #RSsolarCADGroup #BuildingTheFuture

  4. Every milestone brings us closer to a single, seamless financial ecosystem — one that connects people, payments, and possibilities across the world.
    From decentralized infrastructure to real-time global interoperability, we’re building the universal financial OS that empowers everyone, everywhere.
    The journey has just begun.
    #Nirvista #Roadmap2025 #FutureOfFinance #FinancialOS #DecentralizedFuture #BorderlessPayments #FintechInnovation #DigitalEconomy #NextGenFinance #BuildingTheFuture

  5. We're building the machines that will inspire future generations. The techniques we pioneer, the boundaries we push - all become foundation for builders not yet born.
    Save this perspective for when your work feels insignificant. You're contributing to motorcycle evolution.
    What current experimental technique do you think will become standard? Innovation often looks crazy at first.

    #futurevision #pioneeringspirit #innovationcycles #buildingthefuture

    🎥 👉 @ac_fortyeight

  6. We're building the machines that will inspire future generations. The techniques we pioneer, the boundaries we push - all become foundation for builders not yet born.
    Save this perspective for when your work feels insignificant. You're contributing to motorcycle evolution.
    What current experimental technique do you think will become standard? Innovation often looks crazy at first.

    #futurevision #pioneeringspirit #innovationcycles #buildingthefuture

    🎥 👉 @ac_fortyeight

  7. O @garrykasparov.bsky.social é, de facto, um comunicador nato. Capacidade de brincar com ele próprio, enquanto conta uma história, um bocadinho de História. Muito fixe :-) #buildingthefuture #buildingthefuture2025

  8. Queria usar hashtags, fui ver se estavam identificadas. Nope. Não há hashtags oficiais. É uma coisa tão simples, e com um impacto tão grande, que não percebo porque é que as marcas não usam mais esta ferramenta de comunicação. #buildingthefuture #btf #buildingthefuture2025 #btf2025

  9. Queria usar hashtags, fui ver se estavam identificadas. Nope. Não há hashtags oficiais. É uma coisa tão simples, e com um impacto tão grande, que não percebo porque é que as marcas não usam mais esta ferramenta de comunicação. #buildingthefuture #btf #buildingthefuture2025 #btf2025

  10. Every challenge is just a stepping stone toward greatness. 💻 We're facing some tough coding issues right now, but we're more determined than ever to push through. Obstacles only make us stronger, and we know that every line of code gets us one step closer to something extraordinary. 🚀

    #RiseAbove #KeepPushing #TechJourney #BuildingTheFuture #RelentlessInnovation #StartupMindset

  11. It's great that Hamburg was using a former Nazi bunker in the city centre as an art and culture hub with music and other events.

    It's even better that they've made it green with an urban garden, added sports fields and exhibition areas and more!

    newatlas.com/architecture/hamb

    #CityLife #Hamburg #Germany #BuildingTheFuture