@ 56f27915:5fee3024

Ralph Boes – Menschenrechtsaktivist, Philosoph, Vorstandsmitglied im Verein Unsere Verfassung e.V.

Ralph Boes zeigt in dem Buch auf, wie wir uns von der Übermacht des Parteienwesens, die zur Entmündigung des Volkes führt, befreien können. Er zeigt, dass schon im Grundgesetz selbst höchst gegenläufige, an seinen freiheitlich-demokratischen Idealen bemessen sogar als verfassungswidrig zu bezeichnende Tendenzen wirken. Und dass diese es sind, die heute in seine Zerstörung führen. Er weist aber auch die Ansatzpunkte auf, durch die der Zerstörung des Grundgesetzes wirkungsvoll begegnet werden kann.

Eintritt frei, Spendentopf

Ralph Boes hat u.a. dafür gesorgt, dass die unmäßigen Sanktionen in Hartz IV 2019 vom Bundesverfassungsgericht für menschenrechts- und verfassungswidrig erklärt wurden. Aktuell setzt er sich für eine Ur-Abstimmung des Volkes über seine Verfassung ein.

@ ecda4328:1278f072

And what does it mean to withdraw back to Bitcoin Layer 1?

Disclaimer: This post was written with help from ChatGPT-4o. If you spot any mistakes or have suggestions — feel free to reply or zap in feedback!

Let’s break it down — using three popular setups:

---

1. Wallet of Satoshi (WoS)

Custodial — you don’t touch Lightning directly

Sending sats:

• You open WoS, paste a Lightning invoice, hit send.
• WoS handles the payment entirely within their system.
• If recipient uses WoS: internal balance update.
• If external: routed via their node.
• You never open channels, construct routes, or sign anything.

Withdrawing to L1:

• You paste a Bitcoin address.
• WoS sends a regular on-chain transaction from their custodial wallet.
• You pay a fee. It’s like a bank withdrawal.

You don’t interact with Lightning directly. Think of it as a trusted 3rd party Lightning “bank”.

---

2. Phoenix Wallet

Non-custodial — you own keys, Phoenix handles channels

Sending sats:

• You scan a Lightning invoice and hit send.
• Phoenix uses its backend node (ACINQ) to route the payment.
• If needed, it opens a real 2-of-2 multisig channel on-chain automatically.
• You own your keys (12-word seed), Phoenix abstracts the technical parts.

Withdrawing to L1:

• You enter your Bitcoin address.
• Phoenix closes your Lightning channel (cooperatively, if possible).
• Your sats are sent as a real Bitcoin transaction to your address.

You’re using Lightning “for real,” with real Bitcoin channels — but Phoenix smooths out the UX.

---

3. Your Own Lightning Node

Self-hosted — you control everything

Sending sats:

• You manage your channels manually (or via automation).
• Your node:
• Reads the invoice
• Builds a route using HTLCs
• Sends the payment using conditional logic (preimages, time locks).
• If routing fails: retry or adjust liquidity.

Withdrawing to L1:

• You select and close a channel.
• A channel closing transaction is broadcast:
• Cooperative = fast and cheap
• Force-close = slower, more expensive, and time-locked
• Funds land in your on-chain wallet.

You have full sovereignty — but also full responsibility (liquidity, fees, backups, monitoring).

---

Core Tech Behind It: HTLCs, Multisig — and No Sidechain

• Lightning channels = 2-of-2 multisig Bitcoin addresses
• Payments = routed via HTLCs (Hashed Time-Locked Contracts)
• HTLCs are off-chain, but enforceable on-chain if needed
• Important:
• The Lightning Network is not a sidechain.
• It doesn't use its own token, consensus, or separate blockchain.
• Every Lightning channel is secured by real Bitcoin on L1.

Lightning = fast, private, off-chain Bitcoin — secured by Bitcoin itself.

---

Summary Table

| Wallet | Custody | Channel Handling | L1 Withdrawal | HTLC Visibility | User Effort | |--------------------|--------------|------------------------|---------------------|------------------|--------------| | Wallet of Satoshi | Custodial | None | Internal to external| Hidden | Easiest | | Phoenix Wallet | Non-custodial| Auto-managed real LN | Channel close | Abstracted | Low effort | | Own Node | You | Manual | Manual channel close| Full control | High effort |

---

Bonus: Withdrawing from LN to On-Chain

• WoS: sends sats from their wallet — like PayPal.
• Phoenix: closes a real channel and sends your UTXO on-chain.
• Own node: closes your multisig contract and broadcasts your pre-signed tx.

---

Bitcoin + Lightning = Sovereign money + Instant payments.
Choose the setup that fits your needs — and remember, you can always level up later.

P.S. What happens in Lightning... usually stays in Lightning.

@ b0a838f2:34ed3f19

• AmuseWiki - Amusewiki is based on the Emacs Muse markup, remaining mostly compatible with the original implementation. It can work as a read-only site, as a moderated wiki, or as a fully open wiki or even as a private site. (Demo, Source Code) GPL-1.0 Perl/Docker
• BookStack - Organize and store information. Stores documentation in a book like fashion. (Demo, Source Code) MIT PHP/Docker
• django-wiki - Wiki system with complex functionality for simple integration and a superb interface. Store your knowledge with style: Use django models. (Demo) GPL-3.0 Python
• docmost - Collaborative wiki and documentation software (alternative to Confluence, Notion). (Source Code) AGPL-3.0 Docker/Nodejs
• Documize - Modern Docs + Wiki software with built-in workflow, single binary executable, just bring MySQL/Percona. (Source Code) AGPL-3.0 Go
• Dokuwiki - Easy to use, lightweight, standards-compliant wiki engine with a simple syntax allowing reading the data outside the wiki. All data is stored in plain text files, therefore no database is required. (Source Code) GPL-2.0 PHP
• Feather Wiki - A lightning fast and infinitely extensible tool for creating personal non-linear notebooks, databases, and wikis that is entirely self-contained, runs in your browser, and is only 58 kilobytes in size. (Demo, Source Code, Clients) AGPL-3.0 Javascript
• Gitit - Wiki program that stores pages and uploaded files in a git repository, which can then be modified using the VCS command line tools or the wiki's web interface. GPL-2.0 Haskell
• Gollum - Simple, Git-powered wiki with a sweet API and local frontend. MIT Ruby
• Mediawiki - Wiki software package that powers Wikipedia and all other Wikimedia projects, serving hundreds of millions of users each month. (Demo, Source Code) GPL-2.0 PHP
• Mycorrhiza Wiki - Filesystem and git-based wiki engine written in Go using Mycomarkup as its primary markup language. (Source Code) AGPL-3.0 Go
• Otter Wiki - Simple, easy to use wiki software using markdown. (Source Code) MIT Docker
• Pepperminty Wiki - Complete markdown-powered wiki contained in a single PHP file. (Demo) MPL-2.0 PHP
• PmWiki - Wiki-based system for collaborative creation and maintenance of websites. GPL-3.0 PHP
• Raneto - Raneto is an open source Knowledgebase platform that uses static Markdown files to power your Knowledgebase. (Source Code) MIT Nodejs
• TiddlyWiki - Reusable non-linear personal web notebook. (Source Code) BSD-3-Clause Nodejs
• Tiki - Wiki CMS Groupware with the most built-in features. (Demo, Source Code) LGPL-2.1 PHP
• W - Lightweight, mutli-user, flat-file-database Wiki engine. Create pages quickly and edit them in your Web browser using Mardown/HTML/CSS/JS. The main difference with other wiki is that you are encouraged to customize each page style individually. (Source Code) AGPL-3.0 PHP
• WackoWiki - WackoWiki is a light and easy to install multilingual Wiki-engine. (Source Code) BSD-3-Clause PHP
• Wiki.js - Modern, lightweight and powerful wiki app using Git and Markdown. (Demo, Source Code) AGPL-3.0 Nodejs/Docker/K8S
• WikiDocs - A databaseless markdown flat-file wiki engine. (Source Code) MIT PHP/Docker
• WiKiss - Wiki, simple to use and install. (Source Code) GPL-2.0 PHP
• Wikmd - Modern and simple file based wiki that uses Markdown and Git. MIT Python/Docker
• XWiki - Second generation wiki that allows the user to extend its functionalities with a powerful extension-based architecture. (Demo, Source Code) LGPL-2.1 Java/Docker/deb
• Zim - Graphical text editor used to maintain a collection of wiki pages. Each page can contain links to other pages, simple formatting and images. (Source Code) GPL-2.0 Python/deb

@ b0a838f2:34ed3f19

• Algernon - Small self-contained pure-Go web server with Lua, Markdown, HTTP/2, QUIC, Redis and PostgreSQL support. (Source Code) BSD-3-Clause Go/Docker
• Apache HTTP Server - Secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards. (Source Code) Apache-2.0 C/deb/Docker
• BunkerWeb - Next-gen Web Application Firewall (WAF) that will protect your web services. (Demo, Source Code, Clients) AGPL-3.0 deb/Docker/K8S/Python
• Caddy - Powerful, enterprise-ready, open source web server with automatic HTTPS. (Source Code) Apache-2.0 Go/deb/Docker
• go-doxy - Lightweight, simple, and performant reverse proxy with WebUI, Docker integration, automatic shutdown/startup for container based on traffic. MIT Docker/Go
• HAProxy - Very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications. (Source Code) GPL-2.0 C/deb/Docker
• Jauth ⚠ - Lightweight SSL/TLS reverse proxy with authorization (via Telegram and SSH) for self-hosted apps. GPL-3.0 Go
• Lighttpd - Secure, fast, compliant, and very flexible web server that has been optimized for high-performance environments. (Source Code) BSD-3-Clause C/deb/Docker
• Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface. (Source Code) MIT Docker
• NGINX - HTTP and reverse proxy server, mail proxy server, and generic TCP/UDP proxy server. (Source Code) BSD-2-Clause C/deb/Docker
• Pomerium - Identity-aware reverse proxy, successor to now obsolete oauth_proxy. It inserts an OAuth step before proxying your request to the backend, so that you can safely expose your self-hosted websites to public Internet. (Source Code) Apache-2.0 Go/Docker
• SafeLine - Web application firewall / reverse proxy to protect your web apps from attacks and exploits. (Demo, Source Code) GPL-3.0 Docker
• Static Web Server - Cross-platform, high-performance, and asynchronous web server for static file serving. (Source Code) Apache-2.0/MIT Rust/Docker
• SWAG (Secure Web Application Gateway) - Nginx webserver and reverse proxy with PHP support, built-in Certbot (Let's Encrypt) client and fail2ban integration. GPL-3.0 Docker
• Traefik - HTTP reverse proxy and load balancer that makes deploying microservices easy. (Source Code) MIT Go/Docker
• Varnish - Web application accelerator/caching HTTP reverse proxy. (Source Code) BSD-3-Clause Go/deb/Docker
• Zoraxy - General purpose HTTP reverse proxy and forwarding tool. (Source Code) AGPL-3.0 Go/Docker

@ b0a838f2:34ed3f19

• Bluecherry - Closed-circuit television (CCTV) software application which supports IP and Analog cameras. (Source Code) GPL-2.0 PHP
• Frigate - Monitor your security cameras with locally processed AI. (Source Code) MIT Docker/Python/Nodejs
• SentryShot - Video surveillance management system. GPL-2.0 Docker/Rust
• Viseron - Self-hosted, local-only NVR and AI Computer Vision software. With features such as object detection, motion detection, face recognition and more, it gives you the power to keep an eye on your home, office or any other place you want to monitor. (Source Code) MIT Docker
• Zoneminder - Closed-circuit television (CCTV) software application which supports IP, USB and Analog cameras. (Source Code) GPL-2.0 PHP/deb

@ b0a838f2:34ed3f19

• bit - Fast, lightweight, resource-efficient, compiled URL shortener. MIT Docker/Crystal
• Chhoto URL - Simple, lightning-fast URL shortener with no bloat (fork of simply-shorten). MIT Rust/Docker
• clink - A super-minimal link shortening service written in pure C, focusing on small executable size, portability, and ease of configuration. (Demo, Source Code) AGPL-3.0 C
• Flink - Create QR Codes, embeddable link previews for your website and crawls/scrapes metadata. (Demo) MIT Docker
• Just Short It! - A KISS, single-user URL shortener that runs in just one container. MIT Docker
• Kutt - Modern URL shortener with support for custom domains and custom URLs. (Demo, Source Code) MIT Nodejs/Docker
• liteshort - User-friendly, actually lightweight, and configurable URL shortener. (Source Code) MIT Python/deb
• rs-short - A lightweight link shortener written in Rust, with features such as caching, spambot protection and phishing detection. (Demo) MPL-2.0 Rust
• Shlink - URL shortener with REST API and command line interface. Includes official progressive web application and docker images. (Source Code, Clients) MIT PHP/Docker
• Simple-URL-Shortener - KISS URL shortener, public or private (with account). Minimalist and lightweight. No dependencies. (Demo) MIT PHP
• YOURLS - YOURLS is a set of PHP scripts that will allow you to run Your Own URL Shortener. Features include password protection, URL customization, bookmarklets, statistics, API, plugins, jsonp. (Source Code) MIT PHP

@ b0a838f2:34ed3f19

• ActivityWatch - Automatically track how you spend time on your devices. (Source Code) MPL-2.0 Python
• Beaver Habit Tracker - Habit tracking app to save your precious moments in your fleeting life. (Demo) BSD-3-Clause Docker
• Ever Gauzy - Open business management platform for collaborative, on-demand and sharing economies (ERP/CRM/HRM/ATS/PM). (Demo, Source Code) AGPL-3.0 Docker/Nodejs
• Kimai - Track work time and print out a summary of your activities on demand. (Demo, Source Code) AGPL-3.0 PHP
• solidtime - Modern time tracking application for freelancers and agencies. (Source Code) AGPL-3.0 Docker
• TimeTagger - An open source time-tracker based on an interactive timeline and powerful reporting. (Demo, Source Code) GPL-3.0 Python
• Traggo - Traggo is a tag-based time tracking tool. In Traggo there are no tasks, only tagged time spans. (Source Code) GPL-3.0 Docker/Go

@ b0a838f2:34ed3f19

• Bugzilla - General-purpose bugtracker and testing tool originally developed and used by the Mozilla project. (Source Code) MPL-2.0 Perl
• Frappe Helpdesk - Helpdesk software which helps you streamline your company's support, offers an easy setup, clean user interface, and automation tools to resolve customer queries efficiently. (Source Code) AGPL-3.0 Docker
• FreeScout - Email-based customer support application, help desk and shared mailbox (alternative to Zendesk and Help Scout). (Demo, Source Code) AGPL-3.0 PHP/Docker
• GlitchTip - Error tracking app to collect errors reported by your app. (Source Code) MIT Python/Docker/K8S
• ITFlow - Client IT documentation, ticketing, invoicing and accounting for MSPs (Managed Service Providers). (Demo, Source Code) GPL-3.0 PHP
• MantisBT - Bug tracker, fits best for software development. (Demo, Source Code) GPL-2.0 PHP
• OTOBO - Flexible web-based ticketing system used for customer service, help desk, IT service management. (Demo, Source Code) GPL-3.0 Perl/Docker
• Request Tracker - An enterprise-grade issue tracking system. (Source Code) GPL-2.0 Perl
• Roundup Issue Tracker - A simple-to-use and -install issue-tracking system with command-line, web, REST, XML-RPC, and e-mail interfaces. Designed with flexibility in mind - not just another bug tracker. (Source Code) MIT/ZPL-2.0 Python/Docker
• Trudesk - Trudesk is an open-source help desk/ticketing solution. (Source Code) Apache-2.0 Nodejs/Docker
• Zammad - Easy to use but powerful open-source support and ticketing system. (Source Code) AGPL-3.0 Ruby/deb

@ b0a838f2:34ed3f19

• 4ga Boards - Straightforward realtime kanban boards management for intuitive task tracking. Featuring an elegant dark mode, collapsible todo lists, and multitasking tools to supercharge your team's productivity. (Demo, Source Code) MIT Nodejs/Docker/K8S
• AppFlowy - Build detailed lists of to-do’s for different projects while tracking the status of each one. Open Source Notion Alternative. (Source Code) AGPL-3.0 Rust/Dart/Docker
• Donetick - Task and chore management tool for personal and family use, with advanced scheduling, flexible assignment, and group sharing capabilities, detailed history, automation via API, simple and modern design. (Demo, Source Code) AGPL-3.0 Go/Docker
• Focalboard - Define, organize, track and manage work across individuals and teams (alternative to Trello, Notion, and Asana). (Source Code, Clients) MIT/AGPL-3.0/Apache-2.0 Nodejs/Go/Docker
• Kanboard - Simple visual task board. (Source Code) MIT PHP
• myTinyTodo - Simple way to manage your todo list in AJAX style. Uses PHP, jQuery, SQLite/MySQL. GTD compliant. (Demo, Source Code) GPL-2.0 PHP
• Nullboard - Single-page minimalist kanban board; compact, highly readable and quick to use. (Demo) BSD-2-Clause Javascript
• Our Shopping List - Simple shared list application including shopping lists and any other small todo-list that needs to be used collaboratively. (Demo) AGPL-3.0 Docker
• Planka - Realtime kanban board for workgroups (alternative to Trello). (Demo, Source Code) AGPL-3.0 Nodejs/Docker/K8S
• Task Keeper - List editor for power users, backed by a self-hosted server. Apache-2.0 Scala
• Tasks.md - A self-hosted, file based task management board that supports Markdown syntax. MIT Docker
• Taskwarrior - Taskwarrior is Free and Open Source Software that manages your TODO list from your command line. It is flexible, fast, efficient, and unobtrusive. It does its job then gets out of your way. (Source Code) MIT C++
• Tegon ⚠ - Dev-first issue tracking tool (alternative to Jira, Linear). (Source Code) AGPL-3.0 Docker
• Tracks - Web-based application to help you implement David Allen’s Getting Things Done™ methodology. (Source Code) GPL-2.0 Ruby
• Vikunja - The to-do app to organize your life. (Demo, Source Code) GPL-3.0 Go
• Wekan - Open-source Trello-like kanban. (Source Code) MIT Nodejs

@ b0a838f2:34ed3f19

• cState - Static status page for hyperfast Hugo. Clean design, minimal JS, super light HTML/CSS, high customization, optional admin panel, read-only API, IE8+. Best used with Netlify, Docker. (Demo, Source Code) MIT Go
• Gatus - Automated service health dashboard. (Demo, Source Code) Apache-2.0 Docker/K8S
• kener - Status page with incident management, easy to use and customize. (Demo, Source Code) MIT Nodejs/Docker
• StatPing.ng - An easy to use Status Page for your websites and applications. Statping will automatically fetch the application and render a beautiful status page with tons of features for you to build an even better status page. (Source Code) GPL-3.0 Docker/Go
• Uptime Kuma - Self-hosted website monitoring tool like "Uptime Robot". (Demo, Source Code) MIT Docker/Nodejs

@ b0a838f2:34ed3f19

• Bencher - Suite of continuous benchmarking tools designed to catch performance regressions in CI. (Source Code) MIT/Apache-2.0 Rust
• WebHook Tester - Powerful tool for testing WebHooks and more. MIT Docker/Go/deb/K8S

@ b0a838f2:34ed3f19

• Cgit - Fast lightweight web interface for git repositories. (Source Code) GPL-2.0 C
• Forgejo - A lightweight software forge focused on scaling, federation, and privacy (fork of Gitea). (Demo, Source Code, Clients) MIT Docker/Go
• Fossil - Distributed version control system featuring wiki and bug tracker. BSD-2-Clause-FreeBSD C
• Gerrit - Code review and project management tool for Git-based projects. (Source Code) Apache-2.0 Java/Docker
• gitbucket - Git platform powered with easy installation, high extensibility & GitHub API compatibility (alternative to GitHub). (Source Code) Apache-2.0 Scala/Java
• Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. (Demo, Source Code) MIT Go/Docker/K8S
• GitLab - Self Hosted Git repository management, code reviews, issue tracking, activity feeds and wikis. (Demo, Source Code) MIT Ruby/deb/Docker/K8S
• Gitolite - Setup git hosting on a central server, with fine-grained access control and many more powerful features. (Source Code) GPL-2.0 Perl
• Gogs - Painless self-hosted Git Service written in Go. (Source Code) MIT Go
• Huly - All-in-one project management platform (alternative to Linear, Jira, Slack, Notion, Motion). (Demo, Source Code) EPL-2.0 Docker/K8S/Nodejs
• Kallithea - Source code management system that supports two leading version control systems, Mercurial and Git, with a web interface. (Source Code) GPL-3.0 Python
• Klaus - Simple, easy-to-set-up Git web viewer that Just Works. ISC Python/Docker
• Leantime - Lean project management system for small teams and startups helping to manage projects from ideation through delivery. (Source Code) AGPL-3.0 PHP/Docker
• Mergeable ⚠ - A better inbox for GitHub pull requests. (Demo, Source Code) MIT Nodejs/Docker/K8S
• Mindwendel - Brainstorm and upvote ideas and thoughts within your team. (Demo, Source Code) AGPL-3.0 Docker/Elixir
• minimal-git-server - Lightweight git server with a basic CLI to manage repositories, supporting multiple accounts and running in a container. MIT Docker
• Octobox ⚠ - Take back control of your GitHub Notifications. (Source Code) AGPL-3.0 Ruby/Docker
• OneDev - All-In-One DevOps Platform. With Git Management, Issue Tracking, and CI/CD. Simple yet Powerful. (Source Code) MIT Java/Docker/K8S
• OpenProject - Manage your projects, tasks and goals. Collaborate via work packages and link them to your pull requests on Github. (Source Code) GPL-3.0 Ruby/deb/Docker
• Pagure - Lightweight, powerful, and flexible git-centric forge with features laying the foundation for federated and decentralized development. (Demo) GPL-2.0 Docker/Python/deb
• Phorge - Community-driven platform for collaborating, managing, organizing and reviewing software development projects. (Source Code) Apache-2.0 PHP
• Plane - Track issues, epics, and product roadmaps in the simplest way possible (alternative to JIRA, Linear and Height). (Demo, Source Code) AGPL-3.0 Docker
• ProjeQtOr - Complete, mature, multi-user project management system with extensive functionality for all phases of a project. (Demo, Source Code) AGPL-3.0 PHP
• Redmine - Redmine is a flexible project management web application. (Source Code) GPL-2.0 Ruby
• Review Board - Extensible and friendly code review tool for projects and companies of all sizes. (Demo, Source Code) MIT Python/Docker
• rgit - An ultra-fast & lightweight cgit clone. WTFPL Rust/Docker
• RhodeCode - RhodeCode is an open source platform for software development teams. It unifies and simplifies repository management for Git, Subversion, and Mercurial. (Source Code) AGPL-3.0 Python
• Rukovoditel - Configurable open source project management, web-based application. (Source Code) GPL-2.0 PHP
• SCM Manager - The easiest way to share and manage your Git, Mercurial and Subversion repositories over http. (Source Code) BSD-3-Clause Java/deb/Docker/K8S
• Smederee - A frugal platform which is dedicated to help people build great software together leveraging the power of the Darcs version control system. (Source Code) AGPL-3.0 Scala
• Sourcehut - A full web git interface with no javascript. (Demo, Source Code) GPL-2.0 Go
• Taiga - Agile Project Management Tool based on the Kanban and Scrum methods. (Source Code) MPL-2.0 Docker/Python/Nodejs
• Titra - Time-tracking solution for freelancers and small teams. (Source Code) GPL-3.0 Javascript/Docker
• Trac - Trac is an enhanced wiki and issue tracking system for software development projects. BSD-3-Clause Python/deb
• Traq - Project management and issue tracking system written in PHP. (Source Code) GPL-3.0 PHP/Nodejs
• Tuleap - Tuleap is a libre suite to plan, track, code and collaborate on software projects. (Source Code) GPL-2.0 PHP
• UVDesk - UVDesk community is a service oriented, event driven extensible opensource helpdesk system that can be used by your organization to provide efficient support to your clients effortlessly whichever way you imagine. (Demo, Source Code) MIT PHP
• ZenTao - An agile(scrum) project management system/tool. (Source Code) AGPL-3.0 PHP

@ b0a838f2:34ed3f19

• Appsmith - Build admin panels, CRUD apps and workflows. Build everything you need, 10x faster. (Source Code) Apache-2.0 Java/Docker/K8S
• Appwrite - End to end backend server for web, native, and mobile developers 🚀. (Source Code) BSD-3-Clause Docker
• Dashpress - Generate fully functional admin apps in seconds from your database information, with a single command. AGPL-3.0 Nodejs/Docker
• Manifest - Complete backend that fits into 1 YAML file. (Demo, Source Code) MIT Nodejs
• Motor Admin - No-code admin panel and business intelligence software - search, create, update, and delete data entries, create custom actions, and build reports. (Source Code) AGPL-3.0 Ruby/Docker
• PocketBase - Backend for your next SaaS and Mobile app in one file. (Source Code) MIT Go/Docker
• SQLPage - SQL-only dynamic website builder. (Source Code) MIT Rust/Docker
• ToolJet - Low-code framework to build & deploy internal tools with minimal engineering effort (alternative to Retool & Mendix). (Source Code) GPL-3.0 Nodejs/Docker/K8S
• TrailBase - Open, sub-millisecond, single-executable FireBase alternative with type-safe REST & realtime APIs, built-in JS/TS runtime, auth & admin UI. (Demo, Source Code) OSL-3.0 Rust/Docker

@ b0a838f2:34ed3f19

• Accent - Developer-oriented translation tool. (Source Code) BSD-3-Clause Elixir/Docker
• Tolgee - Developer & translator friendly web-based localization platform enabling users to translate directly in the app they develop. (Source Code) Apache-2.0 Docker/Java
• Traduora - Translation management platform for teams. (Source Code) AGPL-3.0 Docker/K8S/Nodejs
• Weblate - Web-based translation tool with tight version control integration. (Source Code) GPL-3.0 Python/Docker/K8S

@ b0a838f2:34ed3f19

• Atheos - Web-based IDE framework with a small footprint and minimal requirements, continued from Codiad. (Source Code) MIT PHP/Docker
• code-server - VS Code in the browser, hosted on a remote server. MIT Nodejs/Docker
• Coder - Remote development machines on your own infrastructure. (Source Code) AGPL-3.0 Go/Docker/K8S/deb
• Eclipse Che - Open source workspace server and cloud IDE. (Source Code) EPL-1.0 Docker/Java
• HttPlaceholder - Quickly mock away any webservice using HttPlaceholder. HttPlaceholder lets you specify what the request should look like and what response needs to be returned. MIT C#
• Judge0 CE - API to compile and run source code. (Source Code) GPL-3.0 Docker
• JupyterLab - Web-based environment for interactive and reproducible computing. (Demo, Source Code) BSD-3-Clause Python/Docker
• Langfuse - LLM engineering platform for model tracing, prompt management, and application evaluation. Langfuse helps teams collaboratively debug, analyze, and iterate on their LLM applications such as chatbots or AI agents. (Demo, Source Code, Clients) MIT Docker
• LiveCodes ⚠ - Feature-rich client-side code playground for React, Vue, Svelte, Solid, Typescript, Python, Go, Ruby, PHP and 90+ other languages. (Demo, Source Code) MIT Nodejs
• Lowdefy - Build internal tools, BI dashboards, admin panels, CRUD apps and workflows in minutes using YAML / JSON on an self-hosted, open-source platform. Connect to your data sources, host via Serverless, Netlify or Docker. (Source Code) Apache-2.0 Nodejs/Docker
• RStudio Server - Web browser based IDE for R. (Source Code) AGPL-3.0 Java/C++
• Wakapi - Tracking tool for coding statistics, compatible with WakaTime. (Source Code) GPL-3.0 Go/Docker

@ b0a838f2:34ed3f19

• Featbit - Enterprise-grade feature flag platform that you can self-host. (Source Code) MIT Docker/K8S
• Flagsmith - Dashboard, API and SDKs for adding Feature Flags to your applications (alternative to LaunchDarkly). (Source Code) BSD-3-Clause Docker/K8S
• Flipt - Feature flag solution with support for multiple data backends (alternative to LaunchDarkly). (Demo, Source Code) GPL-3.0 Docker/K8S/Go
• GO Feature Flag - Simple, complete, and lightweight feature flag solution (alternative to LaunchDarkly). (Source Code) MIT Go

@ b0a838f2:34ed3f19

• DreamFactory - Turns any SQL/NoSQL/Structured data into Restful API. (Source Code) Apache-2.0 PHP/Docker/K8S
• form.io - A REST API building platform that utilizes a drag & drop form builder, and is application framework agnostic. Contains open source and enterprise version. (Demo, Source Code) MIT Nodejs/Docker
• Fusio - Open-source API management platform which helps to build and manage REST APIs. (Demo, Source Code) AGPL-3.0 PHP/Docker
• Graphweaver - Turn multiple data sources into a single GraphQL API. (Source Code) MIT Nodejs
• Hasura - Fast, instant realtime GraphQL APIs on Postgres with fine grained access control, also trigger webhooks on database events. (Source Code) Apache-2.0 Haskell/Docker/K8S
• Hoppscotch Community Edition - Fast and beautiful API request builder. (Source Code) MIT Nodejs/Docker
• Kong - Microservice API Gateway and Platform. (Source Code) Apache-2.0 Lua/Docker/K8S/deb
• Lura - High-performance API Gateway. (Source Code) Apache-2.0 Go
• Opik ⚠ - Evaluate, test, and ship LLM applications with a suite of observability tools to calibrate language model outputs across your dev and production lifecycle. (Source Code) Apache-2.0 Docker/Python
• Panora ⚠ - Add an integration catalog to your SaaS product in minutes (alternative to Merge.dev). (Source Code) AGPL-3.0 Nodejs/Docker
• Para - Flexible and modular backend framework/server for object persistence, API development and authentication. (Source Code) Apache-2.0 Java/Docker
• Svix - Open-source webhooks as a service that makes it super easy for API providers to send webhooks. (Source Code) MIT Docker/Rust
• Tyk - Fast and scalable open source API Gateway. Out of the box, Tyk offers an API Management Platform with an API Gateway, API Analytics, Developer Portal and API Management Dashboard. (Source Code) MPL-2.0 Go/Docker/K8S
• Yaade - Yaade is an open-source, self-hosted, collaborative API development environment. (Source Code) MIT Docker

@ b0a838f2:34ed3f19

• Ansible-NAS - Build a full-featured home server with this playbook and an Ubuntu box. MIT Ansible/Docker
• CasaOS - Simple, easy-to-use, elegant Home Cloud system. (Source Code) Apache-2.0 Go/Docker
• DietPi - Minimal Debian OS optimized for single-board computers, which allows you to easily install and manage several services for selfhosting at home. (Source Code) GPL-2.0 Shell
• DockSTARTer - DockSTARTer helps you get started with home server apps running in Docker. (Source Code) MIT Shell
• Dropserver - An application platform for your personal web services. (Source Code) Apache-2.0 Go/Deno
• FreedomBox - Community project to develop, design and promote personal servers running free software for private, personal, communications. (Source Code) AGPL-3.0 Python/deb
• HomelabOS - Offline privacy-centric data-center. Deploy over 100 services with a few commands. (Source Code) MIT Docker
• HomeServerHQ - All-in-one home server infrastructure and installer. Have a fully configured email server, VPN, and public website(s) set up in less than an hour, even behind CGNAT. (Source Code) GPL-3.0 Shell
• LibreServer - Home server configuration based on Debian. (Source Code) AGPL-3.0 Shell
• Mars Server - Managed home server with Docker, Docker Compose, Make and Bash. MIT Docker
• Mistborn - Virtual private cloud platform and WebUI that manages self hosted services. MIT Shell/Docker
• NextCloudPi - Nextcloud preinstalled and preconfigured, with a text and web management interface and all the tools needed to self host private data. With installation images for Raspberry Pi, Odroid, Rock64, Docker, and a curl installer for Armbian/Debian. GPL-2.0 Shell/PHP
• OpenMediaVault - Network attached storage (NAS) solution based on Debian Linux. It contains services like SSH, (S)FTP, SMB/CIFS, DAAP media server, RSync, BitTorrent client and many more. (Source Code) GPL-3.0 PHP
• Sandstorm - Personal server for running self-hosted apps easily and securely. (Demo, Source Code) Apache-2.0 C++/Shell
• Self Host Blocks ⚠ - Modular server management based on NixOS modules and focused on best practices. AGPL-3.0 Nix
• StartOS - Browser-based, graphical Operating System (OS) that makes running a personal server as easy as running a personal computer. (Source Code) MIT Rust
• Syncloud - Your own online file storage, social network or email server. (Source Code) GPL-3.0 Go/Shell
• Tipi - Homeserver manager. One command setup, one click installs for your favorites self-hosted apps. (Source Code) GPL-3.0 Shell
• UBOS - Linux distro that runs on indie boxes (personal servers and IoT devices). Single-command installation and management of apps - Jenkins, Mediawiki, Owncloud, WordPress, etc., and other features. GPL-3.0 Perl
• Websoft9 ⚠ - GitOps-driven, multi-application hosting for cloud servers and home servers, one-click deployment of 200+ open source apps. (Demo, Source Code, Clients) LGPL-3.0 Shell/Python
• WikiSuite - The most comprehensive and integrated Free / Libre / Open Source enterprise software suite. (Source Code) GPL-3.0/LGPL-2.1/Apache-2.0/MPL-2.0/MPL-1.1/MIT/AGPL-3.0 Shell/Perl/deb
• xsrv - Install and manage self-hosted services/applications, on your own server(s). (Source Code) GPL-3.0 Ansible/Shell
• YunoHost - Server operating system aiming to make self-hosting accessible to everyone. (Demo, Source Code) AGPL-3.0 Python/Shell

@ b0a838f2:34ed3f19

• Aleph - Tool for indexing large amounts of both documents (PDF, Word, HTML) and structured (CSV, XLS, SQL) data for easy browsing and search. It is built with investigative reporting as a primary use case. (Demo, Source Code) MIT Docker/K8S
• Apache Solr - Enterprise search platform featuring full-text search, hit highlighting, faceted search, real-time indexing, dynamic clustering, and rich document (e.g., Word, PDF) handling. (Source Code) Apache-2.0 Java/Docker/K8S
• Fess - Powerful and easily deployable Enterprise Search Server. (Demo, Source Code) Apache-2.0 Java/Docker
• Jina - Cloud-native neural search framework for any kind of data. Apache-2.0 Python/Docker
• Manticore Search - Full-text search and data analytics, with fast response time for small, medium and big data (alternative to Elasticsearch). GPL-3.0 Docker/deb/C++/K8S
• MeiliSearch - Ultra relevant, instant and typo-tolerant full-text search API. (Source Code) MIT Rust/Docker/deb
• OpenSearch - Distributed and RESTful search engine. (Source Code) Apache-2.0 Java/Docker/K8S/deb
• SearXNG ⚠ - Internet metasearch engine which aggregates results from various search services and databases (Fork of Searx). (Source Code) AGPL-3.0 Python/Docker
• sist2 - Lightning-fast file system indexer and search tool. GPL-3.0 C/Docker
• Sosse - Selenium based search engine and crawler with offline archiving. (Source Code) AGPL-3.0 Python/Docker
• Typesense - Blazing fast, typo-tolerant open source search engine optimized for developer happiness and ease of use. (Source Code) GPL-3.0 C++/Docker/K8S/deb
• Websurfx ⚠ - Aggregate results from other search engines (metasearch engine) without ads while keeping privacy and security in mind. It is extremely fast and provides a high level of customization (alternative to SearX). AGPL-3.0 Rust/Docker
• Whoogle ⚠ - A self-hosted, ad-free, privacy-respecting metasearch engine. MIT Python
• Yacy - Peer based, decentralized search engine server. (Source Code) GPL-2.0 Java/Docker/K8S
• ZincSearch - Search engine that requires minimal resources (alternative to Elasticsearch). (Demo, Source Code) Apache-2.0 Go/Docker/K8S

@ b0a838f2:34ed3f19

• Dolibarr - Modern CRM software package to manage your company or foundation activity (contacts, suppliers, invoices, orders, stocks, agenda, accounting, ...). (Demo, Source Code) GPL-3.0 PHP/deb
• ERPNext - ERP system to help you run your business. (Source Code) GPL-3.0 Python/Docker
• farmOS - Web-based farm record keeping application. (Demo, Source Code) GPL-2.0 PHP/Docker
• grocy - ERP beyond your fridge. Groceries & household management solution for your home. (Demo, Source Code) MIT PHP/Docker
• LedgerSMB - Integrated accounting and ERP system for small and midsize businesses, with double entry accounting, budgeting, invoicing, quotations, projects, orders and inventory management, shipping and more. (Demo, Source Code) GPL-2.0 Docker/Perl
• Odoo - Free open source ERP system. (Demo, Source Code) LGPL-3.0 Python/deb/Docker
• OFBiz - Enterprise Resource Planning system with a suite of business applications flexible enough to be used across any industry. (Source Code) Apache-2.0 Java
• Tryton - Free open source business solution. (Demo, Source Code) GPL-3.0 Python

@ b0a838f2:34ed3f19

• Engity's Bifröst - Highly customizable SSH server with several ways to authorize a user and options where and how to execute a user's session. (Source Code) Apache-2.0 Go/Docker
• Firezone - Secure remote access gateway that supports the WireGuard protocol. It offers a Web GUI, 1-line install script, multi-factor auth (MFA), and SSO. (Source Code) Apache-2.0 Elixir/Docker
• Guacamole - Clientless remote desktop gateway supporting standard protocols like VNC and RDP. (Source Code) Apache-2.0 Java/C
• MeshCentral - Run your own web server to remotely manage and control computers on a local network or anywhere on the internet. (Source Code) Apache-2.0 Nodejs
• Remotely - A remote desktop control and remote scripting solution, enterprise level remote support solution with admin web interface and remote control via browser. GPL-3.0 C#/Docker
• RustDesk - Remote Desktop Access software that works out-of-the-box (alternative to TeamViewer). (Source Code) AGPL-3.0 Rust/Docker/deb
• ShellHub - ShellHub is a modern SSH server for remotely accessing linux devices via command line (using any SSH client) or web-based user interface, designed as an alternative to sshd. (Source Code) Apache-2.0 Docker
• Sshwifty - Sshwifty is a SSH and Telnet connector made for the Web. (Demo) AGPL-3.0 Go/Docker
• Warpgate - Smart SSH and HTTPS bastion that works with any SSH client. Apache-2.0 Rust/Docker

@ b0a838f2:34ed3f19

• Bar Assistant - Manage your home bar while adding your ingredients, searching for cocktails and creating custom cocktail recipes. (Demo, Source Code) MIT PHP/Docker
• Fork Recipes - Manage your food recipes with simplicity. (Source Code) BSD-3-Clause Docker
• KitchenOwl - Cross-platform shopping list, recipe storage, expense tracker, and meal planner following the material design language. (Source Code) AGPL-3.0 Docker/deb
• ManageMeals - Manage recipes, import recipes by URL and organize them without any ads or unnecessary text. (Demo, Source Code) GPL-3.0 Docker
• Mealie - Material design inspired recipe manager with category and tag management, shopping-lists, meal-planner, and site customizations. Mealie is focused on simple user interactions to keep the whole family using the app. (Source Code) MIT Python
• RecipeSage - A recipe keeper, meal plan organizer, and shopping list manager that can import recipes directly from any URL. (Demo) AGPL-3.0 Nodejs
• Recipya - A clean, simple and powerful recipe manager your whole family will enjoy. (Demo, Source Code) GPL-3.0 Docker/Go
• Specifically Clementines - Grocery shopping app (previously Groceries), providing reliable sync with multiple users/devices (web/Android/iOS), recipes and integration with Tandoor. (Source Code) MIT Docker
• Tamari - Recipe manager web app with a built-in collection of recipes. Organize by favorites and categories, create shopping lists, and plan meals. (Demo, Source Code) GPL-3.0 Docker/Python
• What To Cook? - Get a recipe to cook today, based on the ingredients you have at home. AGPL-3.0 Docker

@ b0a838f2:34ed3f19

• imgproxy - Fast and secure standalone server for resizing and converting remote images. (Source Code) MIT Go/Docker/K8S
• iodine - IPv4 over DNS tunnel solution, enabling you to start up a socks5 proxy listener. (Source Code) ISC C/deb
• Koblas - Lightweight SOCKS5 proxy server. MIT Rust/Docker
• Outline Server - A proxy server that runs a Shadowsocks instance for each access key and a REST API to manage the access keys. (Source Code) Apache-2.0 Docker/Nodejs
• Privoxy - Non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk. GPL-2.0 C/deb
• sish - HTTP(S)/WS(S)/TCP tunnels to localhost using only SSH (serveo/ngrok alternative). MIT Go/Docker
• socks5-proxy-server - SOCKS5 proxy server with built-in authentication and Telegram-bot for user management and user statistics on data spent (handy when you pay per GB of data). It is dockerised and simple to install. Apache-2.0 Docker
• Squid - Caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. (Source Code) GPL-2.0 C/deb
• Tinyproxy - Light-weight HTTP/HTTPS proxy daemon. (Source Code) GPL-2.0 C/deb
• txtdot - A HTTP proxy that parses only text, links and pictures from pages reducing internet bandwidth usage, removing ads and heavy scripts. (Demo, Source Code) MIT Nodejs/Docker

@ b0a838f2:34ed3f19

• Bitpoll - Conduct polls about dates, times or general questions. (Demo) GPL-3.0 Docker/Python
• Bracket - Flexible tournament system to build a tournament setup, add teams, schedule matches, keep track of scores and present ranking live to the public. (Demo, Source Code) AGPL-3.0 Docker/Nodejs
• Christmas Community - Create a simple place for your entire family to use to find gifts that people want, and to avoid double-gifting. AGPL-3.0 Docker/Nodejs
• Claper - The ultimate tool to interact with your audience (alternative to Slido, AhaSlides and Mentimeter). (Source Code) GPL-3.0 Elixir/Docker
• ClearFlask - Community-feedback tool for managing incoming feedback and prioritizing a public roadmap (alternative to Canny, UserVoice, Upvoty). (Demo, Source Code) AGPL-3.0 Docker
• docassemble - A free, open-source expert system for guided interviews and document assembly, based on Python, YAML, and Markdown. (Demo, Source Code) MIT Docker/Python
• Fider - Open platform to collect and prioritize feedback (alternative to UserVoice). (Demo, Source Code) MIT Docker
• Formbricks - Experience Management Suite built on the largest open source survey stack worldwide. Gracefully gather feedback at every step of the customer journey to know what your customers need. (Demo, Source Code) AGPL-3.0 Nodejs/Docker
• Framadate - Online service for planning an appointment or make a decision quickly and easily: Make a poll, Define dates or subjects to choose, Send the poll link to your friends or colleagues, Discuss and make a decision. (Demo, Source Code) CECILL-B PHP
• Gancio - Local community event and agenda sharing. (Demo, Source Code) AGPL-3.0 Nodejs
• gathio - Self-destructing, shareable, no-registration event pages. (Demo, Source Code) GPL-3.0 Nodejs/Docker
• HeyForm - Form builder that allows anyone to create engaging conversational forms for surveys, questionnaires, quizzes, and polls. (Source Code) AGPL-3.0 Docker
• hitobito - Manage complex group hierarchies with members, events and a lot more. (Demo, Source Code) AGPL-3.0 Ruby
• Input - Privacy-focused, no-code, open-source form builder designed for simplicity and brand consistency. (Source Code) AGPL-3.0 PHP/Nodejs/Docker
• LimeSurvey - Feature-rich web-based polling software. Supports extensive survey logic. (Demo, Source Code) GPL-2.0 PHP
• Meetable - Minimal events aggregator. (Source Code) MIT PHP
• Mobilizon - Federated tool that helps you find, create and organise events and groups. (Source Code) AGPL-3.0 Elixir/Docker
• OpnForm - Beautiful open-source form builder. (Demo, Source Code) AGPL-3.0 PHP/Nodejs/Docker

@ b0a838f2:34ed3f19

• Chevereto - Ultimate image sharing software. Create your very own personal image hosting website in just minutes. (Source Code) AGPL-3.0 PHP/Docker
• Coppermine - Multilingual photo gallery that integrates with various bulletin boards. Includes upload approval and password protected albums. (Source Code) GPL-3.0 PHP
• Damselfly - Fast server-based photo management system for large collections of images. Includes face detection, face & object recognition, powerful search, and EXIF Keyword tagging. Runs on Linux, MacOS and Windows. (Source Code) GPL-3.0 Docker/C#/.NET
• Ente - An end-to-end encrypted photo-sharing platform (alternative to Google Photos, Apple Photos). (Source Code) AGPL-3.0 Docker/Nodejs/Go
• HomeGallery - Browse personal photos and videos featuring tagging, mobile-friendly, and AI powered image discovery. (Demo, Source Code) MIT Nodejs/Docker
• Immich Kiosk - Lightweight slideshow for running on kiosk devices and browsers that uses Immich as a data source. GPL-3.0 Docker/Go
• Immich - Photo and video backup solution directly from your mobile phone. (Demo, Source Code) AGPL-3.0 Docker
• LibrePhotos - Photo management service with a slight focus on cool graphs (alternative to Google Photos). (Clients) MIT Python/Docker
• Lychee - Grid and album based photo-management-system. (Source Code) MIT PHP/Docker
• Mediagoblin - Media publishing platform that anyone can run (alternative to Flickr, YouTube, SoundCloud, etc). (Source Code) AGPL-3.0 Python
• Mejiro - Easy-to-use instant photo publishing. GPL-3.0 PHP
• Nextcloud Memories - Fast, modern and advanced photo management suite. Runs as a Nextcloud app. (Demo, Source Code) AGPL-3.0 PHP
• Photofield - Experimental fast photo viewer. MIT Docker/Go
• PhotoPrism - Personal photo management powered by Go and Google TensorFlow. Browse, organize, and share your personal photo collection, using the latest technologies to automatically tag and find pictures. (Demo, Source Code) AGPL-3.0 Go/Docker
• Photoview - Simple and user-friendly photo gallery for personal servers. It is made for photographers and aims to provide an easy and fast way to navigate directories, with thousands of high resolution photos. (Source Code) GPL-3.0 Go/Docker
• PiGallery 2 - Directory-first photo gallery website, with a rich UI, optimised for running on low resource servers. (Source Code) MIT Docker/Nodejs
• Piwigo - Photo gallery software for the web, built by an active community of users and developers. (Source Code) GPL-2.0 PHP
• sigal - Yet another simple static gallery generator. MIT Python
• SPIS - A simple, lightweight and fast media server with decent mobile support. GPL-3.0 Docker/Rust
• This week in past - Aggregates images taken this week, from previous years and presents them on a web page with a simple slideshow. MIT Docker/Rust
• Thumbor - A smart imaging service and enables on-demand cropping, resizing, applying filters and optimizing images. (Source Code) MIT Python/Docker
• Zenphoto - Open-source gallery and CMS project. (Source Code) GPL-2.0 PHP

@ b0a838f2:34ed3f19

• Dashy - Feature-rich homepage for your homelab, with easy YAML configuration. (Demo, Source Code) MIT Nodejs/Docker
• Fenrus - Personal home page that allows for multiple users, guest access and multiple dashboards for each user. It also has "Smart Apps" which display live data for those apps. GPL-3.0 .NET/Docker
• Glance - Highly customizable dashboard that puts all your feeds in one place. AGPL-3.0 Docker/Go
• Heimdall - Elegant solution to organise all your web applications. (Source Code) MIT PHP
• Hiccup - Beautiful static homepage to get to your links and services quickly. It has built-in search, editing, PWA support and localstorage caching to easily organize your start page. (Source Code) MIT Javascript/Docker
• Homarr - Sleek, modern dashboard with many integrations and web-based config. (Source Code) MIT Docker/Nodejs
• Homepage by gethomepage - Highly customizable homepage (or startpage / application dashboard) with Docker and service API integrations. GPL-3.0 Docker/Nodejs
• Homepage by tomershvueli - Simple, standalone, self-hosted PHP page that is your window to your server and the web. MIT PHP
• Homer - Dead simple static homepage to expose your server services, with an easy yaml configuration and connectivity check. Apache-2.0 Docker/K8S/Nodejs
• Hubleys - Personal dashboards to organize links for multiple users via a central yaml config. MIT Docker
• LinkStack - Link all your social media platforms easily accessible on one page, customizable through an intuitive, easy to use user/admin interface (alternative to Linktree and Manylink). (Demo, Source Code) AGPL-3.0 PHP/Docker
• LittleLink - Simplistic approach for links in bio with 100+ branded buttons (alternative to Linktree). (Demo, Source Code) MIT Javascript
• Mafl - Minimalistic flexible homepage. (Source Code) MIT Docker/Nodejs
• portkey - Simple web portal that serves as a startup page, displaying a compilation of links and URLs, while also allowing the addition of custom pages, all managed through a single configuration file. (Demo, Source Code) AGPL-3.0 Go/Docker
• ryot - Platform for tracking various facets of your life - media, fitness, etc. (Demo) GPL-3.0 Docker
• Starbase 80 - A simple homepage with an iPad-style application grid, for mobile and desktop. One JSON configuration file. MIT Docker
• Web-Portal - A python web app designed to allow a easy way to manage the links to all of your web services. AGPL-3.0 Docker/Python
• Your Spotify ⚠ - Allows you to record your Spotify listening activity and have statistics about them served through a Web application. MIT Nodejs/Docker

@ b0a838f2:34ed3f19

• bin - A paste bin that's actually minimalist. WTFPL/0BSD Rust
• BinPastes - Minimal pastebin supporting client-side encryption, fulltext search, one-time messages. Intended for one to few users looking for a simple pastebin deployment. (Demo) Apache-2.0 Java
• ByteStash - Pastebin and file storage service with a simple web interface. Supports syntax highlighting, optional user authentication and public sharing. (Demo) GPL-3.0 Docker
• dpaste - Simple pastebin with multiple text and code option, with short url result easy to remember. (Source Code) MIT Docker/Django
• FlashPaper - One-time encrypted zero-knowledge password/secret sharing application focused on simplicity and security. No database or complicated set-up required. (Demo) MIT Docker/PHP
• Hemmelig - Share encrypted secrets cross organizations, or as private persons. (Source Code) MIT Docker/Nodejs
• lesma - Simple paste app friendly with browser and command line. (Demo, Source Code) GPL-3.0 Rust/Docker
• Local Content Share - Store and share text snippets and files within your local network. MIT Docker/Go
• not-th.re - Simple paste sharing platform, with client side encryption, featuring the monaco browser-based code editor. (Demo, Source Code) AGPL-3.0 Nodejs/Docker
• Opengist - Pastebin powered by Git. (Demo) AGPL-3.0 Docker/Go/Nodejs
• paaster - End-to-end encrypted pastebin built with the objective of simplicity. (Source Code) AGPL-3.0 Docker
• pacebin - Super-minimal pastebin and file upload service focusing on small executable size, portability, and ease of configuration. (Demo, Source Code) AGPL-3.0 C
• Password Pusher - Dead-simple application to securely communicate passwords (or text) over the web. Passwords automatically expire after a certain number of views and/or time has passed. (Source Code) Apache-2.0 Docker/K8S/Ruby
• Pastefy - Beautiful, simple and easy to deploy Pastebin with optional client encryption, multitab pastes, an API, a highlighted editor and more. (Source Code, Clients) MIT Docker/K8S/Java
• PrivateBin - Minimalist pastebin/discussion board where the server has zero knowledge of hosted data. (Demo, Source Code) Zlib PHP
• rustypaste - A minimal file upload/pastebin service. MIT Rust
• SnyPy - Open source on-prem code snippet manager. (Demo, Source Code) MIT Docker
• Spacebin - Modern Pastebin server written in Go with a JS-free web UI and tons of features. (Demo, Source Code) Apache-2.0 Go/Docker
• Sup3rS3cretMes5age - Very simple (to deploy and to use) secret message service using Hashicorp Vault as a secrets storage. MIT Go
• Wastebin - Lightweight, minimal and fast pastebin with an SQLite backend. (Demo) MIT Rust/Docker
• YABin - A pastebin that contains plentiful features while remaining simple. Supports optional E2E encryption, a client-side CLI app, syntax highlighting, minimalistic UI, APIs, keyboard shortcuts, and more. It can even be run in serverless environments. (Demo) MIT Nodejs/Docker
• ybFeed - Personal micro feed where you can post snippets of text or images. MIT Go/Nodejs/Docker
• Yopass - Secure sharing of secrets, passwords and files. (Demo) Apache-2.0 Go/Docker

@ b0a838f2:34ed3f19

• AliasVault - End-to-end encrypted password manager with a built-in email alias generator and server. (Source Code) MIT Docker
• Bitwarden ⚠ - Password manager with a webapp, browser extension, and mobile app. (Source Code) AGPL-3.0 Docker/C#
• Passbolt - Collaborative password manager. (Source Code) AGPL-3.0 PHP/deb/K8S/Docker
• PassIt - Simple password manage with sharing features by group and user, but no administration interface. (Demo, Source Code) AGPL-3.0 Docker/Django
• Passky - Simple and modern password manager with website, browser extension, android and desktop application. (Demo, Source Code) GPL-3.0 PHP/Docker
• Psono - Password manager for companies. (Demo, Source Code) Apache-2.0 Python
• Teampass - Password manager dedicated for managing passwords in a collaborative way. One symmetric key is used to encrypt all shared/team passwords and stored server side in a file and the database. works on any server Apache, MySQL and PHP. (Source Code) GPL-3.0 PHP
• Vaultwarden - Lightweight Bitwarden server API implementation written in Rust. GPL-3.0 Rust/Docker

@ b0a838f2:34ed3f19

• Collabora Online Development Edition - Collabora Online Development Edition (CODE) is a powerful LibreOffice-based online office that supports all major document, spreadsheet and presentation file formats, which you can integrate in your own infrastructure. (Source Code) MPL-2.0 C++
• CryptPad - Collaboration suite built to enable collaboration, synchronizing changes to documents in real time. (Source Code) AGPL-3.0 Nodejs/Docker
• Digislides - Create multimedia presentations in a quick and easy way. (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs/PHP
• Etherpad - Highly customizable online editor providing collaborative editing in real-time. (Demo, Source Code) Apache-2.0 Nodejs/Docker
• Grist - Next-generation spreadsheet with relational structure, formula-based access control, and a portable, self-contained format (alternative to Airtable). (Demo, Source Code) Apache-2.0 Nodejs/Python/Docker
• ONLYOFFICE - Office suite that enables you to manage documents, projects, team and customer relations in one place. (Source Code) AGPL-3.0 Nodejs/Docker

@ b0a838f2:34ed3f19

• Blinko - A personal note tool with AI features. (Source Code) AGPL-3.0 Docker
• DailyTxT - Encrypted diary Web application to save your personal memories of each day. Includes a search function and encrypted file upload. MIT Docker
• Dnote - A simple command line notebook with multi-device sync and web interface. (Source Code) AGPL-3.0 Go
• Docs - Collaborative note taking, wiki and documentation platform that scales. (Source Code) MIT K8S
• draw.io - Diagram software for making flowcharts, process diagrams, org charts, UML, ER and network diagrams. (Source Code) Apache-2.0 Javascript/Docker
• flatnotes - Database-less note-taking web app that utilises a flat folder of markdown files for storage. (Demo) MIT Docker
• HedgeDoc - Realtime collaborative markdown notes on all platforms, formerly known as CodiMD and HackMD CE. (Demo, Source Code) AGPL-3.0 Docker/Nodejs
• Joplin - Note taking application with markdown editor and encryption support for mobile and desktop platforms. Runs client-side and syncs through a self hosted Nextcloud instance or similar (alternative to Evernote). (Source Code) MIT Nodejs
• Livebook - Realtime collaborative notebook app based on Markdown that supports running Elixir code snippets, TeX and Mermaid Diagrams. Easily deployed using Docker or Elixir. (Source Code) Apache-2.0 Elixir/Docker
• Memos - Knowledge base that works with a SQLite db file. (Demo, Source Code) MIT Docker/Go
• minimalist-web-notepad - Minimalist notepad.cc clone. (Demo) Apache-2.0 PHP
• Note Mark - Minimal web-based Markdown notes app. (Source Code) AGPL-3.0 Docker
• Oddmuse - Simple wiki engine written in Perl. No database required. (Source Code) GPL-3.0 Perl
• Overleaf - Web-based collaborative LaTeX editor. (Source Code) AGPL-3.0 Ruby
• Plainpad - Modern note taking application for the cloud, utilizing the best features of progressive web apps technology. (Demo, Source Code) GPL-3.0 PHP
• SilverBullet - Note-taking application optimized for people with a hacker mindset. (Demo, Source Code, Clients) MIT Docker/Deno
• Standard Notes - Simple and private notes app. Protect your privacy while getting more done. That's Standard Notes. (Demo, Source Code) GPL-3.0 Ruby
• TriliumNext Notes - Cross-platform hierarchical note taking application with focus on building large personal knowledge bases (fork of Trilium Notes). AGPL-3.0 Nodejs/Docker/K8S
• Turtl - Totally private personal database and note taking app. (Source Code) GPL-3.0 CommonLisp
• Writing - Lightweight distraction-free text editor, in the browser (Markdown and LaTeX supported). No lag when writing. (Source Code) MIT Javascript

@ b0a838f2:34ed3f19

• Actual - Local-first personal finance tool based on zero-sum budgeting, supporting synchronization across devices, custom rules, manual transaction importing (from QIF, OFX, and QFX files), and optional automatic synchronization with many banks. (Source Code) MIT Nodejs/Docker
• Bigcapital - Financial accounting and inventory management software for small to medium businesses. (Source Code) AGPL-3.0 Docker
• Bitcart - Cryptocurrencies payment processor and development platform. (Demo, Source Code) MIT Docker/Python/Nodejs
• BTCPay Server - Bitcoin and other cryptocurrencies payment processor. (Demo, Source Code) MIT C#
• DePay - Accept Web3 Payments directly into your wallet. Peer-to-peer, free, self-hosted & open-source. (Demo, Source Code) MIT Nodejs
• ExpenseOwl - Extremely simple expense tracker with a beautiful UI. MIT Go/Docker/K8S
• ezbookkeeping - A lightweight personal bookkeeping app hosted by yourself. (Demo, Source Code) MIT Go/Docker
• Family Accounting Tool - Web-based finance management tool for partners with partially shared expenses. Apache-2.0 Scala
• Fava - Web frontend of Beancount, a text based double-entry accounting system. (Demo, Source Code) MIT Python
• Firefly III - Firefly III is a modern financial manager. It helps you to keep track of your money and make budget forecasts. It supports credit cards, has an advanced rule engine and can import data from many banks. (Demo, Source Code) AGPL-3.0 PHP/Docker
• FOSSBilling - Hosting and billing automation. Integrates with WHM, CWP, cPanel and HestiaCP. Full API and easily extensible. (Demo, Source Code) Apache-2.0 PHP/Docker
• Galette - Membership management web application aimed towards non profit organizations. (Source Code) GPL-3.0 PHP
• Ghostfolio - Wealth management software to keep track of stocks, ETFs and cryptocurrencies. (Source Code) AGPL-3.0 Docker/Nodejs
• GRR - Assets management and booking for small/medium companies. (Source Code) GPL-2.0 PHP
• HyperSwitch ⚠ - Payment switch to make payments fast, reliable and affordable. Connect with multiple payment processors and route traffic effortlessly, all with a single API integration. (Source Code) Apache-2.0 Docker/Rust
• IHateMoney - Manage your shared expenses, easily. (Demo, Source Code) BSD-3-Clause Docker/Python
• Invoice Ninja - Powerful tool to invoice clients online. (Demo, Source Code) AAL PHP/Docker/K8S
• InvoicePlane - Manage quotes, invoices, payments and customers for your small business. (Source Code) MIT PHP
• InvoiceShelf - Track expenses, payments & create professional invoices & estimates (fork of Crater). (Source Code) AGPL-3.0 PHP/Docker
• Kill Bill - Subscription billing & payments platform. Have access to real-time analytics and financial reports. (Source Code) Apache-2.0 Java/Docker
• Kresus - Personal finance manager. (Demo, Source Code) AGPL-3.0 Nodejs/Docker
• Lago - Metering and usage-based billing. (Source Code) AGPL-3.0 Docker
• Maybe - An OS for your personal finances built by a small team alongside an incredible community. (Source Code) AGPL-3.0 Docker
• Mybucks.online - Secure, browser-based, password-only self-custodial cryptocurrency wallet. (Demo, Source Code) MIT Nodejs
• MyFin Budget - Personal finances platform (web + REST API + Android) that'll help you budget, keep track of your income/spending and forecast your financial future. (Demo, Source Code, Clients) GPL-3.0 Nodejs/Docker
• OctoBot - Cryptocurrency trading bot. (Source Code) GPL-3.0 Python/Docker
• Ocular - Simplistic and straightforward budgeting app to track your budget across months and years. (Demo, Source Code) MIT Docker
• OpenBudgeteer - Budgeting app based on the Bucket Budgeting Principle. AGPL-3.0 Docker/C#
• Receipt Wrangler ⚠ - Easy-to-use receipt manager, powered by AI. Allows users to create receipts effortlessly and quickly, categorize and more. (Demo, Source Code) AGPL-3.0 Docker
• REI3 - Open source, expandable Business Management Software. Manage tasks, time, assets and much more. (Demo, Source Code) MIT Go
• SHKeeper - Cryptocurrency payment processor with the unique combination of gateway and merchant allowing you to accept payments in multiple cryptocurrencies without fees and intermediaries. (Demo, Source Code) GPL-3.0 Python
• SolidInvoice - Open source invoicing and quote application. (Source Code) MIT PHP
• VoucherVault - Store and manage vouchers, coupons, loyalty and gift cards digitally. Supports expiry notifications, transaction histories, file uploads and OIDC SSO. GPL-3.0 Docker
• Wallos - Lightweight personal subscription tracker with statistics and optional notifications. (Demo, Source Code) GPL-3.0 PHP/Docker
• WYGIWYH - Simple and powerful finance tracker. (Demo) AGPL-3.0 Docker/Django
• YAFFA - Personal finance web application, that can be used to keep track of your money, expenses, budgets, and investments. It also helps with long-term financial planning. (Demo, Source Code) MIT PHP

@ 21335073:a244b1ad

The other day, I had the privilege of sitting down with one of my favorite living artists. Our conversation was so captivating that I felt compelled to share it. I’m leaving his name out for privacy.

Since our last meeting, I’d watched a documentary about his life, one he’d helped create. I told him how much I admired his openness in it. There’s something strange about knowing intimate details of someone’s life when they know so little about yours—it’s almost like I knew him too well for the kind of relationship we have.

He paused, then said quietly, with a shy grin, that watching the documentary made him realize how “odd and eccentric” he is. I laughed and told him he’s probably the sanest person I know. Because he’s lived fully, chasing love, passion, and purpose with hardly any regrets. He’s truly lived.

Today, I turn 44, and I’ll admit I’m a bit eccentric myself. I think I came into the world this way. I’ve made mistakes along the way, but I carry few regrets. Every misstep taught me something. And as I age, I’m not interested in blending in with the world—I’ll probably just lean further into my own brand of “weird.” I want to live life to the brim. The older I get, the more I see that the “normal” folks often seem less grounded than the eccentric artists who dare to live boldly. Life’s too short to just exist, actually live.

I’m not saying to be strange just for the sake of it. But I’ve seen what the crowd celebrates, and I’m not impressed. Forge your own path, even if it feels lonely or unpopular at times.

It’s easy to scroll through the news and feel discouraged. But actually, this is one of the most incredible times to be alive! I wake up every day grateful to be here, now. The future is bursting with possibility—I can feel it.

So, to my fellow weirdos on nostr: stay bold. Keep dreaming, keep pushing, no matter what’s trending. Stay wild enough to believe in a free internet for all. Freedom is radical—hold it tight. Live with the soul of an artist and the grit of a fighter. Thanks for inspiring me and so many others to keep hoping. Thank you all for making the last year of my life so special.

@ b0a838f2:34ed3f19

• 2FAuth - Manage your Two-Factor Authentication (2FA) accounts and generate their security codes. (Demo) AGPL-3.0 PHP/Docker
• AlertHub ⚠ - Get alerts from GitHub releases. MIT Nodejs/Docker
• Anchr - Toolbox for tiny tasks on the internet, including bookmark collections, URL shortening and (encrypted) image uploads. (Source Code) GPL-3.0 Nodejs
• asciinema - Web app for hosting asciicasts. (Demo, Source Code) Apache-2.0 Elixir/Docker
• Baby Buddy - Helps caregivers track baby sleep, feedings, diaper changes, and tummy time. (Demo) BSD-2-Clause Python
• beelzebub ⚠ - Honeypot framework designed to provide a highly secure environment for detecting and analyzing cyber attacks. (Source Code) MIT Docker/K8S/Go
• ClipCascade - Syncs your clipboard across multiple devices instantly, without any button press. Available on Windows, macOS, Linux, and Android, it provides seamless and secure clipboard sharing with end-to-end data encryption. GPL-3.0 Java/Docker
• Cloudlog - Log your amateur radio contacts anywhere. (Source Code) MIT PHP/Docker
• ConvertX - Online file converter which supports over a thousand different formats. AGPL-3.0 Docker
• CUPS - The Common Unix Print System uses Internet Printing Protocol (IPP) to support printing to local and network printers. (Source Code) GPL-2.0 C
• CyberChef - Perform all manner of operations within a web browser such as AES, DES and Blowfish encryption and decryption, creating hexdumps, calculating hashes, and much more. (Demo) Apache-2.0 Javascript
• Digiboard - Create collaborative whiteboards (documentation in French). (Source Code) AGPL-3.0 Nodejs
• Digicard - Create simple graphic compositions (documentation in French). (Demo) AGPL-3.0 Nodejs
• Digicut - Cut audio and video files using FFMPEG.wasm (documentation in French). (Source Code) AGPL-3.0 Nodejs
• Digiface - Create avatars using the Avataaars library (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs
• Digiflashcards - An online application to create flashcards (documentation in French). (Source Code) AGPL-3.0 Nodejs/PHP
• Digimerge - Assemble audio and video files directly in your browser (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs
• Digiquiz - An online application to publish content created with H5P (documentation in French). (Source Code) AGPL-3.0 Nodejs
• Digiread ⚠ - Clean up online pages and articles using Mozilla's Readability (documentation in French). (Source Code) AGPL-3.0 Nodejs/PHP
• Digisteps - A simple application for creating online educational paths (documentation in French). (Source Code) AGPL-3.0 Nodejs/PHP
• Digitranscode - Convert audio files and videos directly in the browser (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs
• Digiview ⚠ - View YouTube videos in a distraction-free interface (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs/PHP
• Digiwords - A simple online application for creating word clouds (documentation in French). (Source Code) AGPL-3.0 Nodejs/PHP
• DOCAT - Host your docs. Simple. Versioned. Fancy. MIT Python/Docker
• DOMJudge - System for running a programming contest, like the ICPC regional and world championship programming contests. (Demo, Source Code) GPL-2.0/BSD-3-Clause/MIT PHP
• ESMira - Run longitudinal studies (ESM, AA, EMA) with data collection and communication with participants being completely anonymous. (Demo, Source Code) AGPL-3.0 PHP
• F-Droid - Server tools for maintaining an F-Droid repository system. (Source Code) AGPL-3.0 Python/Docker/deb
• Flyimg - Resize and crop images on the fly. Get optimised images with MozJPEG, WebP or PNG using ImageMagick, with an efficient caching system. (Demo, Source Code) MIT Docker
• Geeftlist - Collaborative platform for managing, sharing and reserving gifts between friends and family. GPL-3.0 Docker
• google-webfonts-helper ⚠ - Hassle-Free Way to Self-Host Google Fonts. Get eot, ttf, svg, woff and woff2 files + CSS snippets. (Demo) MIT Nodejs
• Gophish - Powerful phishing framework that makes it easy to test your organization's exposure to phishing. (Source Code) MIT Go/Docker
• graph-vl - Identity document verification using Machine Learning and GraphQL. MIT Python/Docker/K8S
• Habitica - Habit tracker app which treats your goals like a Role Playing Game. (Source Code) GPL-3.0/CC-BY-SA-3.0 Nodejs/Docker
• HortusFox - Collaborative plant management and tracking system for plant enthusiasts. (Source Code) MIT PHP/Docker
• iSponsorBlockTV ⚠ - Block and skip sponsors, while also muting and skipping ads on YouTube. GPL-3.0 Docker/Python
• Jelu - Read and to-read list book tracker. (Source Code) MIT Java/Docker
• Kasm Workspaces - Streaming containerized apps and desktops to end-users. Examples include Ubuntu in your browser, or simply single apps such as Chrome, OpenOffice, Gimp, Filezilla etc. (Demo, Source Code) GPL-3.0 Docker
• Koillection - Koillection is a service allowing users to manage any kind of collections. (Source Code) MIT Docker/PHP
• LanguageTool - Proofread more than 20 languages. It finds many errors that a simple spell checker cannot detect. (Source Code, Clients) LGPL-2.1 Java/Docker
• Libre Translate - Machine Translation API. (Source Code) AGPL-3.0 Docker/Python
• LubeLogger - Web-based vehicle maintenance and fuel mileage tracker. (Demo, Source Code) MIT Docker/K8S/C#
• mosparo - The modern spam protection tool. It replaces other captcha methods with a simple and easy to use spam protection solution. (Source Code) MIT PHP
• MyIP ⚠ - All in one IP Toolbox. Easy to check what's your IPs, IP geolocation, check for DNS leaks, examine WebRTC connections, speed test, ping test, MTR test, check website availability and more. (Demo, Source Code) MIT Nodejs/Docker
• MySpeed - Speed test analysis software that shows your internet speed for up to 30 days. (Source Code) MIT Docker/Nodejs
• Neko - Virtual browser that runs in docker and uses WebRTC. (Source Code) Apache-2.0 Docker/Go
• Open-Meteo - Weather API with open-data forecasts, historical and climate data from all major national weather services. (Demo, Source Code) AGPL-3.0 Docker
• OpenZiti - Fully-featured, zero trust, full mesh overlay network. Includes a 2FA support out of the box, clients for all major desktop/mobile OS'es. (Source Code) Apache-2.0 Go
• penpot - Web-based design and prototyping platform meant for cross-domain teams. (Source Code) MPL-2.0 Docker
• POMjs - Random password generator. (Source Code) GPL-2.0 Javascript
• Reactive Resume - A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. (Demo, Source Code) MIT Docker/Nodejs
• revealjs - Framework for easily creating beautiful presentations using HTML. (Demo, Source Code) MIT Javascript
• Revive Adserver - World's most popular free, open source ad serving system. Formerly known as OpenX Adserver and phpAdsNew. (Source Code) GPL-2.0 PHP
• SANE Network Scanning - Allow remote clients to access image acquisition devices (scanners) available on the local host. (Source Code) GPL-2.0 C
• Speed Test by OpenSpeedTest™ - Free & Open-Source HTML5 Network Performance Estimation Tool. (Source Code) MIT Docker
• Speedtest Tracker - Monitor the performance and uptime of your internet connection. (Source Code) MIT Docker/K8S
• string.is - An open-source, privacy-friendly online string toolkit for developers. (Source Code) AGPL-3.0 Nodejs
• Teleport - Certificate authority and access plane for SSH, Kubernetes, web applications, and databases. (Source Code) Apache-2.0 Go/Docker/K8S
• TeslaMate - A powerful data logger for Tesla vehicles. MIT Elixir/Docker
• Upsnap - A simple Wake on LAN (WOL) dashboard app. Wake up devices on your network and see current status. MIT Go/Docker
• URL-to-PNG - URL to PNG utility featuring parallel rendering using Playwright for screenshots and with storage caching via Local, S3, or CouchDB. MIT Nodejs/Docker
• Wakupator - Wake On LAN Machine Manager based on network traffic. MIT C
• Wavelog - Webbased Logging Software for Radio Amateurs. Enhanced QSO logging, statistics and maps for your browser. (Demo, Source Code) MIT PHP/Docker
• WeeWX - Open source software for your weather station. (Demo, Source Code) GPL-3.0 Python/deb
• WeTTY - Terminal in browser over http/https. (Source Code) MIT Docker/Nodejs
• Yamtrack ⚠ - Media tracker for movies, tv shows, anime, manga, video games and books. (Demo) AGPL-3.0 Docker/Python

@ 51bbb15e:b77a2290

Yeah, I’m sure everything in the file is legit. 👍 Let’s review the guard witness testimony…Oh wait, they weren’t at their posts despite 24/7 survellience instructions after another Epstein “suicide” attempt two weeks earlier. Well, at least the video of the suicide is in the file? Oh wait, a techical glitch. Damn those coincidences!

At this point, the Trump administration has zero credibility with me on anything related to the Epstein case and his clients. I still suspect the administration is using the Epstein files as leverage to keep a lot of RINOs in line, whereas they’d be sabotaging his agenda at every turn otherwise. However, I just don’t believe in ends-justify-the-means thinking. It’s led almost all of DC to toss out every bit of the values they might once have had.

@ b0a838f2:34ed3f19

• CyTube - Synchronize media, chat, and more for an arbitrary number of channels. (Demo) MIT Nodejs
• Invidious ⚠ - Alternative YouTube front-end. (Demo) AGPL-3.0 Docker/Crystal
• MediaCMS - Modern, fully featured open source video and media CMS, written in Python/Django/React, featuring a REST API. (Source Code) AGPL-3.0 Python/Docker
• OvenMediaEngine - Streaming Server with Sub-Second Latency. (Demo) AGPL-3.0 C++/Docker
• Owncast - Decentralized single-user live video streaming and chat server for running your own live streams similar in style to the large mainstream options. (Source Code) MIT Go
• PeerTube - Decentralized video streaming platform using P2P (BitTorrent) directly in the web browser. (Source Code) AGPL-3.0 Nodejs
• Rapidbay - Self-hosted torrent videostreaming service/torrent client that allows searching and playing videos from torrents in the browser or from a Chromecast/AppleTV/Smart TV. MIT Python/Docker
• Restreamer - Restreamer allows you to do h.264 real-time video streaming on your website without a streaming provider. (Source Code) Apache-2.0 Nodejs/Docker
• SRS - A simple, high efficiency and real-time video server, supports RTMP, WebRTC, HLS, HTTP-FLV and SRT. (Source Code) MIT Docker/C++
• SyncTube - Lightweight and very simple to setup CyTube alternative to watch videos with friends and chat. MIT Nodejs/Haxe
• Tube Archivist ⚠ - Organize, search, and enjoy your YouTube collection. Subscribe, download, and track viewed content with metadata indexing and a user-friendly interface. (Source Code, Clients) GPL-3.0 Docker
• Tube - Youtube-like (without censorship and features you don't need!) video sharing app written in Go which also supports automatic transcoding to MP4 H.265 AAC, multiple collections and RSS feed. (Demo) MIT Go
• VideoLAN Client (VLC) - Cross-platform multimedia player client and server supporting most multimedia files as well as DVDs, Audio CDs, VCDs, and various streaming protocols. (Source Code) GPL-2.0 C/deb

@ c9badfea:610f861a

1. Install Sky Map (it's free and open source)
2. Launch the app and tap Accept, then tap OK
3. When asked to access the device's location, tap While Using The App
4. Tap somewhere on the screen to activate the menu, then tap ⁝ and select Settings
5. Disable Send Usage Statistics
6. Return to the main screen and enjoy stargazing!

ℹ️ Use the 🔍 icon in the upper toolbar to search for a specific celestial body, or tap the 👁️ icon to activate night mode

@ b0a838f2:34ed3f19

• ClipBucket - Start your own video sharing website (YouTube/Netflix Clone) in a matter of minutes. (Demo, Source Code) AAL Docker/PHP
• Gerbera - UPnP Media Server, which allows you to stream your digital media throughout your home network and listen to/watch it on a variety of UPnP compatible devices. (Source Code) GPL-2.0 Docker/deb/C++
• Icecast 2 - Streaming audio/video server which can be used to create an Internet radio station or a privately running jukebox and many things in between. (Source Code, Clients) GPL-2.0 C
• Jellyfin - Media server for audio, video, books, comics, and photos with a sleek interface and robust transcoding capabilities. Almost all modern platforms have clients, including Roku, Android TV, iOS, and Kodi. (Demo, Source Code, Clients) GPL-2.0 C#/deb/Docker
• Karaoke Eternal - Host awesome karaoke parties where everyone can easily find and queue songs from their phone's browser. The player is also fully browser-based with support for MP3+G, MP4 and WebGL visualizations. (Source Code) ISC Docker/Nodejs
• Kodi - Multimedia/Entertainment center, formerly known as XBMC. Runs on Android, BSD, Linux, macOS, iOS and Windows. (Source Code) GPL-2.0 C++/deb
• Kyoo - Innovative media browser designed for seamless streaming of anime, series and movies, offering advanced features like dynamic transcoding, auto watch history and intelligent metadata retrieval. (Demo) GPL-3.0 Docker
• Meelo - Personal Music Server, designed for collectors and music maniacs. GPL-3.0 Docker
• MistServer - Public domain streaming media server that works with any device and any format. (Source Code) Unlicense C++
• NymphCast - Turn your choice of Linux-capable hardware into an audio and video source for a television or powered speakers (alternative to Chromecast). (Source Code) BSD-3-Clause C++
• ReadyMedia - Simple media server software, with the aim of being fully compliant with DLNA/UPnP-AV clients. Formerly known as MiniDLNA. (Source Code) GPL-2.0 C
• Rygel - Rygel is a UPnP AV MediaServer that allows you to easily share audio, video, and pictures. Media player software may use Rygel to become a MediaRenderer that may be controlled remotely by a UPnP or DLNA Controller. (Source Code) GPL-3.0 C
• Stash - A web-based library organizer and player for your adult media stash, with auto-tagging and metadata scraping support. (Source Code) AGPL-3.0 Docker/Go
• µStreamer - Lightweight and very quick server to stream MJPEG video from any V4L2 device to the net. GPL-3.0 C/deb
• üWave ⚠ - Self-hosted collaborative listening platform. Users take turns playing media—songs, talks, gameplay videos, or anything else—from a variety of media sources like YouTube and SoundCloud. (Demo, Source Code) MIT Nodejs

@ b0a838f2:34ed3f19

• Ampache - Web based audio/video streaming application. (Demo, Source Code) AGPL-3.0 PHP
• Audiobookshelf - Audiobook and podcast server. It streams all audio formats, keeps and syncs progress across devices. Comes with open-source apps for Android and iOS. (Source Code, Clients) GPL-3.0 Docker/deb/Nodejs
• Audioserve - Simple personal server to serve audio files from directories (audiobooks, music, podcasts...). Focused on simplicity and supports sync of play position between clients. MIT Rust
• AzuraCast - Modern and accessible web radio management suite. (Source Code) Apache-2.0 Docker
• Beets - Music library manager and MusicBrainz tagger (command-line and Web interface). (Source Code) MIT Python/deb
• Black Candy - Music streaming server. MIT Docker/Ruby
• Funkwhale - Modern, web-based, convivial, multi-user and free music server. BSD-3-Clause Python/Django
• gonic - Lightweight music streaming server. Subsonic compatible. GPL-3.0 Go/Docker
• HoloPlay ⚠ - Listen to Youtube audio sources using Invidious API. (Source Code) MIT Nodejs/Docker
• koel - Personal music streaming server that works. (Demo, Source Code) MIT PHP
• LibreTime - Broadcast streaming radio on the web (fork of Airtime). (Source Code) AGPL-3.0 Docker/PHP
• LMS - Access your self-hosted music using a web interface. GPL-3.0 Docker/deb/C++
• Maloja - Music scrobble database (alternative to Last.fm). (Demo) GPL-3.0 Python/Docker
• moOde Audio - Audiophile-quality music playback for the wonderful Raspberry Pi family of single board computers. (Source Code) GPL-3.0 PHP
• Mopidy ⚠ - Extensible music server. Offers a superset of the mpd API, as well as integration with 3rd party services like Spotify, SoundCloud etc. (Source Code) Apache-2.0 Python/deb
• mpd - Daemon to remotely play music, stream music, handle and organize playlists. Many clients available. (Source Code, Clients) GPL-2.0 C++
• mStream - Music streaming server with GUI management tools. Runs on Mac, Windows, and Linux. (Source Code) GPL-3.0 Nodejs
• multi-scrobbler - Scrobble plays from multiple sources to multiple scrobbling services. (Source Code) MIT Nodejs/Docker
• musikcube - Streaming audio server with Linux/macOS/Windows/Android clients. (Source Code) BSD-3-Clause C++/deb
• Navidrome Music Server - Modern Music Server and Streamer, compatible with Subsonic/Airsonic. (Demo, Source Code, Clients) GPL-3.0 Docker/Go
• Pinepods - Podcast management system with multi-user support. Pinepods utilizes a central database so aspects like listen time and themes follow from device to device. (Demo, Source Code) GPL-3.0 Docker
• Polaris - Music browsing and streaming application optimized for large music collections, ease of use and high performance. MIT Rust/Docker
• Snapcast - Synchronous multiroom audio server. GPL-3.0 C++/deb
• Stretto ⚠ - Music player with Youtube/Soundcloud import and iTunes/Spotify discovery. (Demo, Clients) MIT Nodejs
• Supysonic - Python implementation of the Subsonic server API. AGPL-3.0 Python/deb
• SwingMusic - Swing Music is a beautiful, self-hosted music player and streaming server for your local audio files. Like a cooler Spotify ... but bring your own music. (Source Code) MIT Python/Docker
• vod2pod-rss ⚠ - Convert YouTube and Twitch channels to podcasts, no storage required. Transcodes VoDs to MP3 192k on the fly, generates an RSS feed to use in podcast clients. MIT Docker

@ b0a838f2:34ed3f19

• ChannelTube ⚠ - Download video or audio from YouTube channels on a schedule via yt-dlp. AGPL-3.0 Docker
• Dagu - Powerful Cron alternative with a Web UI. It allows you to define dependencies between commands as a Directed Acyclic Graph (DAG) in a declarative YAML format. (Source Code) GPL-3.0 Go/Docker
• Headphones - Automated music downloader for NZB and Torrent, written in Python. It supports SABnzbd, NZBget, Transmission, µTorrent, Deluge and Blackhole. GPL-3.0 Python
• Jellyseerr - Manage requests for your media library, supports Plex, Jellyfin and Emby media servers (fork of Overseerr). MIT Docker/Nodejs
• Lidarr - Music collection manager for Usenet and BitTorrent users. (Source Code) GPL-3.0 C#/Docker
• LidaTube ⚠ - Finding and fetch missing Lidarr albums via yt-dlp. GPL-3.0 Docker
• Lidify ⚠ - Music discovery tool that provides recommendations based on selected Lidarr artists, using Spotify or LastFM. MIT Docker
• Medusa - Automatic Video library manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic. (Clients) GPL-3.0 Python
• MetaTube ⚠ - Automatically download music from YouTube add metadata from Spotify, Deezer or Musicbrainz. GPL-3.0 Python
• MeTube - Web GUI for youtube-dl, with playlist support. Allows downloading videos from dozens of websites. AGPL-3.0 Python/Nodejs/Docker
• nefarious - Automate downloading Movies and TV Shows. (Source Code) GPL-3.0 Python
• Ombi - Content request system for Plex/Emby, connects to SickRage, CouchPotato, Sonarr, with a growing feature set. (Demo, Source Code) GPL-2.0 C#/deb
• Overseerr ⚠ - Manage requests for your media library. It integrates with your existing services, such as Sonarr, Radarr, and Plex!. (Source Code) MIT Docker
• Pinchflat ⚠ - Download YouTube content built using yt-dlp. AGPL-3.0 Docker
• PlexRipper ⚠ - Cross-platform Plex media downloader that seamlessly adds media from other Plex servers to your own. (Source Code) GPL-3.0 Docker
• PodFetch - Sleek and efficient podcast downloader. (Source Code) Apache-2.0 Docker/Rust
• Radarr - Radarr is an independent fork of Sonarr reworked for automatically downloading movies via Usenet and BitTorrent, à la Couchpotato. (Source Code) GPL-3.0 C#/Docker
• Reiverr ⚠ - Clean combined interface for Jellyfin, TMDB, Radarr and Sonarr, as well as a replacement to Overseerr. AGPL-3.0 Docker
• SickChill - Automatic video library manager for TV shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic. (Source Code) GPL-3.0 Python/Docker
• Sonarr - Automatic TV Shows downloader and manager for Usenet and BitTorrent. It can grab, sort and rename new episodes and automatically upgrade the quality of files already downloaded when a better quality format becomes available. (Source Code) GPL-3.0 C#/Docker
• tubesync ⚠ - Syncs YouTube channels and playlists to a locally hosted media server. AGPL-3.0 Docker/Python
• Watcharr - Add and track all the shows and movies you are watching. Comes with user authentication, modern and clean UI and a very simple setup. (Demo) MIT Docker
• ydl_api_ng - Simple youtube-dl REST API to launch downloads on a distant server. GPL-3.0 Python
• YoutubeDL-Server - Web and REST interface to Youtube-DL for downloading videos onto a server. MIT Python/Docker
• yt-dlp Web UI - Web GUI for yt-dlp. MPL-2.0 Docker/Go/Nodejs

@ b0a838f2:34ed3f19

• AdventureLog - Travel tracker and trip planner. (Demo, Source Code) GPL-3.0 Docker
• AirTrail - Personal flight tracking system. (Source Code) GPL-3.0 Docker/Nodejs
• Bicimon - Bike Speedometer as Progressive Web App. (Demo) MIT Javascript
• Dawarich - Visualize your location history, track your movements, and analyze your travel patterns with complete privacy and control (alternative to Google Timeline a.k.a. Google Location History). (Source Code) AGPL-3.0 Docker
• Geo2tz - Get the timezone from geo coordinates (lat, lon). MIT Go/Docker
• GraphHopper - Fast routing library and server using OpenStreetMap. (Source Code) Apache-2.0 Java
• Nominatim - Server application for geocoding (address -> coordinates) and reverse geocoding (coordinates -> address) on OpenStreetMap data. (Source Code) GPL-2.0 C
• Open Source Routing Machine (OSRM) - High performance routing engine designed to run on OpenStreetMap data and offering an HTTP API, C++ library interface, and Nodejs wrapper. (Demo, Source Code) BSD-2-Clause C++
• OpenRouteService - Route service with directions, isochrones, time-distance matrix, route optimization, etc. (Demo, Source Code) GPL-3.0 Docker/Java
• OpenStreetMap - Collaborative project to create a free editable map of the world. (Source Code, Clients) GPL-2.0 Ruby
• OpenTripPlanner - Multimodal trip planning software based on OpenStreetMap data and consuming published GTFS-formatted data to suggest routes using local public transit systems. (Source Code) LGPL-3.0 Java/Javascript
• OwnTracks Recorder ⚠ - Store and access data published by OwnTracks location tracking apps. GPL-2.0 C/Lua/deb/Docker
• TileServer GL - Vector and raster maps with GL styles. Server side rendering by Mapbox GL Native. Map tile server for Mapbox GL JS, Android, iOS, Leaflet, OpenLayers, GIS via WMTS, etc. (Source Code) BSD-2-Clause Nodejs/Docker
• Traccar - Java application to track GPS positions. Supports loads of tracking devices and protocols, has an Android and iOS App. Has a web interface to view your trips. (Demo, Source Code) Apache-2.0 Java
• wanderer - Trail database where you can upload your recorded tracks or create new ones and add various metadata to build an easily searchable catalogue. (Demo) AGPL-3.0 Docker/Go/Nodejs

@ b0a838f2:34ed3f19

• CNCjs - Web interface for CNC milling controllers running Grbl, Smoothieware, or TinyG. (Source Code) MIT Nodejs
• Fluidd - Lightweight & responsive user interface for Klipper, the 3D printer firmware. (Source Code) GPL-3.0 Docker/Nodejs
• Mainsail - Modern and responsive user interface for the Klipper 3D printer firmware. Control and monitor your printer from everywhere, from any device. (Source Code) GPL-3.0 Docker/Python
• Manyfold - Digital asset manager for 3d print files; STL, OBJ, 3MF and more. (Source Code) MIT Docker
• Octoprint - Snappy web interface for controlling consumer 3D printers. (Source Code) AGPL-3.0 Docker/Python

@ 04c915da:3dfbecc9

This piece is the first in a series that will focus on things I think are a priority if your focus is similar to mine: building a strong family and safeguarding their future.

---

Choosing the ideal place to raise a family is one of the most significant decisions you will ever make. For simplicity sake I will break down my thought process into key factors: strong property rights, the ability to grow your own food, access to fresh water, the freedom to own and train with guns, and a dependable community.

A Jurisdiction with Strong Property Rights

Strong property rights are essential and allow you to build on a solid foundation that is less likely to break underneath you. Regions with a history of limited government and clear legal protections for landowners are ideal. Personally I think the US is the single best option globally, but within the US there is a wide difference between which state you choose. Choose carefully and thoughtfully, think long term. Obviously if you are not American this is not a realistic option for you, there are other solid options available especially if your family has mobility. I understand many do not have this capability to easily move, consider that your first priority, making movement and jurisdiction choice possible in the first place.

Abundant Access to Fresh Water

Water is life. I cannot overstate the importance of living somewhere with reliable, clean, and abundant freshwater. Some regions face water scarcity or heavy regulations on usage, so prioritizing a place where water is plentiful and your rights to it are protected is critical. Ideally you should have well access so you are not tied to municipal water supplies. In times of crisis or chaos well water cannot be easily shutoff or disrupted. If you live in an area that is drought prone, you are one drought away from societal chaos. Not enough people appreciate this simple fact.

Grow Your Own Food

A location with fertile soil, a favorable climate, and enough space for a small homestead or at the very least a garden is key. In stable times, a small homestead provides good food and important education for your family. In times of chaos your family being able to grow and raise healthy food provides a level of self sufficiency that many others will lack. Look for areas with minimal restrictions, good weather, and a culture that supports local farming.

Guns

The ability to defend your family is fundamental. A location where you can legally and easily own guns is a must. Look for places with a strong gun culture and a political history of protecting those rights. Owning one or two guns is not enough and without proper training they will be a liability rather than a benefit. Get comfortable and proficient. Never stop improving your skills. If the time comes that you must use a gun to defend your family, the skills must be instinct. Practice. Practice. Practice.

A Strong Community You Can Depend On

No one thrives alone. A ride or die community that rallies together in tough times is invaluable. Seek out a place where people know their neighbors, share similar values, and are quick to lend a hand. Lead by example and become a good neighbor, people will naturally respond in kind. Small towns are ideal, if possible, but living outside of a major city can be a solid balance in terms of work opportunities and family security.

---

Let me know if you found this helpful. My plan is to break down how I think about these five key subjects in future posts.

@ 04c915da:3dfbecc9

There is something quietly rebellious about stacking sats. In a world obsessed with instant gratification, choosing to patiently accumulate Bitcoin, one sat at a time, feels like a middle finger to the hype machine. But to do it right, you have got to stay humble. Stack too hard with your head in the clouds, and you will trip over your own ego before the next halving even hits.

Small Wins

Stacking sats is not glamorous. Discipline. Stacking every day, week, or month, no matter the price, and letting time do the heavy lifting. Humility lives in that consistency. You are not trying to outsmart the market or prove you are the next "crypto" prophet. Just a regular person, betting on a system you believe in, one humble stack at a time. Folks get rekt chasing the highs. They ape into some shitcoin pump, shout about it online, then go silent when they inevitably get rekt. The ones who last? They stack. Just keep showing up. Consistency. Humility in action. Know the game is long, and you are not bigger than it.

Ego is Volatile

Bitcoin’s swings can mess with your head. One day you are up 20%, feeling like a genius and the next down 30%, questioning everything. Ego will have you panic selling at the bottom or over leveraging the top. Staying humble means patience, a true bitcoin zen. Do not try to "beat” Bitcoin. Ride it. Stack what you can afford, live your life, and let compounding work its magic.

Simplicity

There is a beauty in how stacking sats forces you to rethink value. A sat is worth less than a penny today, but every time you grab a few thousand, you plant a seed. It is not about flaunting wealth but rather building it, quietly, without fanfare. That mindset spills over. Cut out the noise: the overpriced coffee, fancy watches, the status games that drain your wallet. Humility is good for your soul and your stack. I have a buddy who has been stacking since 2015. Never talks about it unless you ask. Lives in a decent place, drives an old truck, and just keeps stacking. He is not chasing clout, he is chasing freedom. That is the vibe: less ego, more sats, all grounded in life.

The Big Picture

Stack those sats. Do it quietly, do it consistently, and do not let the green days puff you up or the red days break you down. Humility is the secret sauce, it keeps you grounded while the world spins wild. In a decade, when you look back and smile, it will not be because you shouted the loudest. It will be because you stayed the course, one sat at a time. \ \ Stay Humble and Stack Sats. 🫡

@ b0a838f2:34ed3f19

• Canvas LMS - Learning management system (LMS) that is revolutionizing the way we educate. (Demo, Source Code) AGPL-3.0 Ruby
• Chamilo LMS - Create a virtual campus for the provision of online or semi-online training. (Source Code) GPL-3.0 PHP
• Digiscreen - Interactive whiteboard/wallpaper for the classroom, in person or remotely (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs/PHP
• Digitools - A set of simple tools to accompany the animation of courses in person or remotely. (documentation in French). (Demo, Source Code) AGPL-3.0 PHP
• edX - The Open edX platform is open-source code that powers edX.org. (Source Code) AGPL-3.0 Python
• Gibbon - Flexible school management platform designed to make life better for teachers, students, parents and leaders. (Source Code) GPL-3.0 PHP
• ILIAS - Learning management system that can cope with anything you throw at it. (Demo, Source Code) GPL-3.0 PHP
• INGInious - Intelligent grader that allows secured and automated testing of code made by students. (Source Code, Clients) AGPL-3.0 Python/Docker
• Moodle - Learning and courses platform with one of the largest open source communities worldwide. (Demo, Source Code) GPL-3.0 PHP
• Open eClass - Open eClass is an advanced e-learning solution that can enhance the teaching and learning process. (Demo, Source Code) GPL-2.0 PHP
• OpenOLAT - Learning management system for teaching, education, assessment and communication. (Demo, Source Code) Apache-2.0 Java
• QST - Online assessment software. From a quick quiz on your phone to large scale, high stakes, proctored desktop testing, easy, secure and economical. (Demo, Source Code) GPL-2.0 Perl
• RELATE - RELATE is a web-based courseware package, includes features such as: flexible rules, statistics, multi-course support, class calendar. (Source Code) MIT Python
• RosarioSIS - RosarioSIS, free Student Information System for school management. (Demo, Source Code) GPL-2.0 PHP
• Schoco - Online IDE for learning Java programming at school, including automatic JUnit tests. Designed to give coding homework/assignments. MIT Docker
• scholarsome - Web-based and open source interactive flashcard learning software studying for the masses. (Demo, Source Code) GPL-3.0 Docker

@ 04c915da:3dfbecc9

Here’s a revised timeline of macro-level events from The Mandibles: A Family, 2029–2047 by Lionel Shriver, reimagined in a world where Bitcoin is adopted as a widely accepted form of money, altering the original narrative’s assumptions about currency collapse and economic control. In Shriver’s original story, the failure of Bitcoin is assumed amid the dominance of the bancor and the dollar’s collapse. Here, Bitcoin’s success reshapes the economic and societal trajectory, decentralizing power and challenging state-driven outcomes.

Part One: 2029–2032

• 2029 (Early Year)\ The United States faces economic strain as the dollar weakens against global shifts. However, Bitcoin, having gained traction emerges as a viable alternative. Unlike the original timeline, the bancor—a supranational currency backed by a coalition of nations—struggles to gain footing as Bitcoin’s decentralized adoption grows among individuals and businesses worldwide, undermining both the dollar and the bancor.

• 2029 (Mid-Year: The Great Renunciation)\ Treasury bonds lose value, and the government bans Bitcoin, labeling it a threat to sovereignty (mirroring the original bancor ban). However, a Bitcoin ban proves unenforceable—its decentralized nature thwarts confiscation efforts, unlike gold in the original story. Hyperinflation hits the dollar as the U.S. prints money, but Bitcoin’s fixed supply shields adopters from currency devaluation, creating a dual-economy split: dollar users suffer, while Bitcoin users thrive.

• 2029 (Late Year)\ Dollar-based inflation soars, emptying stores of goods priced in fiat currency. Meanwhile, Bitcoin transactions flourish in underground and online markets, stabilizing trade for those plugged into the bitcoin ecosystem. Traditional supply chains falter, but peer-to-peer Bitcoin networks enable local and international exchange, reducing scarcity for early adopters. The government’s gold confiscation fails to bolster the dollar, as Bitcoin’s rise renders gold less relevant.

• 2030–2031\ Crime spikes in dollar-dependent urban areas, but Bitcoin-friendly regions see less chaos, as digital wallets and smart contracts facilitate secure trade. The U.S. government doubles down on surveillance to crack down on bitcoin use. A cultural divide deepens: centralized authority weakens in Bitcoin-adopting communities, while dollar zones descend into lawlessness.

• 2032\ By this point, Bitcoin is de facto legal tender in parts of the U.S. and globally, especially in tech-savvy or libertarian-leaning regions. The federal government’s grip slips as tax collection in dollars plummets—Bitcoin’s traceability is low, and citizens evade fiat-based levies. Rural and urban Bitcoin hubs emerge, while the dollar economy remains fractured.

Time Jump: 2032–2047

• Over 15 years, Bitcoin solidifies as a global reserve currency, eroding centralized control. The U.S. government adapts, grudgingly integrating bitcoin into policy, though regional autonomy grows as Bitcoin empowers local economies.

Part Two: 2047

• 2047 (Early Year)\ The U.S. is a hybrid state: Bitcoin is legal tender alongside a diminished dollar. Taxes are lower, collected in BTC, reducing federal overreach. Bitcoin’s adoption has decentralized power nationwide. The bancor has faded, unable to compete with Bitcoin’s grassroots momentum.

• 2047 (Mid-Year)\ Travel and trade flow freely in Bitcoin zones, with no restrictive checkpoints. The dollar economy lingers in poorer areas, marked by decay, but Bitcoin’s dominance lifts overall prosperity, as its deflationary nature incentivizes saving and investment over consumption. Global supply chains rebound, powered by bitcoin enabled efficiency.

• 2047 (Late Year)\ The U.S. is a patchwork of semi-autonomous zones, united by Bitcoin’s universal acceptance rather than federal control. Resource scarcity persists due to past disruptions, but economic stability is higher than in Shriver’s original dystopia—Bitcoin’s success prevents the authoritarian slide, fostering a freer, if imperfect, society.

Key Differences

• Currency Dynamics: Bitcoin’s triumph prevents the bancor’s dominance and mitigates hyperinflation’s worst effects, offering a lifeline outside state control.
• Government Power: Centralized authority weakens as Bitcoin evades bans and taxation, shifting power to individuals and communities.
• Societal Outcome: Instead of a surveillance state, 2047 sees a decentralized, bitcoin driven world—less oppressive, though still stratified between Bitcoin haves and have-nots.

This reimagining assumes Bitcoin overcomes Shriver’s implied skepticism to become a robust, adopted currency by 2029, fundamentally altering the novel’s bleak trajectory.

@ b0a838f2:34ed3f19

• Atomic Server - Knowledge graph database with documents (similar to Notion), tables, search, and a powerful linked data API. Lightweight, very fast and no runtime dependencies. (Demo) MIT Docker/Rust
• Digimindmap - Create simple mindmaps (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs/PHP
• LibreKB - Web-based knowledge base solution. A simple web app, it runs on pretty much any web server or hosting provider with PHP and MySQL. (Source Code) GPL-3.0 PHP
• memEx - Structured personal knowledge base, inspired by zettlekasten and org-mode. AGPL-3.0 Docker
• SiYuan - A privacy-first personal knowledge management software, written in typescript and golang. (Source Code) AGPL-3.0 Docker/Go
• TeamMapper - Host and create your own mindmaps. Share your mindmap sessions with your team and collaborate live on mindmaps. (Demo) MIT Docker/Nodejs

@ 39cc53c9:27168656

Read the original blog post

The new website is finally live! I put in a lot of hard work over the past months on it. I'm proud to say that it's out now and it looks pretty cool, at least to me!

Why rewrite it all?

The old kycnot.me site was built using Python with Flask about two years ago. Since then, I've gained a lot more experience with Golang and coding in general. Trying to update that old codebase, which had a lot of design flaws, would have been a bad idea. It would have been like building on an unstable foundation.

That's why I made the decision to rewrite the entire application. Initially, I chose to use SvelteKit with JavaScript. I did manage to create a stable site that looked similar to the new one, but it required Jav aScript to work. As I kept coding, I started feeling like I was repeating "the Python mistake". I was writing the app in a language I wasn't very familiar with (just like when I was learning Python at that mom ent), and I wasn't happy with the code. It felt like spaghetti code all the time.

So, I made a complete U-turn and started over, this time using Golang. While I'm not as proficient in Golang as I am in Python now, I find it to be a very enjoyable language to code with. Most aof my recent pr ojects have been written in Golang, and I'm getting the hang of it. I tried to make the best decisions I could and structure the code as well as possible. Of course, there's still room for improvement, which I'll address in future updates.

Now I have a more maintainable website that can scale much better. It uses a real database instead of a JSON file like the old site, and I can add many more features. Since I chose to go with Golang, I mad e the "tradeoff" of not using JavaScript at all, so all the rendering load falls on the server. But I believe it's a tradeoff that's worth it.

What's new

• UI/UX - I've designed a new logo and color palette for kycnot.me. I think it looks pretty cool and cypherpunk. I am not a graphic designer, but I think I did a decent work and I put a lot of thinking on it to make it pleasant!
• Point system - The new point system provides more detailed information about the listings, and can be expanded to cover additional features across all services. Anyone can request a new point!
• ToS Scrapper: I've implemented a powerful automated terms-of-service scrapper that collects all the ToS pages from the listings. It saves you from the hassle of reading the ToS by listing the lines that are suspiciously related to KYC/AML practices. This is still in development and it will improve for sure, but it works pretty fine right now!
• Search bar - The new search bar allows you to easily filter services. It performs a full-text search on the Title, Description, Category, and Tags of all the services. Looking for VPN services? Just search for "vpn"!
• Transparency - To be more transparent, all discussions about services now take place publicly on GitLab. I won't be answering any e-mails (an auto-reply will prompt to write to the corresponding Gitlab issue). This ensures that all service-related matters are publicly accessible and recorded. Additionally, there's a real-time audits page that displays database changes.
• Listing Requests - I have upgraded the request system. The new form allows you to directly request services or points without any extra steps. In the future, I plan to enable requests for specific changes to parts of the website.
• Lightweight and fast - The new site is lighter and faster than its predecessor!
• Tor and I2P - At last! kycnot.me is now officially on Tor and I2P!

How?

This rewrite has been a labor of love, in the end, I've been working on this for more than 3 months now. I don't have a team, so I work by myself on my free time, but I find great joy in helping people on their private journey with cryptocurrencies. Making it easier for individuals to use cryptocurrencies without KYC is a goal I am proud of!

If you appreciate my work, you can support me through the methods listed here. Alternatively, feel free to send me an email with a kind message!

Technical details

All the code is written in Golang, the website makes use of the chi router for the routing part. I also make use of BigCache for caching database requests. There is 0 JavaScript, so all the rendering load falls on the server, this means it needed to be efficient enough to not drawn with a few users since the old site was reporting about 2M requests per month on average (note that this are not unique users).

The database is running with mariadb, using gorm as the ORM. This is more than enough for this project. I started working with an sqlite database, but I ended up migrating to mariadb since it works better with JSON.

The scraper is using chromedp combined with a series of keywords, regex and other logic. It runs every 24h and scraps all the services. You can find the scraper code here.

The frontend is written using Golang Templates for the HTML, and TailwindCSS plus DaisyUI for the CSS classes framework. I also use some plain CSS, but it's minimal.

The requests forms is the only part of the project that requires JavaScript to be enabled. It is needed for parsing some from fields that are a bit complex and for the "captcha", which is a simple Proof of Work that runs on your browser, destinated to avoid spam. For this, I use mCaptcha.

@ b0a838f2:34ed3f19

• Cannery - Firearm and ammunition tracker app. (Source Code) AGPL-3.0 Docker
• HomeBox (SysAdminsMedia) - Inventory and organization system built for the home user. (Demo, Source Code) AGPL-3.0 Docker/Go
• Inventaire - Collaborative resources mapper project, while yet only focused on exploring books mapping with wikidata and ISBNs. (Source Code) AGPL-3.0 Nodejs
• Inventree - Inventory management system which provides intuitive parts management and stock control. (Demo, Source Code) MIT Python
• Open QuarterMaster - Powerful inventory management system, designed to be flexible and scalable. (Source Code) GPL-3.0 deb/Docker
• Part-DB - Inventory management system for your electronic components. (Demo, Source Code) AGPL-3.0 Docker/PHP/Nodejs
• Shelf - Asset and equipment tracking software used by teams who value clarity. Shelf is an asset database and QR asset label generator that lets you create, manage and overview your assets across locations. Unlimited assets, free forever. (Source Code) AGPL-3.0 Nodejs
• Spoolman - Keep track of your inventory of 3D-printer filament spools. MIT Docker/Python

@ b83a28b7:35919450

This article was originally part of the sermon of Plebchain Radio Episode 111 (May 2, 2025) that nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgqpqtvqc82mv8cezhax5r34n4muc2c4pgjz8kaye2smj032nngg52clq7fgefr and I did with nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7ct4w35zumn0wd68yvfwvdhk6tcqyzx4h2fv3n9r6hrnjtcrjw43t0g0cmmrgvjmg525rc8hexkxc0kd2rhtk62 and nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgqpq4wxtsrj7g2jugh70pfkzjln43vgn4p7655pgky9j9w9d75u465pqahkzd0 of the nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyqwfvwrccp4j2xsuuvkwg0y6a20637t6f4cc5zzjkx030dkztt7t5hydajn

Listen to the full episode here:

<<https://fountain.fm/episode/Ln9Ej0zCZ5dEwfo8w2Ho>>

---

Bitcoin has always been a narrative revolution disguised as code. White paper, cypherpunk lore, pizza‑day legends - every block is a paragraph in the world’s most relentless epic. But code alone rarely converts the skeptic; it’s the camp‑fire myth that slips past the prefrontal cortex and shakes hands with the limbic system. People don’t adopt protocols first - they fall in love with protagonists.

Early adopters heard the white‑paper hymn, but most folks need characters first: a pizza‑day dreamer; a mother in a small country, crushed by the cost of remittance; a Warsaw street vendor swapping złoty for sats. When their arcs land, the brain releases a neurochemical OP_RETURN which says, “I belong in this plot.” That’s the sly roundabout orange pill: conviction smuggled inside catharsis.

That’s why, from 22–25 May in Warsaw’s Kinoteka, the Bitcoin Film Fest is loading its reels with rebellion. Each documentary, drama, and animated rabbit‑hole is a stealth wallet, zipping conviction straight into the feels of anyone still clasped within the cold claw of fiat. You come for the plot, you leave checking block heights.

---

Here's the clip of the sermon from the episode:

nostr:nevent1qvzqqqqqqypzpwp69zm7fewjp0vkp306adnzt7249ytxhz7mq3w5yc629u6er9zsqqsy43fwz8es2wnn65rh0udc05tumdnx5xagvzd88ptncspmesdqhygcrvpf2

@ b0a838f2:34ed3f19

• Domoticz - Home Automation System that lets you monitor and configure various devices like: Lights, Switches, various sensors/meters like Temperature, Rain, Wind, UV, Electra, Gas, Water and much more. (Source Code, Clients) GPL-3.0 C/C++/Docker/Shell
• EMQX - Scalable MQTT broker. Connect 100M+ IoT devices in one single cluster, move and process real-time IoT data with 1M msg/s throughput at 1ms latency. (Demo, Source Code) Apache-2.0 Docker/Erlang
• evcc - Extensible Electric Vehicle Charge Controller and home energy management system. (Source Code) MIT deb/Docker/Go
• FHEM - Automate common tasks in the household like switching lamps and heating. It can also be used to log events like temperature or power consumption. You can control it via web or smartphone frontends, telnet or TCP/IP directly. (Source Code) GPL-3.0 Perl
• FlowForge - Deploy Node-RED applications in a reliable, scalable and secure manner. The FlowForge platform provides DevOps capabilities for Node-RED development teams. (Source Code) Apache-2.0 Nodejs/Docker/K8S
• Gladys - Privacy-first home assistant. (Source Code) Apache-2.0 Nodejs/Docker
• Home Assistant - Home automation platform. (Demo, Source Code) Apache-2.0 Python/Docker
• ioBroker - Integration platform for the Internet of Things, focused on building automation, smart metering, ambient assisted living, process automation, visualization and data logging. (Source Code) MIT Nodejs
• LHA - Light Home Automation application that is fully extensible using Blockly, HTML or Lua. It includes extensions such as ConBee, Philips Hue or Z-Wave JS. MIT Lua
• Node RED - Browser-based flow editor that helps you wiring hardware devices, APIs and online services to create IoT solutions. (Source Code) Apache-2.0 Nodejs/Docker
• openHAB - Vendor and technology agnostic open source software for home automation. (Source Code) EPL-2.0 Java
• OpenRemote - IoT Asset management, Flow Rules and WHEN-THEN rules, Data visualization, Edge Gateway. (Demo, Source Code) AGPL-3.0 Java
• SIP Irrigation Control - Open source software for sprinkler/irrigation control. (Source Code) GPL-3.0 Python
• Tasmota - Open source firmware for ESP devices. Total local control with quick setup and updates. Control using MQTT, Web UI, HTTP or serial. Automate using timers, rules or scripts. Integration with home automation solutions. (Source Code) GPL-3.0 C/C++
• Thingsboard - Open-source IoT Platform - Device management, data collection, processing and visualization. (Demo, Source Code) Apache-2.0 Java/Docker/K8S
• WebThings Gateway - WebThings is an open source implementation of the Web of Things, including the WebThings Gateway and the WebThings Framework. (Source Code) MPL-2.0 Nodejs

@ 04c915da:3dfbecc9

Bitcoin has always been rooted in freedom and resistance to authority. I get that many of you are conflicted about the US Government stacking but by design we cannot stop anyone from using bitcoin. Many have asked me for my thoughts on the matter, so let’s rip it.

Concern

One of the most glaring issues with the strategic bitcoin reserve is its foundation, built on stolen bitcoin. For those of us who value private property this is an obvious betrayal of our core principles. Rather than proof of work, the bitcoin that seeds this reserve has been taken by force. The US Government should return the bitcoin stolen from Bitfinex and the Silk Road.

Using stolen bitcoin for the reserve creates a perverse incentive. If governments see bitcoin as a valuable asset, they will ramp up efforts to confiscate more bitcoin. The precedent is a major concern, and I stand strongly against it, but it should be also noted that governments were already seizing coin before the reserve so this is not really a change in policy.

Ideally all seized bitcoin should be burned, by law. This would align incentives properly and make it less likely for the government to actively increase coin seizures. Due to the truly scarce properties of bitcoin, all burned bitcoin helps existing holders through increased purchasing power regardless. This change would be unlikely but those of us in policy circles should push for it regardless. It would be best case scenario for American bitcoiners and would create a strong foundation for the next century of American leadership.

Optimism

The entire point of bitcoin is that we can spend or save it without permission. That said, it is a massive benefit to not have one of the strongest governments in human history actively trying to ruin our lives.

Since the beginning, bitcoiners have faced horrible regulatory trends. KYC, surveillance, and legal cases have made using bitcoin and building bitcoin businesses incredibly difficult. It is incredibly important to note that over the past year that trend has reversed for the first time in a decade. A strategic bitcoin reserve is a key driver of this shift. By holding bitcoin, the strongest government in the world has signaled that it is not just a fringe technology but rather truly valuable, legitimate, and worth stacking.

This alignment of incentives changes everything. The US Government stacking proves bitcoin’s worth. The resulting purchasing power appreciation helps all of us who are holding coin and as bitcoin succeeds our government receives direct benefit. A beautiful positive feedback loop.

Realism

We are trending in the right direction. A strategic bitcoin reserve is a sign that the state sees bitcoin as an asset worth embracing rather than destroying. That said, there is a lot of work left to be done. We cannot be lulled into complacency, the time to push forward is now, and we cannot take our foot off the gas. We have a seat at the table for the first time ever. Let's make it worth it.

We must protect the right to free usage of bitcoin and other digital technologies. Freedom in the digital age must be taken and defended, through both technical and political avenues. Multiple privacy focused developers are facing long jail sentences for building tools that protect our freedom. These cases are not just legal battles. They are attacks on the soul of bitcoin. We need to rally behind them, fight for their freedom, and ensure the ethos of bitcoin survives this new era of government interest. The strategic reserve is a step in the right direction, but it is up to us to hold the line and shape the future.

@ b0a838f2:34ed3f19

• admidio - User management system for websites of organizations and groups. The system has a flexible role model so that it’s possible to reflect the structure and permissions of your organization. (Demo, Source Code) GPL-2.0 PHP/Docker
• Frappe HR - Complete HRMS solution with over 13 different modules right from employee management, onboarding, leaves, to payroll, taxation, and more. (Source Code) GPL-3.0 Docker/Python/Nodejs
• MintHCM - Tool for Human Capital Management based on two popular, well-known business applications SugarCRM Community Edition and SuiteCRM. (Source Code) AGPL-3.0 PHP
• OrangeHRM - Comprehensive HRM system that captures all the essential functionalities required for any enterprise. (Demo, Source Code) GPL-2.0 PHP

@ b0a838f2:34ed3f19

• Endurain - Fitness tracking service designed to give users full control over their data and hosting environment. (Source Code) AGPL-3.0 Docker
• Fasten Health ⚠ - Personal/family electronic medical record aggregator, designed to integrate with hundreds of thousands of insurances/hospitals/clinics in the United States. GPL-3.0 Go/Docker
• Mere Medical ⚠ - Manage all of your medical records from Epic MyChart, Cerner, and OnPatient patient portals in one place. Privacy-focused, self-hosted, and offline-first. (Demo, Source Code) GPL-3.0 Docker/Nodejs
• OpenEMR - Electronic health records and medical practice management solution. (Demo, Source Code) GPL-3.0 PHP/Docker
• wger - Web-based personal workout, fitness and weight logger/tracker. It can also be used as a simple gym management utility and offers a full REST API as well. (Demo, Source Code) AGPL-3.0 Python/Docker

@ 04c915da:3dfbecc9

Recently we have seen a wave of high profile X accounts hacked. These attacks have exposed the fragility of the status quo security model used by modern social media platforms like X. Many users have asked if nostr fixes this, so lets dive in. How do these types of attacks translate into the world of nostr apps? For clarity, I will use X’s security model as representative of most big tech social platforms and compare it to nostr.

The Status Quo

On X, you never have full control of your account. Ultimately to use it requires permission from the company. They can suspend your account or limit your distribution. Theoretically they can even post from your account at will. An X account is tied to an email and password. Users can also opt into two factor authentication, which adds an extra layer of protection, a login code generated by an app. In theory, this setup works well, but it places a heavy burden on users. You need to create a strong, unique password and safeguard it. You also need to ensure your email account and phone number remain secure, as attackers can exploit these to reset your credentials and take over your account. Even if you do everything responsibly, there is another weak link in X infrastructure itself. The platform’s infrastructure allows accounts to be reset through its backend. This could happen maliciously by an employee or through an external attacker who compromises X’s backend. When an account is compromised, the legitimate user often gets locked out, unable to post or regain control without contacting X’s support team. That process can be slow, frustrating, and sometimes fruitless if support denies the request or cannot verify your identity. Often times support will require users to provide identification info in order to regain access, which represents a privacy risk. The centralized nature of X means you are ultimately at the mercy of the company’s systems and staff.

Nostr Requires Responsibility

Nostr flips this model radically. Users do not need permission from a company to access their account, they can generate as many accounts as they want, and cannot be easily censored. The key tradeoff here is that users have to take complete responsibility for their security. Instead of relying on a username, password, and corporate servers, nostr uses a private key as the sole credential for your account. Users generate this key and it is their responsibility to keep it safe. As long as you have your key, you can post. If someone else gets it, they can post too. It is that simple. This design has strong implications. Unlike X, there is no backend reset option. If your key is compromised or lost, there is no customer support to call. In a compromise scenario, both you and the attacker can post from the account simultaneously. Neither can lock the other out, since nostr relays simply accept whatever is signed with a valid key.

The benefit? No reliance on proprietary corporate infrastructure.. The negative? Security rests entirely on how well you protect your key.

Future Nostr Security Improvements

For many users, nostr’s standard security model, storing a private key on a phone with an encrypted cloud backup, will likely be sufficient. It is simple and reasonably secure. That said, nostr’s strength lies in its flexibility as an open protocol. Users will be able to choose between a range of security models, balancing convenience and protection based on need.

One promising option is a web of trust model for key rotation. Imagine pre-selecting a group of trusted friends. If your account is compromised, these people could collectively sign an event announcing the compromise to the network and designate a new key as your legitimate one. Apps could handle this process seamlessly in the background, notifying followers of the switch without much user interaction. This could become a popular choice for average users, but it is not without tradeoffs. It requires trust in your chosen web of trust, which might not suit power users or large organizations. It also has the issue that some apps may not recognize the key rotation properly and followers might get confused about which account is “real.”

For those needing higher security, there is the option of multisig using FROST (Flexible Round-Optimized Schnorr Threshold). In this setup, multiple keys must sign off on every action, including posting and updating a profile. A hacker with just one key could not do anything. This is likely overkill for most users due to complexity and inconvenience, but it could be a game changer for large organizations, companies, and governments. Imagine the White House nostr account requiring signatures from multiple people before a post goes live, that would be much more secure than the status quo big tech model.

Another option are hardware signers, similar to bitcoin hardware wallets. Private keys are kept on secure, offline devices, separate from the internet connected phone or computer you use to broadcast events. This drastically reduces the risk of remote hacks, as private keys never touches the internet. It can be used in combination with multisig setups for extra protection. This setup is much less convenient and probably overkill for most but could be ideal for governments, companies, or other high profile accounts.

---

Nostr’s security model is not perfect but is robust and versatile. Ultimately users are in control and security is their responsibility. Apps will give users multiple options to choose from and users will choose what best fits their need.

@ 04c915da:3dfbecc9

In much of the world, it is incredibly difficult to access U.S. dollars. Local currencies are often poorly managed and riddled with corruption. Billions of people demand a more reliable alternative. While the dollar has its own issues of corruption and mismanagement, it is widely regarded as superior to the fiat currencies it competes with globally. As a result, Tether has found massive success providing low cost, low friction access to dollars. Tether claims 400 million total users, is on track to add 200 million more this year, processes 8.1 million transactions daily, and facilitates $29 billion in daily transfers. Furthermore, their estimates suggest nearly 40% of users rely on it as a savings tool rather than just a transactional currency.

Tether’s rise has made the company a financial juggernaut. Last year alone, Tether raked in over $13 billion in profit, with a lean team of less than 100 employees. Their business model is elegantly simple: hold U.S. Treasuries and collect the interest. With over $113 billion in Treasuries, Tether has turned a straightforward concept into a profit machine.

Tether’s success has resulted in many competitors eager to claim a piece of the pie. This has triggered a massive venture capital grift cycle in USD tokens, with countless projects vying to dethrone Tether. Due to Tether’s entrenched network effect, these challengers face an uphill battle with little realistic chance of success. Most educated participants in the space likely recognize this reality but seem content to perpetuate the grift, hoping to cash out by dumping their equity positions on unsuspecting buyers before they realize the reality of the situation.

Historically, Tether’s greatest vulnerability has been U.S. government intervention. For over a decade, the company operated offshore with few allies in the U.S. establishment, making it a major target for regulatory action. That dynamic has shifted recently and Tether has seized the opportunity. By actively courting U.S. government support, Tether has fortified their position. This strategic move will likely cement their status as the dominant USD token for years to come.

While undeniably a great tool for the millions of users that rely on it, Tether is not without flaws. As a centralized, trusted third party, it holds the power to freeze or seize funds at its discretion. Corporate mismanagement or deliberate malpractice could also lead to massive losses at scale. In their goal of mitigating regulatory risk, Tether has deepened ties with law enforcement, mirroring some of the concerns of potential central bank digital currencies. In practice, Tether operates as a corporate CBDC alternative, collaborating with authorities to surveil and seize funds. The company proudly touts partnerships with leading surveillance firms and its own data reveals cooperation in over 1,000 law enforcement cases, with more than $2.5 billion in funds frozen.

---

The global demand for Tether is undeniable and the company’s profitability reflects its unrivaled success. Tether is owned and operated by bitcoiners and will likely continue to push forward strategic goals that help the movement as a whole. Recent efforts to mitigate the threat of U.S. government enforcement will likely solidify their network effect and stifle meaningful adoption of rival USD tokens or CBDCs. Yet, for all their achievements, Tether is simply a worse form of money than bitcoin. Tether requires trust in a centralized entity, while bitcoin can be saved or spent without permission. Furthermore, Tether is tied to the value of the US Dollar which is designed to lose purchasing power over time, while bitcoin, as a truly scarce asset, is designed to increase in purchasing power with adoption. As people awaken to the risks of Tether’s control, and the benefits bitcoin provides, bitcoin adoption will likely surpass it.

@ b0a838f2:34ed3f19

• Citadel - Groupware including email, calendar/scheduling, address books, forums, mailing lists, IM, wiki and blog engines, RSS aggregation and more. (Source Code) GPL-3.0 C/Docker/Shell
• Cozy Cloud - Personal cloud where you can manage and sync your contact, files and calendars, and manage your budget with an app store full of community contributions. (Source Code) GPL-3.0 Nodejs
• Digipad - An online self-hosted application for creating collaborative digital notepads (Documentation in french). (Source Code) AGPL-3.0 Nodejs
• Digistorm - Create collaborative surveys, quizzes, brainstorms, and word clouds (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs
• Digiwall - Create multimedia collaborative walls for in-person or remote work (documentation in French). (Source Code) AGPL-3.0 Nodejs
• egroupware - Software suite including calendars, address books, notepad, project management tools, client relationship management tools (CRM), knowledge management tools, a wiki and a CMS. (Source Code) GPL-2.0 PHP
• Group Office - Enterprise CRM and groupware tool. Share projects, calendars, files and e-mail online with co-workers and clients. (Source Code) AGPL-3.0 PHP
• Openmeetings - Video conferencing, instant messaging, whiteboard, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming. (Source Code) Apache-2.0 Java
• SOGo - SOGo offers multiple ways to access the calendaring and messaging data. CalDAV, CardDAV, GroupDAV, as well as ActiveSync, including native Outlook compatibility and Web interface. (Demo, Source Code) LGPL-2.1 Objective-C
• Tine - Software for digital collaboration in companies and organizations. From powerful groupware functionalities to clever add-ons, tine combines everything to make daily team collaboration easier. (Source Code) AGPL-3.0 Docker
• Tracim - Collaborative Platform for team collaboration: file,threads,notes,agenda,etc. AGPL-3.0/LGPL-3.0/MIT Python
• Zimbra Collaboration - Email, calendar, collaboration server with Web interface and lots of integrations. (Source Code) GPL-2.0/CPAL-1.0 Java

@ b0a838f2:34ed3f19

• IOPaint ⚠ - Image inpainting tool powered by SOTA AI Model. (Source Code) Apache-2.0 Python/Docker
• Ollama - Get up and running with Llama 3.3, DeepSeek-R1, Phi-4, Gemma 3, and other large language models. (Source Code) MIT Docker/Python
• Open-WebUI - User-friendly AI Interface, supports Ollama, OpenAI API. (Source Code) BSD-3-Clause Docker/Python
• Perplexica - AI-powered search engine (alternative to Perplexity AI). MIT Docker

@ 04c915da:3dfbecc9

One of the most common criticisms leveled against nostr is the perceived lack of assurance when it comes to data storage. Critics argue that without a centralized authority guaranteeing that all data is preserved, important information will be lost. They also claim that running a relay will become prohibitively expensive. While there is truth to these concerns, they miss the mark. The genius of nostr lies in its flexibility, resilience, and the way it harnesses human incentives to ensure data availability in practice.

A nostr relay is simply a server that holds cryptographically verifiable signed data and makes it available to others. Relays are simple, flexible, open, and require no permission to run. Critics are right that operating a relay attempting to store all nostr data will be costly. What they miss is that most will not run all encompassing archive relays. Nostr does not rely on massive archive relays. Instead, anyone can run a relay and choose to store whatever subset of data they want. This keeps costs low and operations flexible, making relay operation accessible to all sorts of individuals and entities with varying use cases.

Critics are correct that there is no ironclad guarantee that every piece of data will always be available. Unlike bitcoin where data permanence is baked into the system at a steep cost, nostr does not promise that every random note or meme will be preserved forever. That said, in practice, any data perceived as valuable by someone will likely be stored and distributed by multiple entities. If something matters to someone, they will keep a signed copy.

Nostr is the Streisand Effect in protocol form. The Streisand effect is when an attempt to suppress information backfires, causing it to spread even further. With nostr, anyone can broadcast signed data, anyone can store it, and anyone can distribute it. Try to censor something important? Good luck. The moment it catches attention, it will be stored on relays across the globe, copied, and shared by those who find it worth keeping. Data deemed important will be replicated across servers by individuals acting in their own interest.

Nostr’s distributed nature ensures that the system does not rely on a single point of failure or a corporate overlord. Instead, it leans on the collective will of its users. The result is a network where costs stay manageable, participation is open to all, and valuable verifiable data is stored and distributed forever.

@ b0a838f2:34ed3f19

• Genea.app - Genealogy tool designed with privacy in mind that anyone can use to author or edit their family tree. Data is stored in the GEDCOM format and all processing is done in the browser. (Source Code) MIT Javascript
• GeneWeb - Genealogy software that can be used offline or as a Web service. (Demo, Source Code) GPL-2.0 OCaml
• Gramps Web - Web app for collaborative genealogy, based on and interoperable with Gramps, the open source genealogy desktop application. (Demo, Source Code) AGPL-3.0 Docker
• webtrees - Webtrees is the web's leading online collaborative genealogy application. (Demo, Source Code) GPL-3.0 PHP

@ b0a838f2:34ed3f19

• auto-mcs - Cross-platform Minecraft server manager. (Source Code) AGPL-3.0 Python
• Crafty Controller - Minecraft launcher and manager that allows users to start and administer Minecraft servers from a user-friendly interface. (Source Code) GPL-3.0 Docker/Python
• EasyWI - Easy-Wi is a Web-interface that allows you to manage server daemons like gameservers. In addition it provides you with a CMS which includes a fully automated game- and voiceserver lending service. (Source Code) GPL-3.0 PHP/Shell
• Gaseous Server ⚠ - Game ROM manager with a built-in web-based emulator using multiple sources to identify and provide metadata. AGPL-3.0 Docker/.NET
• Kubek - Web management panel for Minecraft servers. (Source Code) GPL-3.0 Nodejs
• Lancache ⚠ - LAN Party game caching made easy. (Source Code) MIT Docker/Shell
• LinuxGSM - CLI tool for deployment and management of dedicated game servers on Linux: more than 120 games are supported. (Source Code) MIT Shell
• Lodestone - Server hosting tool for Minecraft and other multiplayers. AGPL-3.0 Docker/Rust
• Minus Games - Sync games and save files across multiple devices. (Source Code) MIT Rust
• Pelican Panel - Web application for easy management of game servers, offering a user-friendly interface for deploying, configuring, and managing servers, server monitoring tools, and extensive customization options (fork of Pterodactyl). (Source Code) AGPL-3.0 PHP/Docker
• Pterodactyl - Management panel for game servers, with an intuitive UI for end users. (Source Code) MIT PHP
• PufferPanel - Game server management panel designed for both small networks and game server providers. (Source Code) Apache-2.0 Go
• RconCli - CLI for executing queries on a remote Valve Source dedicated server using the RCON Protocol. MIT Go
• Retrom - Private cloud game library distribution server + frontend/launcher. GPL-3.0 Docker/Rust
• RomM ⚠ - ROM manager for organizing, enriching, and playing retro games, with support for 400+ platforms. (Demo, Source Code) AGPL-3.0 Docker
• SourceBans++ - Admin, ban, and communication management system for games running on the Source engine. (Source Code) CC-BY-SA-4.0 PHP
• Sunshine - Remote game stream host for Moonlight with support up to 120 frames per second and 4K resolution. (Source Code) GPL-3.0 C++/deb/Docker

@ 21335073:a244b1ad

Someone asked for my thoughts, so I’ll share them thoughtfully. I’m not here to dictate how to promote Nostr—I’m still learning about it myself. While I’m not new to Nostr, freedom tech is a newer space for me. I’m skilled at advocating for topics I deeply understand, but freedom tech isn’t my expertise, so take my words with a grain of salt. Nothing I say is set in stone.

Those who need Nostr the most are the ones most vulnerable to censorship on other platforms right now. Reaching them requires real-time awareness of global issues and the dynamic relationships between governments and tech providers, which can shift suddenly. Effective Nostr promoters must grasp this and adapt quickly.

The best messengers are people from or closely tied to these at-risk regions—those who truly understand the local political and cultural dynamics. They can connect with those in need when tensions rise. Ideal promoters are rational, trustworthy, passionate about Nostr, but above all, dedicated to amplifying people’s voices when it matters most.

Forget influencers, corporate-backed figures, or traditional online PR—it comes off as inauthentic, corny, desperate and forced. Nostr’s promotion should be grassroots and organic, driven by a few passionate individuals who believe in Nostr and the communities they serve.

The idea that “people won’t join Nostr due to lack of reach” is nonsense. Everyone knows X’s “reach” is mostly with bots. If humans want real conversations, Nostr is the place. X is great for propaganda, but Nostr is for the authentic voices of the people.

Those spreading Nostr must be so passionate they’re willing to onboard others, which is time-consuming but rewarding for the right person. They’ll need to make Nostr and onboarding a core part of who they are. I see no issue with that level of dedication. I’ve been known to get that way myself at times. It’s fun for some folks.

With love, I suggest not adding Bitcoin promotion with Nostr outreach. Zaps already integrate that element naturally. (Still promote within the Bitcoin ecosystem, but this is about reaching vulnerable voices who needed Nostr yesterday.)

To promote Nostr, forget conventional strategies. “Influencers” aren’t the answer. “Influencers” are not the future. A trusted local community member has real influence—reach them. Connect with people seeking Nostr’s benefits but lacking the technical language to express it. This means some in the Nostr community might need to step outside of the Bitcoin bubble, which is uncomfortable but necessary. Thank you in advance to those who are willing to do that.

I don’t know who is paid to promote Nostr, if anyone. This piece isn’t shade. But it’s exhausting to see innocent voices globally silenced on corporate platforms like X while Nostr exists. Last night, I wondered: how many more voices must be censored before the Nostr community gets uncomfortable and thinks creatively to reach the vulnerable?

A warning: the global need for censorship-resistant social media is undeniable. If Nostr doesn’t make itself known, something else will fill that void. Let’s start this conversation.

@ 21335073:a244b1ad

Please respect Virginia Giuffre’s memory by refraining from asking about the circumstances or theories surrounding her passing.

Since Virginia Giuffre’s death, I’ve reflected on what she would want me to say or do. This piece is my attempt to honor her legacy.

When I first spoke with Virginia, I was struck by her unshakable hope. I had grown cynical after years in the anti-human trafficking movement, worn down by a broken system and a government that often seemed complicit. But Virginia’s passion, creativity, and belief that survivors could be heard reignited something in me. She reminded me of my younger, more hopeful self. Instead of warning her about the challenges ahead, I let her dream big, unburdened by my own disillusionment. That conversation changed me for the better, and following her lead led to meaningful progress.

Virginia was one of the bravest people I’ve ever known. As a survivor of Epstein, Maxwell, and their co-conspirators, she risked everything to speak out, taking on some of the world’s most powerful figures.

She loved when I said, “Epstein isn’t the only Epstein.” This wasn’t just about one man—it was a call to hold all abusers accountable and to ensure survivors find hope and healing.

The Epstein case often gets reduced to sensational details about the elite, but that misses the bigger picture. Yes, we should be holding all of the co-conspirators accountable, we must listen to the survivors’ stories. Their experiences reveal how predators exploit vulnerabilities, offering lessons to prevent future victims.

You’re not powerless in this fight. Educate yourself about trafficking and abuse—online and offline—and take steps to protect those around you. Supporting survivors starts with small, meaningful actions. Free online resources can guide you in being a safe, supportive presence.

When high-profile accusations arise, resist snap judgments. Instead of dismissing survivors as “crazy,” pause to consider the trauma they may be navigating. Speaking out or coping with abuse is never easy. You don’t have to believe every claim, but you can refrain from attacking accusers online.

Society also fails at providing aftercare for survivors. The government, often part of the problem, won’t solve this. It’s up to us. Prevention is critical, but when abuse occurs, step up for your loved ones and community. Protect the vulnerable. it’s a challenging but a rewarding journey.

If you’re contributing to Nostr, you’re helping build a censorship resistant platform where survivors can share their stories freely, no matter how powerful their abusers are. Their voices can endure here, offering strength and hope to others. This gives me great hope for the future.

Virginia Giuffre’s courage was a gift to the world. It was an honor to know and serve her. She will be deeply missed. My hope is that her story inspires others to take on the powerful.

@ b0a838f2:34ed3f19

• 0 A.D. - Cross-platform real-time strategy game of ancient warfare. (Source Code) MIT/GPL-2.0/Zlib C++/C/deb
• A Dark Room - Minimalist text adventure game for your browser. (Demo) MPL-2.0 Javascript
• Digibuzzer - Create a virtual game room around a connected buzzer (documentation in French). (Demo, Source Code) AGPL-3.0 Nodejs
• Lila - Ad-less chess server powering lichess.org, with official iOS and Android client apps. (Source Code) AGPL-3.0 Scala
• Luanti - Voxel game engine (formerly Minetest). Play one of our many games, mod a game to your liking, make your own game, or play on a multiplayer server. (Source Code) LGPL-2.1/MIT/Zlib C++/Lua/deb
• Mindustry - Factorio-like tower defense game. Build production chains to gather more resources, and build complex facilities. (Source Code) GPL-3.0 Java
• MTA:SA ⚠ - Add network play functionality to Rockstar North's Grand Theft Auto game series, in which this functionality is not originally found. (Source Code) GPL-3.0 C++
• OpenTTD - Transport tycoon simulation game. (Source Code, Clients) GPL-2.0 C++/Docker
• piqueserver - Server for openspades, the first-person shooter in a destructible voxel world. (Clients) GPL-3.0 Python/C++
• Posio - Geography multiplayer game. MIT Python
• Quizmaster - Web application for conducting a quiz, including a page for players to enter their answers. Apache-2.0 Scala
• Red Eclipse 2 - A FOSS Arena First-Person Shooter Similar to Unreal Tournament. (Source Code) Zlib/MIT/CC-BY-SA-4.0 C/C++/deb
• Scribble.rs - A web-based pictionary game. (Demo) BSD-3-Clause Go/Docker
• Suroi - An open-source 2D battle royale game inspired by surviv.io. (Demo, Source Code) GPL-3.0 Nodejs
• The Battle for Wesnoth - The Battle for Wesnoth is an Open Source, turn-based tactical strategy game with a high fantasy theme, featuring both singleplayer and online/hotseat multiplayer combat. GPL-2.0 C++/deb
• Veloren - Multiplayer RPG. Open-source game inspired by Cube World, Legend of Zelda, Dwarf Fortress and Minecraft. (Source Code) GPL-3.0 Rust
• Word Mastermind - Wordle clone. A Mastermind-like game, but instead of colors you need to guess words. (Demo) MIT Nodejs
• Zero-K - Open Source on Springrts engine. Zero-K is a traditional real time strategy game with a focus on player creativity through terrain manipulation, physics, and a large roster of unique units - all while being balanced to support competitive play. (Source Code) GPL-2.0 Lua

@ 52b4a076:e7fad8bd

I have been recently building NFDB, a new relay DB. This post is meant as a short overview.

Regular relays have challenges

Current relay software have significant challenges, which I have experienced when hosting Nostr.land: - Scalability is only supported by adding full replicas, which does not scale to large relays. - Most relays use slow databases and are not optimized for large scale usage. - Search is near-impossible to implement on standard relays. - Privacy features such as NIP-42 are lacking. - Regular DB maintenance tasks on normal relays require extended downtime. - Fault-tolerance is implemented, if any, using a load balancer, which is limited. - Personalization and advanced filtering is not possible. - Local caching is not supported.

NFDB: A scalable database for large relays

NFDB is a new database meant for medium-large scale relays, built on FoundationDB that provides: - Near-unlimited scalability - Extended fault tolerance - Instant loading - Better search - Better personalization - and more.

Search

NFDB has extended search capabilities including: - Semantic search: Search for meaning, not words. - Interest-based search: Highlight content you care about. - Multi-faceted queries: Easily filter by topic, author group, keywords, and more at the same time. - Wide support for event kinds, including users, articles, etc.

Personalization

NFDB allows significant personalization: - Customized algorithms: Be your own algorithm. - Spam filtering: Filter content to your WoT, and use advanced spam filters. - Topic mutes: Mute topics, not keywords. - Media filtering: With Nostr.build, you will be able to filter NSFW and other content - Low data mode: Block notes that use high amounts of cellular data. - and more

Other

NFDB has support for many other features such as: - NIP-42: Protect your privacy with private drafts and DMs - Microrelays: Easily deploy your own personal microrelay - Containers: Dedicated, fast storage for discoverability events such as relay lists

Calcite: A local microrelay database

Calcite is a lightweight, local version of NFDB that is meant for microrelays and caching, meant for thousands of personal microrelays.

Calcite HA is an additional layer that allows live migration and relay failover in under 30 seconds, providing higher availability compared to current relays with greater simplicity. Calcite HA is enabled in all Calcite deployments.

For zero-downtime, NFDB is recommended.

Noswhere SmartCache

Relays are fixed in one location, but users can be anywhere.

Noswhere SmartCache is a CDN for relays that dynamically caches data on edge servers closest to you, allowing: - Multiple regions around the world - Improved throughput and performance - Faster loading times

routerd

routerd is a custom load-balancer optimized for Nostr relays, integrated with SmartCache.

routerd is specifically integrated with NFDB and Calcite HA to provide fast failover and high performance.

Ending notes

NFDB is planned to be deployed to Nostr.land in the coming weeks.

A lot more is to come. 👀️️️️️️

@ 866e0139:6a9334e5

Autor: Caitlin Johnstone. Dieser Beitrag wurde mit dem Pareto-Client geschrieben. Sie finden alle Texte der Friedenstaube und weitere Texte zum Thema Frieden hier. Die neuesten Pareto-Artikel finden Sie in unserem Telegram-Kanal.

---

Die neuesten Artikel der Friedenstaube gibt es jetzt auch im eigenen Friedenstaube-Telegram-Kanal.

---

Ich hörte einem jungen Autor zu, der eine Idee beschrieb, die ihn so sehr begeisterte, dass er die Nacht zuvor nicht schlafen konnte. Und ich erinnerte mich daran, wie ich mich früher – vor Gaza – über das Schreiben freuen konnte. Dieses Gefühl habe ich seit 2023 nicht mehr gespürt.

Ich beklage mich nicht und bemitleide mich auch nicht selbst, ich stelle einfach fest, wie unglaublich düster und finster die Welt in dieser schrecklichen Zeit geworden ist. Es wäre seltsam und ungesund, wenn ich in den letzten anderthalb Jahren Freude an meiner Arbeit gehabt hätte. Diese Dinge sollen sich nicht gut anfühlen. Nicht, wenn man wirklich hinschaut und ehrlich zu sich selbst ist in dem, was man sieht.

Es war die ganze Zeit über so hässlich und so verstörend. Es gibt eigentlich keinen Weg, all diesen Horror umzudeuten oder irgendwie erträglich zu machen. Alles, was man tun kann, ist, an sich selbst zu arbeiten, um genug inneren Raum zu schaffen, um die schlechten Gefühle zuzulassen und sie ganz durchzufühlen, bis sie sich ausgedrückt haben. Lass die Verzweiflung herein. Die Trauer. Die Wut. Den Schmerz. Lass sie deinen Körper vollständig durchfließen, ohne Widerstand, und steh dann auf und schreibe das nächste Stück.

Das ist es, was Schreiben für mich jetzt ist. Es ist nie etwas, worüber ich mich freue, es zu teilen, oder wofür ich von Inspiration erfüllt bin. Wenn überhaupt, dann fühlt es sich eher so an wie: „Okay, hier bitte, es tut mir schrecklich leid, dass ich euch das zeigen muss, Leute.“ Es ist das Starren in die Dunkelheit, in das Blut, in das Gemetzel, in die gequälten Gesichter – und das Aufschreiben dessen, was ich sehe, Tag für Tag.

Nichts daran ist angenehm oder befriedigend. Es ist einfach das, was man tut, wenn ein Genozid in Echtzeit vor den eigenen Augen stattfindet, mit der Unterstützung der eigenen Gesellschaft. Alles daran ist entsetzlich, und es gibt keinen Weg, das schönzureden – aber man tut, was getan werden muss. So, wie man es täte, wenn es die eigene Familie wäre, die da draußen im Schutt liegt.

Dieser Genozid hat mich für immer verändert. Er hat viele Menschen für immer verändert. Wir werden nie wieder dieselben sein. Die Welt wird nie wieder dieselbe sein. Ganz gleich, was passiert oder wie dieser Albtraum endet – die Dinge werden nie wieder so sein wie zuvor.

Und das sollten sie auch nicht. Der Holocaust von Gaza ist das Ergebnis der Welt, wie sie vor ihm war. Unsere Gesellschaft hat ihn hervorgebracht – und jetzt starrt er uns allen direkt ins Gesicht. Das sind wir. Das ist die Frucht des Baumes, den die westliche Zivilisation bis zu diesem Punkt gepflegt hat.

Jetzt geht es nur noch darum, alles zu tun, was wir können, um den Genozid zu beenden – und sicherzustellen, dass die Welt die richtigen Lehren daraus zieht. Das ist eines der würdigsten Anliegen, denen man sich in diesem Leben widmen kann.

Ich habe noch immer Hoffnung, dass wir eine gesunde Welt haben können. Ich habe noch immer Hoffnung, dass das Schreiben über das, was geschieht, eines Tages wieder Freude bereiten kann. Aber diese Dinge liegen auf der anderen Seite eines langen, schmerzhaften, konfrontierenden Weges, der in den kommenden Jahren vor uns liegt. Es gibt keinen Weg daran vorbei.

Die Welt kann keinen Frieden und kein Glück finden, solange wir uns nicht vollständig damit auseinandergesetzt haben, was wir Gaza angetan haben.

Dieser Text ist die deutsche Übersetzung dieses Substack-Artikels von Caitlin Johnstone.

---

LASSEN SIE DER FRIEDENSTAUBE FLÜGEL WACHSEN!

Hier können Sie die Friedenstaube abonnieren und bekommen die Artikel zugesandt.

Schon jetzt können Sie uns unterstützen:

• Für 50 CHF/EURO bekommen Sie ein Jahresabo der Friedenstaube.
• Für 120 CHF/EURO bekommen Sie ein Jahresabo und ein T-Shirt/Hoodie mit der Friedenstaube.
• Für 500 CHF/EURO werden Sie Förderer und bekommen ein lebenslanges Abo sowie ein T-Shirt/Hoodie mit der Friedenstaube.
• Ab 1000 CHF werden Sie Genossenschafter der Friedenstaube mit Stimmrecht (und bekommen lebenslanges Abo, T-Shirt/Hoodie).

Für Einzahlungen in CHF (Betreff: Friedenstaube):

Für Einzahlungen in Euro:

Milosz Matuschek

IBAN DE 53710520500000814137

BYLADEM1TST

Sparkasse Traunstein-Trostberg

Betreff: Friedenstaube

Wenn Sie auf anderem Wege beitragen wollen, schreiben Sie die Friedenstaube an: friedenstaube@pareto.space

---

Sie sind noch nicht auf Nostr and wollen die volle Erfahrung machen (liken, kommentieren etc.)? Zappen können Sie den Autor auch ohne Nostr-Profil! Erstellen Sie sich einen Account auf Start. Weitere Onboarding-Leitfäden gibt es im Pareto-Wiki.

@ 91bea5cd:1df4451c

O Contexto Legal Brasileiro e o Consentimento

No ordenamento jurídico brasileiro, o consentimento do ofendido pode, em certas circunstâncias, afastar a ilicitude de um ato que, sem ele, configuraria crime (como lesão corporal leve, prevista no Art. 129 do Código Penal). Contudo, o consentimento tem limites claros: não é válido para bens jurídicos indisponíveis, como a vida, e sua eficácia é questionável em casos de lesões corporais graves ou gravíssimas.

A prática de BDSM consensual situa-se em uma zona complexa. Em tese, se ambos os parceiros são adultos, capazes, e consentiram livre e informadamente nos atos praticados, sem que resultem em lesões graves permanentes ou risco de morte não consentido, não haveria crime. O desafio reside na comprovação desse consentimento, especialmente se uma das partes, posteriormente, o negar ou alegar coação.

A Lei Maria da Penha (Lei nº 11.340/2006)

A Lei Maria da Penha é um marco fundamental na proteção da mulher contra a violência doméstica e familiar. Ela estabelece mecanismos para coibir e prevenir tal violência, definindo suas formas (física, psicológica, sexual, patrimonial e moral) e prevendo medidas protetivas de urgência.

Embora essencial, a aplicação da lei em contextos de BDSM pode ser delicada. Uma alegação de violência por parte da mulher, mesmo que as lesões ou situações decorram de práticas consensuais, tende a receber atenção prioritária das autoridades, dada a presunção de vulnerabilidade estabelecida pela lei. Isso pode criar um cenário onde o parceiro masculino enfrenta dificuldades significativas em demonstrar a natureza consensual dos atos, especialmente se não houver provas robustas pré-constituídas.

Outros riscos:

Lesão corporal grave ou gravíssima (art. 129, §§ 1º e 2º, CP), não pode ser justificada pelo consentimento, podendo ensejar persecução penal.

Crimes contra a dignidade sexual (arts. 213 e seguintes do CP) são de ação pública incondicionada e independem de representação da vítima para a investigação e denúncia.

Riscos de Falsas Acusações e Alegação de Coação Futura

Os riscos para os praticantes de BDSM, especialmente para o parceiro que assume o papel dominante ou que inflige dor/restrição (frequentemente, mas não exclusivamente, o homem), podem surgir de diversas frentes:

1. Acusações Externas: Vizinhos, familiares ou amigos que desconhecem a natureza consensual do relacionamento podem interpretar sons, marcas ou comportamentos como sinais de abuso e denunciar às autoridades.
2. Alegações Futuras da Parceira: Em caso de término conturbado, vingança, arrependimento ou mudança de perspectiva, a parceira pode reinterpretar as práticas passadas como abuso e buscar reparação ou retaliação através de uma denúncia. A alegação pode ser de que o consentimento nunca existiu ou foi viciado.
3. Alegação de Coação: Uma das formas mais complexas de refutar é a alegação de que o consentimento foi obtido mediante coação (física, moral, psicológica ou econômica). A parceira pode alegar, por exemplo, que se sentia pressionada, intimidada ou dependente, e que seu "sim" não era genuíno. Provar a ausência de coação a posteriori é extremamente difícil.
4. Ingenuidade e Vulnerabilidade Masculina: Muitos homens, confiando na dinâmica consensual e na parceira, podem negligenciar a necessidade de precauções. A crença de que "isso nunca aconteceria comigo" ou a falta de conhecimento sobre as implicações legais e o peso processual de uma acusação no âmbito da Lei Maria da Penha podem deixá-los vulneráveis. A presença de marcas físicas, mesmo que consentidas, pode ser usada como evidência de agressão, invertendo o ônus da prova na prática, ainda que não na teoria jurídica.

Estratégias de Prevenção e Mitigação

Não existe um método infalível para evitar completamente o risco de uma falsa acusação, mas diversas medidas podem ser adotadas para construir um histórico de consentimento e reduzir vulnerabilidades:

1. Comunicação Explícita e Contínua: A base de qualquer prática BDSM segura é a comunicação constante. Negociar limites, desejos, palavras de segurança ("safewords") e expectativas antes, durante e depois das cenas é crucial. Manter registros dessas negociações (e-mails, mensagens, diários compartilhados) pode ser útil.

2. Documentação do Consentimento:

   • Contratos de Relacionamento/Cena: Embora a validade jurídica de "contratos BDSM" seja discutível no Brasil (não podem afastar normas de ordem pública), eles servem como forte evidência da intenção das partes, da negociação detalhada de limites e do consentimento informado. Devem ser claros, datados, assinados e, idealmente, reconhecidos em cartório (para prova de data e autenticidade das assinaturas).

   • Registros Audiovisuais: Gravar (com consentimento explícito para a gravação) discussões sobre consentimento e limites antes das cenas pode ser uma prova poderosa. Gravar as próprias cenas é mais complexo devido a questões de privacidade e potencial uso indevido, mas pode ser considerado em casos específicos, sempre com consentimento mútuo documentado para a gravação.

     Importante: a gravação deve ser com ciência da outra parte, para não configurar violação da intimidade (art. 5º, X, da Constituição Federal e art. 20 do Código Civil).

3. Testemunhas: Em alguns contextos de comunidade BDSM, a presença de terceiros de confiança durante negociações ou mesmo cenas pode servir como testemunho, embora isso possa alterar a dinâmica íntima do casal.

4. Estabelecimento Claro de Limites e Palavras de Segurança: Definir e respeitar rigorosamente os limites (o que é permitido, o que é proibido) e as palavras de segurança é fundamental. O desrespeito a uma palavra de segurança encerra o consentimento para aquele ato.
5. Avaliação Contínua do Consentimento: O consentimento não é um cheque em branco; ele deve ser entusiástico, contínuo e revogável a qualquer momento. Verificar o bem-estar do parceiro durante a cena ("check-ins") é essencial.
6. Discrição e Cuidado com Evidências Físicas: Ser discreto sobre a natureza do relacionamento pode evitar mal-entendidos externos. Após cenas que deixem marcas, é prudente que ambos os parceiros estejam cientes e de acordo, talvez documentando por fotos (com data) e uma nota sobre a consensualidade da prática que as gerou.
7. Aconselhamento Jurídico Preventivo: Consultar um advogado especializado em direito de família e criminal, com sensibilidade para dinâmicas de relacionamento alternativas, pode fornecer orientação personalizada sobre as melhores formas de documentar o consentimento e entender os riscos legais específicos.

Observações Importantes

• Nenhuma documentação substitui a necessidade de consentimento real, livre, informado e contínuo.
• A lei brasileira protege a "integridade física" e a "dignidade humana". Práticas que resultem em lesões graves ou que violem a dignidade de forma não consentida (ou com consentimento viciado) serão ilegais, independentemente de qualquer acordo prévio.
• Em caso de acusação, a existência de documentação robusta de consentimento não garante a absolvição, mas fortalece significativamente a defesa, ajudando a demonstrar a natureza consensual da relação e das práticas.

• A alegação de coação futura é particularmente difícil de prevenir apenas com documentos. Um histórico consistente de comunicação aberta (whatsapp/telegram/e-mails), respeito mútuo e ausência de dependência ou controle excessivo na relação pode ajudar a contextualizar a dinâmica como não coercitiva.

• Cuidado com Marcas Visíveis e Lesões Graves Práticas que resultam em hematomas severos ou lesões podem ser interpretadas como agressão, mesmo que consentidas. Evitar excessos protege não apenas a integridade física, mas também evita questionamentos legais futuros.

O que vem a ser consentimento viciado

No Direito, consentimento viciado é quando a pessoa concorda com algo, mas a vontade dela não é livre ou plena — ou seja, o consentimento existe formalmente, mas é defeituoso por alguma razão.

O Código Civil brasileiro (art. 138 a 165) define várias formas de vício de consentimento. As principais são:

Erro: A pessoa se engana sobre o que está consentindo. (Ex.: A pessoa acredita que vai participar de um jogo leve, mas na verdade é exposta a práticas pesadas.)

Dolo: A pessoa é enganada propositalmente para aceitar algo. (Ex.: Alguém mente sobre o que vai acontecer durante a prática.)

Coação: A pessoa é forçada ou ameaçada a consentir. (Ex.: "Se você não aceitar, eu termino com você" — pressão emocional forte pode ser vista como coação.)

Estado de perigo ou lesão: A pessoa aceita algo em situação de necessidade extrema ou abuso de sua vulnerabilidade. (Ex.: Alguém em situação emocional muito fragilizada é induzida a aceitar práticas que normalmente recusaria.)

No contexto de BDSM, isso é ainda mais delicado: Mesmo que a pessoa tenha "assinado" um contrato ou dito "sim", se depois ela alegar que seu consentimento foi dado sob medo, engano ou pressão psicológica, o consentimento pode ser considerado viciado — e, portanto, juridicamente inválido.

Isso tem duas implicações sérias:

1. O crime não se descaracteriza: Se houver vício, o consentimento é ignorado e a prática pode ser tratada como crime normal (lesão corporal, estupro, tortura, etc.).

2. A prova do consentimento precisa ser sólida: Mostrando que a pessoa estava informada, lúcida, livre e sem qualquer tipo de coação.

   Consentimento viciado é quando a pessoa concorda formalmente, mas de maneira enganada, forçada ou pressionada, tornando o consentimento inútil para efeitos jurídicos.

Conclusão

Casais que praticam BDSM consensual no Brasil navegam em um terreno que exige não apenas confiança mútua e comunicação excepcional, mas também uma consciência aguçada das complexidades legais e dos riscos de interpretações equivocadas ou acusações mal-intencionadas. Embora o BDSM seja uma expressão legítima da sexualidade humana, sua prática no Brasil exige responsabilidade redobrada. Ter provas claras de consentimento, manter a comunicação aberta e agir com prudência são formas eficazes de se proteger de falsas alegações e preservar a liberdade e a segurança de todos os envolvidos. Embora leis controversas como a Maria da Penha sejam "vitais" para a proteção contra a violência real, os praticantes de BDSM, e em particular os homens nesse contexto, devem adotar uma postura proativa e prudente para mitigar os riscos inerentes à potencial má interpretação ou instrumentalização dessas práticas e leis, garantindo que a expressão de sua consensualidade esteja resguardada na medida do possível.

---

Importante: No Brasil, mesmo com tudo isso, o Ministério Público pode denunciar por crime como lesão corporal grave, estupro ou tortura, independente de consentimento. Então a prudência nas práticas é fundamental.

Aviso Legal: Este artigo tem caráter meramente informativo e não constitui aconselhamento jurídico. As leis e interpretações podem mudar, e cada situação é única. Recomenda-se buscar orientação de um advogado qualificado para discutir casos específicos.

Se curtiu este artigo faça uma contribuição, se tiver algum ponto relevante para o artigo deixe seu comentário.

@ e691f4df:1099ad65

Viewing Bitcoin Through the Light of Awakening

Ankh & Ohm Capital’s Overview of the Psycho-Spiritual Nature of Bitcoin

---

Glossary:

I. Preface: The Logos of Our Logo

II. An Oracular Introduction

III. Alchemizing Greed

IV. Layers of Fractalized Thought

V. Permissionless Individuation

VI. Dispelling Paradox Through Resonance

VII. Ego Deflation

VIII. The Coin of Great Price

Preface: The Logos of Our Logo

Before we offer our lens on Bitcoin, it’s important to illuminate the meaning behind Ankh & Ohm’s name and symbol. These elements are not ornamental—they are foundational, expressing the cosmological principles that guide our work.

Our mission is to bridge the eternal with the practical. As a Bitcoin-focused family office and consulting firm, we understand capital not as an end, but as a tool—one that, when properly aligned, becomes a vehicle for divine order. We see Bitcoin not simply as a technological innovation but as an emanation of the Divine Logos—a harmonic expression of truth, transparency, and incorruptible structure. Both the beginning and the end, the Alpha and Omega.

The Ankh (☥), an ancient symbol of eternal life, is a key to the integration of opposites. It unites spirit and matter, force and form, continuity and change. It reminds us that capital, like Life, must not only be generative, but regenerative; sacred. Money must serve Life, not siphon from it.

The Ohm (Ω) holds a dual meaning. In physics, it denotes a unit of electrical resistance—the formative tension that gives energy coherence. In the Vedic tradition, Om (ॐ) is the primordial vibration—the sound from which all existence unfolds. Together, these symbols affirm a timeless truth: resistance and resonance are both sacred instruments of the Creator.

Ankh & Ohm, then, represents our striving for union, for harmony —between the flow of life and intentional structure, between incalculable abundance and measured restraint, between the lightbulb’s electrical impulse and its light-emitting filament. We stand at the threshold where intention becomes action, and where capital is not extracted, but cultivated in rhythm with the cosmos. 

We exist to shepherd this transformation, as guides of this threshold —helping families, founders, and institutions align with a deeper order, where capital serves not as the prize, but as a pathway to collective Presence, Purpose, Peace and Prosperity.

---

An Oracular Introduction

Bitcoin is commonly understood as the first truly decentralized and secure form of digital money—a breakthrough in monetary sovereignty. But this view, while technically correct, is incomplete and spiritually shallow. Bitcoin is more than a tool for economic disruption. Bitcoin represents a mythic threshold: a symbol of the psycho-spiritual shift that many ancient traditions have long foretold.

For millennia, sages and seers have spoken of a coming Golden Age. In the Vedic Yuga cycles, in Plato’s Great Year, in the Eagle and Condor prophecies of the Americas—there exists a common thread: that humanity will emerge from darkness into a time of harmony, cooperation, and clarity. That the veil of illusion (maya, materiality) will thin, and reality will once again become transparent to the transcendent. In such an age, systems based on scarcity, deception, and centralization fall away. A new cosmology takes root—one grounded in balance, coherence, and sacred reciprocity.

But we must ask—how does such a shift happen? How do we cross from the age of scarcity, fear, and domination into one of coherence, abundance, and freedom?

One possible answer lies in the alchemy of incentive.

Bitcoin operates not just on the rules of computer science or Austrian economics, but on something far more old and subtle: the logic of transformation. It transmutes greed—a base instinct rooted in scarcity—into cooperation, transparency, and incorruptibility.

In this light, Bitcoin becomes more than code—it becomes a psychoactive protocol, one that rewires human behavior by aligning individual gain with collective integrity. It is not simply a new form of money. It is a new myth of value. A new operating system for human consciousness.

Bitcoin does not moralize. It harmonizes. It transforms the instinct for self-preservation into a pathway for planetary coherence.

---

Alchemizing Greed

At the heart of Bitcoin lies the ancient alchemical principle of transmutation: that which is base may be refined into gold.

Greed, long condemned as a vice, is not inherently evil. It is a distorted longing. A warped echo of the drive to preserve life. But in systems built on scarcity and deception, this longing calcifies into hoarding, corruption, and decay.

Bitcoin introduces a new game. A game with memory. A game that makes deception inefficient and truth profitable. It does not demand virtue—it encodes consequence. Its design does not suppress greed; it reprograms it.

In traditional models, game theory often illustrates the fragility of trust. The Prisoner’s Dilemma reveals how self-interest can sabotage collective well-being. But Bitcoin inverts this. It creates an environment where self-interest and integrity converge—where the most rational action is also the most truthful.

Its ledger, immutable and transparent, exposes manipulation for what it is: energetically wasteful and economically self-defeating. Dishonesty burns energy and yields nothing. The network punishes incoherence, not by decree, but by natural law.

This is the spiritual elegance of Bitcoin: it does not suppress greed—it transmutes it. It channels the drive for personal gain into the architecture of collective order. Miners compete not to dominate, but to validate. Nodes collaborate not through trust, but through mathematical proof.

This is not austerity. It is alchemy.

Greed, under Bitcoin, is refined. Tempered. Re-forged into a generative force—no longer parasitic, but harmonic.

---

Layers of Fractalized Thought Fragments

All living systems are layered. So is the cosmos. So is the human being. So is a musical scale.

At its foundation lies the timechain—the pulsing, incorruptible record of truth. Like the heart, it beats steadily. Every block, like a pulse, affirms its life through continuity. The difficulty adjustment—Bitcoin’s internal calibration—functions like heart rate variability, adapting to pressure while preserving coherence.

Above this base layer is the Lightning Network—a second layer facilitating rapid, efficient transactions. It is the nervous system: transmitting energy, reducing latency, enabling real-time interaction across a distributed whole.

Beyond that, emerging tools like Fedimint and Cashu function like the capillaries—bringing vitality to the extremities, to those underserved by legacy systems. They empower the unbanked, the overlooked, the forgotten. Privacy and dignity in the palms of those the old system refused to see.

And then there is NOSTR—the decentralized protocol for communication and creation. It is the throat chakra, the vocal cords of the “freedom-tech” body. It reclaims speech from the algorithmic overlords, making expression sovereign once more. It is also the reproductive system, as it enables the propagation of novel ideas and protocols in fertile, uncensorable soil.

Each layer plays its part. Not in hierarchy, but in harmony. In holarchy. Bitcoin and other open source protocols grow not through exogenous command, but through endogenous coherence. Like cells in an organism. Like a song.

Imagine the cell as a piece of glass from a shattered holographic plate —by which its perspectival, moving image can be restructured from the single shard. DNA isn’t only a logical script of base pairs, but an evolving progressive song. Its lyrics imbued with wise reflections on relationships.  The nucleus sings, the cell responds—not by command, but by memory. Life is not imposed; it is expressed. A reflection of a hidden pattern.

Bitcoin chants this. Each node, a living cell, holds the full timechain—Truth distributed, incorruptible. Remove one, and the whole remains. This isn’t redundancy. It’s a revelation on the power of protection in Truth.

Consensus is communion. Verification becomes a sacred rite—Truth made audible through math. 

Not just the signal; the song. A web of self-expression woven from Truth.

No center, yet every point alive with the whole. Like Indra’s Net, each reflects all. This is more than currency and information exchange. It is memory; a self-remembering Mind, unfolding through consensus and code. A Mind reflecting the Truth of reality at the speed of thought.

Heuristics are mental shortcuts—efficient, imperfect, alive. Like cells, they must adapt or decay. To become unbiased is to have self-balancing heuristics which carry feedback loops within them: they listen to the environment, mutate when needed, and survive by resonance with reality. Mutation is not error, but evolution. Its rules are simple, but their expression is dynamic. 

What persists is not rigidity, but pattern. 

To think clearly is not necessarily to be certain, but to dissolve doubt by listening, adjusting, and evolving thought itself.

To understand Bitcoin is simply to listen—patiently, clearly, as one would to a familiar rhythm returning.

---

Permissionless Individuation

Bitcoin is a path. One that no one can walk for you.

Said differently, it is not a passive act. It cannot be spoon-fed. Like a spiritual path, it demands initiation, effort, and the willingness to question inherited beliefs.

Because Bitcoin is permissionless, no one can be forced to adopt it. One must choose to engage it—compelled by need, interest, or intuition. Each person who embarks undergoes their own version of the hero’s journey.

Carl Jung called this process Individuation—the reconciliation of fragmented psychic elements into a coherent, mature Self. Bitcoin mirrors this: it invites individuals to confront the unconscious assumptions of the fiat paradigm, and to re-integrate their relationship to time, value, and agency.

In Western traditions—alchemy, Christianity, Kabbalah—the individual is sacred, and salvation is personal. In Eastern systems—Daoism, Buddhism, the Vedas—the self is ultimately dissolved into the cosmic whole. Bitcoin, in a paradoxical way, echoes both: it empowers the individual, while aligning them with a holistic, transcendent order.

To truly see Bitcoin is to allow something false to die. A belief. A habit. A self-concept.

In that death—a space opens for deeper connection with the Divine itSelf. 

In that dissolution, something luminous is reborn. 

After the passing, Truth becomes resurrected.  

---

Dispelling Paradox Through Resonance

There is a subtle paradox encoded into the hero’s journey: each starts in solidarity, yet the awakening affects the collective.

No one can be forced into understanding Bitcoin. Like a spiritual truth, it must be seen. And yet, once seen, it becomes nearly impossible to unsee—and easier for others to glimpse. The pattern catches.

This phenomenon mirrors the concept of morphic resonance, as proposed and empirically tested by biologist Rupert Sheldrake. Once a critical mass of individuals begins to embody a new behavior or awareness, it becomes easier—instinctive—for others to follow suit. Like the proverbial hundredth monkey who begins to wash the fruit in the sea water, and suddenly, monkeys across islands begin doing the same—without ever meeting.

When enough individuals embody a pattern, it ripples outward. Not through propaganda, but through field effect and wave propagation. It becomes accessible, instinctive, familiar—even across great distance.

Bitcoin spreads in this way. Not through centralized broadcast, but through subtle resonance. Each new node, each individual who integrates the protocol into their life, strengthens the signal for others. The protocol doesn’t shout; it hums, oscillates and vibrates——persistently, coherently, patiently.

One awakens. Another follows. The current builds. What was fringe becomes familiar. What was radical becomes obvious.

This is the sacred geometry of spiritual awakening. One awakens, another follows, and soon the fluidic current is strong enough to carry the rest. One becomes two, two become many, and eventually the many become One again. This tessellation reverberates through the human aura, not as ideology, but as perceivable pattern recognition.

Bitcoin’s most powerful marketing tool is truth. Its most compelling evangelist is reality. Its most unstoppable force is resonance.

Therefore, Bitcoin is not just financial infrastructure—it is psychic scaffolding. It is part of the subtle architecture through which new patterns of coherence ripple across the collective field. 

The training wheels from which humanity learns to embody Peace and Prosperity.

---

Ego Deflation

The process of awakening is not linear, and its beginning is rarely gentle—it usually begins with disruption, with ego inflation and destruction.

To individuate is to shape a center; to recognize peripherals and create boundaries—to say, “I am.” But without integration, the ego tilts—collapsing into void or inflating into noise. Fiat reflects this pathology: scarcity hoarded, abundance simulated. Stagnation becomes disguised as safety, and inflation masquerades as growth.

In other words, to become whole, the ego must first rise—claiming agency, autonomy, and identity. However, when left unbalanced, it inflates, or implodes. It forgets its context. It begins to consume rather than connect. And so the process must reverse: what inflates must deflate.

In the fiat paradigm, this inflation is literal. More is printed, and ethos is diluted. Savings decay. Meaning erodes. Value is abstracted. The economy becomes bloated with inaudible noise. And like the psyche that refuses to confront its own shadow, it begins to collapse under the weight of its own illusions.

But under Bitcoin, time is honored. Value is preserved. Energy is not abstracted but grounded.

Bitcoin is inherently deflationary—in both economic and spiritual senses. With a fixed supply, it reveals what is truly scarce. Not money, not status—but the finite number of heartbeats we each carry.

To see Bitcoin is to feel that limit in one’s soul. To hold Bitcoin is to feel Time’s weight again. To sense the importance of Bitcoin is to feel the value of preserved, potential energy. It is to confront the reality that what matters cannot be printed, inflated, or faked. In this way, Bitcoin gently confronts the ego—not through punishment, but through clarity.

Deflation, rightly understood, is not collapse—it is refinement. It strips away illusion, bloat, and excess. It restores the clarity of essence.

Spiritually, this is liberation.

---

The Coin of Great Price

There is an ancient parable told by a wise man:

“The kingdom of heaven is like a merchant seeking fine pearls, who, upon finding one of great price, sold all he had and bought it.”

Bitcoin is such a pearl.

But the ledger is more than a chest full of treasure. It is a key to the heart of things.

It is not just software—it is sacrament.

A symbol of what cannot be corrupted. A mirror of divine order etched into code. A map back to the sacred center.

It reflects what endures. It encodes what cannot be falsified. It remembers what we forgot: that Truth, when aligned with form, becomes Light once again.

Its design is not arbitrary. It speaks the language of life itself— 

The elliptic orbits of the planets mirrored in its cryptography,

The logarithmic spiral of the nautilus shell discloses its adoption rate,

The interconnectivity of mycelium in soil reflect the network of nodes in cyberspace, 

A webbed breadth of neurons across synaptic space fires with each new confirmed transaction.

It is geometry in devotion. Stillness in motion.

It is the Logos clothed in protocol.

What this key unlocks is beyond external riches. It is the eternal gold within us.

Clarity. Sovereignty. The unshakeable knowing that what is real cannot be taken. That what is sacred was never for sale.

Bitcoin is not the destination.

It is the Path.

And we—when we are willing to see it—are the Temple it leads back to.

@ b0a838f2:34ed3f19

• Apaxy - Theme built to enhance the experience of browsing web directories, using the mod_autoindex Apache module and some CSS to override the default style of a directory listing. (Source Code) GPL-3.0 Javascript
• copyparty - Portable file server with accelerated resumable uploads, deduplication, WebDAV, FTP, zeroconf, media indexer, video thumbnails, audio transcoding, and write-only folders, in a single file with no mandatory dependencies. (Demo) MIT Python
• DirectoryLister - Simple PHP based directory lister that lists a directory and all its sub-directories and allows you to navigate there within. (Source Code) MIT PHP
• filebrowser - Web File Browser with a Material Design web interface. (Source Code) Apache-2.0 Go
• FileGator - FileGator is a powerful multi-user file manager with a single page front-end. (Demo, Source Code) MIT PHP/Docker
• Filestash - Web file manager that lets you manage your data anywhere it is located: FTP, SFTP, WebDAV, Git, S3, Minio, Dropbox, or Google Drive. (Demo, Source Code) AGPL-3.0 Docker
• Gossa - Light and simple webserver for your files. MIT Go
• IFM - Single script file manager. MIT PHP
• mikochi - Browse remote folders, upload files, delete, rename, download and stream files to VLC/mpv. MIT Go/Docker/K8S
• miniserve - CLI tool to serve files and dirs over HTTP. MIT Rust
• ResourceSpace - ResourceSpace open source digital asset management software is the simple, fast, and free way to organise your digital assets. (Demo, Source Code) BSD-4-Clause PHP
• Surfer - Simple static file server with webui to manage files. MIT Nodejs
• TagSpaces - TagSpaces is an offline, cross-platform file manager and organiser that also can function as a note taking app. The WebDAV version of the application can be installed on top of a WebDAV servers such as Nextcloud or ownCloud. (Demo, Source Code) AGPL-3.0 Nodejs
• Tiny File Manager - Web based File Manager in PHP, simple, fast and small file manager with a single file. (Demo, Source Code) GPL-3.0 PHP

@ b0a838f2:34ed3f19

• Chibisafe - File uploader service that aims to to be easy to use and set up. It accepts files, photos, documents, anything you imagine and gives you back a shareable link for you to send to others. (Source Code) MIT Docker/Nodejs
• Digirecord - Record and share audio files (documentation in French). (Source Code) AGPL-3.0 Nodejs/PHP
• elixire - Simple yet advanced screenshot uploading and link shortening service. (Clients) AGPL-3.0 Python
• Enclosed - Minimalistic web application designed for sending private and secure notes. (Demo, Source Code) Apache-2.0 Docker/Nodejs
• Files Sharing - File sharing application based on unique and temporary links. GPL-3.0 PHP/Docker
• Gokapi - Lightweight server to share files, which expire after a set amount of downloads or days. Similar to the discontinued Firefox Send, with the difference that only the admin is allowed to upload files. GPL-3.0 Go/Docker
• goploader - Easy file sharing with server-side encryption, curl/httpie/wget compliant. (Source Code) MIT Go
• GoSƐ - Modern file-uploader focusing on scalability and simplicity. It only depends on a S3 storage backend and hence scales horizontally without the need for additional databases or caches. Apache-2.0 Go/Docker
• OnionShare - Securely and anonymously share a file of any size. GPL-3.0 Python/deb
• Pairdrop - Local file sharing in your browser, inspired by Apple's AirDrop (fork of Snapdrop). (Source Code) GPL-3.0 Docker
• PicoShare - Minimalist, easy-to-host service for sharing images and other files. (Demo, Source Code) AGPL-3.0 Go/Docker
• Picsur - Simple imaging hosting platform that allows you to easily host, edit, and share images. (Demo) AGPL-3.0 Docker
• PictShare - Multi lingual image hosting service with a simple resizing and upload API. (Source Code) Apache-2.0 PHP/Docker
• Pingvin Share - File sharing platform that combines lightness and beauty, perfect for seamless and efficient file sharing. (Demo) BSD-2-Clause Docker/Nodejs
• Plik - Scalable and friendly temporary file upload system. (Demo) MIT Go/Docker
• ProjectSend - Upload files and assign them to specific clients you create. Give access to those files to your clients. (Source Code) GPL-2.0 PHP
• PsiTransfer - Simple file sharing solution with robust up-/download-resume and password protection. BSD-2-Clause Nodejs
• QuickShare - Quick and simple file sharing between different devices. (Source Code) LGPL-3.0 Docker/Go
• Sharry - Share files easily over the internet between authenticated and anonymous users (both ways) with resumable up- and downloads. GPL-3.0 Scala/Java/deb/Docker
• Shifter - A simple, self-hosted file-sharing web app, powered by Django. MIT Docker
• Slink - Image sharing platform designed to give users complete control over their media sharing experience. (Source Code) AGPL-3.0 Docker
• transfer.sh - Easy file sharing from the command line. MIT Go
• Uguu - Stores files and deletes after X amount of time. MIT PHP
• Uploady - Uploady is a simple file uploader script with multi file upload support. MIT PHP
• XBackBone - A simple, fast and lightweight file manager with instant sharing tools integration, like ShareX (a free and open-source screenshot utility for Windows). (Source Code) AGPL-3.0 PHP/Docker
• Zipline - A lightweight, fast and reliable file sharing server that is commonly used with ShareX, offering a react-based Web UI and fast API. MIT Docker/Nodejs

@ b0a838f2:34ed3f19

• bittorrent-tracker - Simple, robust, BitTorrent tracker (client and server) implementation. (Source Code) MIT Nodejs
• Deluge - Lightweight, cross-platform BitTorrent client. (Source Code) GPL-3.0 Python/deb
• qBittorrent - Free cross-platform bittorrent client with a feature rich Web UI for remote access. (Source Code) GPL-2.0 C++
• Send - Simple, private, end to end encrypted temporary file sharing, originally built by Mozilla. (Clients) MPL-2.0 Nodejs/Docker
• slskd ⚠ - A modern client-server application for the Soulseek file sharing network. AGPL-3.0 Docker/C#
• Transmission - Fast, easy, free Bittorrent client. (Source Code) GPL-3.0 C++/deb
• Webtor - Web-based torrent client with instant audio/video streaming. (Demo) MIT Docker

@ b0a838f2:34ed3f19

• GarageHQ - Geo-distributed, S3‑compatible storage service that can fulfill many needs. (Source Code) AGPL-3.0 Docker/Rust
• Minio - Object storage server compatible with Amazon S3 APIs. (Source Code) AGPL-3.0 Go/Docker/K8S
• SeaweedFS - SeaweedFS is an open source distributed file system supporting WebDAV, S3 API, FUSE mount, HDFS, etc, optimized for lots of small files, and easy to add capacity. Apache-2.0 Go
• SFTPGo - Flexible, fully featured and highly configurable SFTP server with optional FTP/S and WebDAV support. AGPL-3.0 Go/deb/Docker
• Zenko CloudServer - Zenko CloudServer, an open-source implementation of a server handling the Amazon S3 protocol. (Source Code) Apache-2.0 Docker/Nodejs
• ZOT OCI Registry - A production-ready vendor-neutral OCI-native container image registry. (Demo, Source Code) Apache-2.0 Go/Docker

@ b0a838f2:34ed3f19

• bewCloud - File sharing + sync, notes, and photos (alternative to Nextcloud and ownCloud's RSS reader). (Source Code, Clients) AGPL-3.0 Docker
• Git Annex - File synchronization between computers, servers, external drives. (Source Code) GPL-3.0 Haskell
• Kinto - Minimalist JSON storage service with synchronisation and sharing abilities. (Source Code) Apache-2.0 Python
• Nextcloud - Access and share your files, calendars, contacts, mail and more from any device, on your terms. (Demo, Source Code) AGPL-3.0 PHP/deb
• OpenSSH SFTP server - Secure File Transfer Program. (Source Code) BSD-2-Clause C/deb
• ownCloud - All-in-one solution for saving, synchronizing, viewing, editing and sharing files, calendars, address books and more. (Source Code, Clients) AGPL-3.0 PHP/Docker/deb
• Peergos - Secure and private space online where you can store, share and view your photos, videos, music and documents. Also includes a calendar, news feed, task lists, chat and email client. (Source Code) AGPL-3.0 Java
• Puter - Web-based operating system designed to be feature-rich, exceptionally fast, and highly extensible. (Demo, Source Code) AGPL-3.0 Nodejs/Docker
• Pydio - Turn any web server into a powerful file management system and an alternative to mainstream cloud storage providers. (Demo, Source Code) AGPL-3.0 Go
• Samba - Samba is the standard Windows interoperability suite of programs for Linux and Unix. It provides secure, stable and fast file and print services for all clients using the SMB/CIFS protocol. (Source Code) GPL-3.0 C
• Seafile - File hosting and sharing solution primary for teams and organizations. (Source Code) GPL-2.0/GPL-3.0/AGPL-3.0/Apache-2.0 C
• Syncthing - Syncthing is an open source peer-to-peer file synchronisation tool. (Source Code) MPL-2.0 Go/Docker/deb
• Unison - Unison is a file-synchronization tool for OSX, Unix, and Windows. (Source Code) GPL-3.0 deb/OCaml

@ 40b9c85f:5e61b451

Introduction

Data Vending Machines (DVMs) have emerged as a crucial component of the Nostr ecosystem, offering specialized computational services to clients across the network. As defined in NIP-90, DVMs operate on an apparently simple principle: "data in, data out." They provide a marketplace for data processing where users request specific jobs (like text translation, content recommendation, or AI text generation)

While DVMs have gained significant traction, the current specification faces challenges that hinder widespread adoption and consistent implementation. This article explores some ideas on how we can apply the reflection pattern, a well established approach in RPC systems, to address these challenges and improve the DVM ecosystem's clarity, consistency, and usability.

The Current State of DVMs: Challenges and Limitations

The NIP-90 specification provides a broad framework for DVMs, but this flexibility has led to several issues:

1. Inconsistent Implementation

As noted by hzrd149 in "DVMs were a mistake" every DVM implementation tends to expect inputs in slightly different formats, even while ostensibly following the same specification. For example, a translation request DVM might expect an event ID in one particular format, while an LLM service could expect a "prompt" input that's not even specified in NIP-90.

2. Fragmented Specifications

The DVM specification reserves a range of event kinds (5000-6000), each meant for different types of computational jobs. While creating sub-specifications for each job type is being explored as a possible solution for clarity, in a decentralized and permissionless landscape like Nostr, relying solely on specification enforcement won't be effective for creating a healthy ecosystem. A more comprehensible approach is needed that works with, rather than against, the open nature of the protocol.

3. Ambiguous API Interfaces

There's no standardized way for clients to discover what parameters a specific DVM accepts, which are required versus optional, or what output format to expect. This creates uncertainty and forces developers to rely on documentation outside the protocol itself, if such documentation exists at all.

The Reflection Pattern: A Solution from RPC Systems

The reflection pattern in RPC systems offers a compelling solution to many of these challenges. At its core, reflection enables servers to provide metadata about their available services, methods, and data types at runtime, allowing clients to dynamically discover and interact with the server's API.

In established RPC frameworks like gRPC, reflection serves as a self-describing mechanism where services expose their interface definitions and requirements. In MCP reflection is used to expose the capabilities of the server, such as tools, resources, and prompts. Clients can learn about available capabilities without prior knowledge, and systems can adapt to changes without requiring rebuilds or redeployments. This standardized introspection creates a unified way to query service metadata, making tools like grpcurl possible without requiring precompiled stubs.

How Reflection Could Transform the DVM Specification

By incorporating reflection principles into the DVM specification, we could create a more coherent and predictable ecosystem. DVMs already implement some sort of reflection through the use of 'nip90params', which allow clients to discover some parameters, constraints, and features of the DVMs, such as whether they accept encryption, nutzaps, etc. However, this approach could be expanded to provide more comprehensive self-description capabilities.

1. Defined Lifecycle Phases

Similar to the Model Context Protocol (MCP), DVMs could benefit from a clear lifecycle consisting of an initialization phase and an operation phase. During initialization, the client and DVM would negotiate capabilities and exchange metadata, with the DVM providing a JSON schema containing its input requirements. nip-89 (or other) announcements can be used to bootstrap the discovery and negotiation process by providing the input schema directly. Then, during the operation phase, the client would interact with the DVM according to the negotiated schema and parameters.

2. Schema-Based Interactions

Rather than relying on rigid specifications for each job type, DVMs could self-advertise their schemas. This would allow clients to understand which parameters are required versus optional, what type validation should occur for inputs, what output formats to expect, and what payment flows are supported. By internalizing the input schema of the DVMs they wish to consume, clients gain clarity on how to interact effectively.

3. Capability Negotiation

Capability negotiation would enable DVMs to advertise their supported features, such as encryption methods, payment options, or specialized functionalities. This would allow clients to adjust their interaction approach based on the specific capabilities of each DVM they encounter.

Implementation Approach

While building DVMCP, I realized that the RPC reflection pattern used there could be beneficial for constructing DVMs in general. Since DVMs already follow an RPC style for their operation, and reflection is a natural extension of this approach, it could significantly enhance and clarify the DVM specification.

A reflection enhanced DVM protocol could work as follows: 1. Discovery: Clients discover DVMs through existing NIP-89 application handlers, input schemas could also be advertised in nip-89 announcements, making the second step unnecessary. 2. Schema Request: Clients request the DVM's input schema for the specific job type they're interested in 3. Validation: Clients validate their request against the provided schema before submission 4. Operation: The job proceeds through the standard NIP-90 flow, but with clearer expectations on both sides

Parallels with Other Protocols

This approach has proven successful in other contexts. The Model Context Protocol (MCP) implements a similar lifecycle with capability negotiation during initialization, allowing any client to communicate with any server as long as they adhere to the base protocol. MCP and DVM protocols share fundamental similarities, both aim to expose and consume computational resources through a JSON-RPC-like interface, albeit with specific differences.

gRPC's reflection service similarly allows clients to discover service definitions at runtime, enabling generic tools to work with any gRPC service without prior knowledge. In the REST API world, OpenAPI/Swagger specifications document interfaces in a way that makes them discoverable and testable.

DVMs would benefit from adopting these patterns while maintaining the decentralized, permissionless nature of Nostr.

Conclusion

I am not attempting to rewrite the DVM specification; rather, explore some ideas that could help the ecosystem improve incrementally, reducing fragmentation and making the ecosystem more comprehensible. By allowing DVMs to self describe their interfaces, we could maintain the flexibility that makes Nostr powerful while providing the structure needed for interoperability.

For developers building DVM clients or libraries, this approach would simplify consumption by providing clear expectations about inputs and outputs. For DVM operators, it would establish a standard way to communicate their service's requirements without relying on external documentation.

I am currently developing DVMCP following these patterns. Of course, DVMs and MCP servers have different details; MCP includes capabilities such as tools, resources, and prompts on the server side, as well as 'roots' and 'sampling' on the client side, creating a bidirectional way to consume capabilities. In contrast, DVMs typically function similarly to MCP tools, where you call a DVM with an input and receive an output, with each job type representing a different categorization of the work performed.

Without further ado, I hope this article has provided some insight into the potential benefits of applying the reflection pattern to the DVM specification.

@ b0a838f2:34ed3f19

• Bubo Reader - Irrationally minimal RSS feed reader. (Demo) MIT Nodejs
• CommaFeed - Google Reader inspired self-hosted RSS reader. (Demo, Source Code) Apache-2.0 Java/Docker
• FeedCord ⚠ - Simple, lightweight & customizable RSS News Feed for your Discord Server. MIT Docker
• Feedpushr - Powerful RSS aggregator, able to transform and send articles to many outputs. Single binary, extensible with plugins. GPL-3.0 Go/Docker
• Feeds Fun - News reader with tags, scoring, and AI. (Source Code) BSD-3-Clause Python
• FreshRSS - Self-hostable RSS feed aggregator. (Demo, Source Code) AGPL-3.0 PHP/Docker
• Fusion - Lightweight RSS aggregator and reader. MIT Go/Docker
• JARR - JARR (Just Another RSS Reader) is a web-based news aggregator and reader (fork of Newspipe). (Demo, Source Code) AGPL-3.0 Docker/Python
• Kriss Feed - Simple and smart (or stupid) feed reader. CC0-1.0 PHP
• Leed - Leed (for Light Feed) is a Free and minimalist RSS aggregator. AGPL-3.0 PHP
• Miniflux - Minimalist news reader. (Source Code) Apache-2.0 Go/deb/Docker
• NewsBlur - Personal news reader that brings people together to talk about the world. A new sound of an old instrument. (Source Code) MIT Python
• Newspipe - Web news reader. (Demo) AGPL-3.0 Python
• Precis - Extensibility-oriented RSS reader that can use LLMs (including local LLMs) to summarize RSS entries with built-in notification support. MIT Python/Docker
• reader - A Python feed reader web app and library (so you can use it to build your own), with only standard library and pure-Python dependencies. BSD-3-Clause Python
• Readflow - Lightweight news reader with modern interface and features: full-text search, automatic categorization, archiving, offline support, notifications... (Source Code) MIT Go/Docker
• RSS-Bridge - Generate RSS/ATOM feeds for websites which don't have one. Unlicense PHP/Docker
• RSS Monster - An easy to use web-based RSS aggregator and reader compatible with the Fever API (alternative to Google Reader). MIT PHP
• RSS2EMail - Fetches RSS/Atom-feeds and pushes new Content to any email-receiver, supports OPML. GPL-2.0 Python/deb
• RSSHub - An easy to use, and extensible RSS feed aggregator, it's capable of generating RSS feeds from pretty much everything ranging from social media to university departments. (Demo, Source Code) MIT Nodejs/Docker
• Selfoss - New multipurpose rss reader, live stream, mashup, aggregation web application. (Source Code) GPL-3.0 PHP
• Stringer - Work-in-progress self-hosted, anti-social RSS reader. MIT Ruby
• Tiny Tiny RSS - Open source web-based news feed (RSS/Atom) reader and aggregator. (Demo, Source Code) GPL-3.0 Docker/PHP
• Yarr - Yarr (yet another rss reader) is a web-based feed aggregator which can be used both as a desktop application and a personal self-hosted server. MIT Go

@ b0a838f2:34ed3f19

• Aimeos - E-commerce framework for building custom online shops, market places and complex B2B applications scaling to billions of items with Laravel. (Demo, Source Code) LGPL-3.0/MIT PHP
• Bagisto - Leading Laravel open source e-commerce framework with multi-inventory sources, taxation, localization, dropshipping and more exciting features. (Demo, Source Code) MIT PHP
• CoreShop - E-commerce plugin for Pimcore. (Source Code) GPL-3.0 PHP
• Drupal Commerce - Popular e-commerce module for Drupal CMS, with support for dozens of payment, shipping, and shopping related modules. (Source Code) GPL-2.0 PHP
• EverShop ⚠ - E-commerce platform with essential commerce features. Modular architecture and fully customizable. (Demo, Source Code) GPL-3.0 Docker/Nodejs
• Litecart ⚠ - Shopping cart in 1 file (with support for payment by card or cryptocurrency). MIT Go/Docker
• Magento Open Source - Leading provider of open omnichannel innovation. (Source Code) OSL-3.0 PHP
• MedusaJs - Headless commerce engine that enables developers to create amazing digital commerce experiences. (Demo, Source Code) MIT Nodejs
• Microweber - Drag and Drop CMS and online shop. (Source Code) MIT PHP
• Open Source POS - Open Source Point of Sale is a web based point of sale system. MIT PHP
• OpenCart - Shopping cart solution. (Source Code) GPL-3.0 PHP
• PrestaShop - Fully scalable e-commerce solution. (Demo, Source Code) OSL-3.0 PHP
• Pretix - Ticket sales platform for events. (Source Code) AGPL-3.0 Python/Docker
• s-cart - S-Cart is a free e-commerce website project for individuals and businesses, built on top of Laravel Framework. (Demo, Source Code) MIT PHP
• Saleor - Django based open-sourced e-commerce storefront. (Demo, Source Code) BSD-3-Clause Docker/Python
• Shopware Community Edition - PHP based open source e-commerce software made in Germany. (Demo, Source Code) MIT PHP
• Solidus - A free, open-source ecommerce platform that gives you complete control over your store. (Source Code) BSD-3-Clause Ruby/Docker
• Spree Commerce - Spree is a complete, modular & API-driven open source e-commerce solution for Ruby on Rails. (Demo, Source Code) BSD-3-Clause Ruby
• Sylius - Symfony2 powered open source full-stack platform for eCommerce. (Demo, Source Code) MIT PHP
• Thelia - Thelia is an open source and flexible e-commerce solution. (Demo, Source Code) LGPL-3.0 PHP
• Vendure - A headless commerce framework. (Demo, Source Code) MIT Nodejs
• WooCommerce - WordPress based e-commerce solution. (Source Code) GPL-3.0 PHP

@ b2caa9b3:9eab0fb5

Yesterday, I faced one of the most heartbreaking and frustrating experiences of my life. Between 10:00 AM and 2:00 PM, I was held at the Taveta border, denied entry into Kenya—despite having all the necessary documents, including a valid visitor’s permit and an official invitation letter.

The Kenyan Immigration officers refused to speak with me. When I asked for clarification, I was told flatly that I would never be allowed to enter Kenya unless I obtain a work permit. No other reason was given. My attempts to explain that I simply wanted to see my child were ignored. No empathy. No flexibility. No conversation. Just rejection.

While I stood there for hours, held by officials with no explanation beyond a bureaucratic wall, I recorded the experience. I now have several hours of footage documenting what happened—a silent testimony to how a system can dehumanize and block basic rights.

And the situation doesn’t end at the border.

My child, born in Kenya, is also being denied the right to see me. Germany refuses to grant her citizenship, which means she cannot visit me either. The German embassy in Nairobi refuses to assist, stating they won’t get involved. Their silence is loud.

This is not just about paperwork. This is about a child growing up without her father. It’s about a system that chooses walls over bridges, and bureaucracy over humanity. Kenya, by refusing me entry, is keeping a father away from his child. Germany, by refusing to act under §13 StGB, is complicit in that injustice.

In the coming days, I’ll share more about my past travels and how this situation unfolded. I’ll also be releasing videos and updates on TikTok—because this story needs to be heard. Not just for me, but for every parent and child caught between borders and bureaucracies.

Stay tuned—and thank you for standing with me.

@ b0a838f2:34ed3f19

• Evergreen - Highly-scalable software for libraries that helps library patrons find library materials, and helps libraries manage, catalog, and circulate those materials. (Source Code) GPL-2.0 PLpgSQL
• Koha - Enterprise-class ILS with modules for acquisitions, circulation, cataloging, label printing, offline circulation for when Internet access is not available, and much more. (Demo, Source Code) GPL-3.0 Perl
• RERO ILS - Large-scale ILS that can be run as a service with consortial features, intended primarily for library networks. Includes most standard modules (circulation, acquisitions, cataloging,...) and a web-based public and professional interface. (Demo, Source Code) AGPL-3.0 Python/Docker

@ 9bde4214:06ca052b

"It's gonna be permissionless or hell."

Gigi and gzuuus are vibing towards dystopia.

Books & articles mentioned:

• AI 2027
• DVMs were a mistake
• Careless People by Sarah Wynn-Williams
• Takedown by Laila michelwait
• The Ultimate Resource by Julian L. Simon
• Harry Potter by J.K. Rowling
• Momo by Michael Ende

In this dialogue:

• Pablo's Roo Setup
• Tech Hype Cycles
• AI 2027
• Prompt injection and other attacks
• Goose and DVMCP
• Cursor vs Roo Code
• Staying in control thanks to Amber and signing delegation
• Is YOLO mode here to stay?
• What agents to trust?
• What MCP tools to trust?
• What code snippets to trust?
• Everyone will run into the issues of trust and micropayments
• Nostr solves Web of Trust & micropayments natively
• Minimalistic & open usually wins
• DVMCP exists thanks to Totem
• Relays as Tamagochis
• Agents aren't nostr experts, at least not right now
• Fix a mistake once & it's fixed forever
• Giving long-term memory to LLMs
• RAG Databases signed by domain experts
• Human-agent hybrids & Chess
• Nostr beating heart
• Pluggable context & experts
• "You never need an API key for anything"
• Sats and social signaling
• Difficulty-adjusted PoW as a rare-limiting mechanism
• Certificate authorities and centralization
• No solutions to policing speech!
• OAuth and how it centralized
• Login with nostr
• Closed vs open-source models
• Tiny models vs large models
• The minions protocol (Stanford paper)
• Generalist models vs specialized models
• Local compute & encrypted queries
• Blinded compute
• "In the eyes of the state, agents aren't people"
• Agents need identity and money; nostr provides both
• "It's gonna be permissionless or hell"
• We already have marketplaces for MCP stuff, code snippets, and other things
• Most great stuff came from marketplaces (browsers, games, etc)
• Zapstore shows that this is already working
• At scale, central control never works. There's plenty scams and viruses in the app stores.
• Using nostr to archive your user-generated content
• HAVEN, blossom, novia
• The switcharoo from advertisements to training data
• What is Truth?
• What is Real?
• "We're vibing into dystopia"
• Who should be the arbiter of Truth?
• First Amendment & why the Logos is sacred
• Silicon Valley AI bros arrogantly dismiss wisdom and philosophy
• Suicide rates & the meaning crisis
• Are LLMs symbiotic or parasitic?
• The Amish got it right
• Are we gonna make it?
• Careless People by Sarah Wynn-Williams
• Takedown by Laila michelwait
• Harry Potter dementors & Momo's time thieves
• Facebook & Google as non-human (superhuman) agents
• Zapping as a conscious action
• Privacy and the internet
• Plausible deniability thanks to generative models
• Google glasses, glassholes, and Meta's Ray Ben's
• People crave realness
• Bitcoin is the realest money we ever had
• Nostr allows for real and honest expression
• How do we find out what's real?
• Constraints, policing, and chilling effects
• Jesus' plans for DVMCP
• Hzrd's article on how DVMs are broken (DVMs were a mistake)
• Don't believe the hype
• DVMs pre-date MCP tools
• Data Vending Machines were supposed to be stupid: put coin in, get stuff out.
• Self-healing vibe-coding
• IP addresses as scarce assets
• Atomic swaps and the ASS protocol
• More marketplaces, less silos
• The intensity of #SovEng and the last 6 weeks
• If you can vibe-code everything, why build anything?
• Time, the ultimate resource
• What are the LLMs allowed to think?
• Natural language interfaces are inherently dialogical
• Sovereign Engineering is dialogical too

@ d9e9fb27:d5fe5e1a

"There are two pillars in Costa Rica, education and coffee." A tourist guide I met told me this, and during the trip I discovered the strong link between coffee and the locals.

In fact, coffee runs very deeply in the Ticos' culture. So deep that the summer vacations from school (November to January) coincide with the coffee collection season. Children had to help their parents with the coffee. Coffee was a family business.

Monteverde, in the region of Puentarenas, is one of those places where coffee ha always been a corner stone of the society. Here, My gf and I went to visit a coffee plantation and discovered how coffee is made.

---

Monteverde

Monteverde is a well-known turistic location in the central part of Costa Rica. Many people reach this beautiful place to visit the famous Cloud Rainforest, acres and acres of pristine forest, with many different kind of animals and plants living in it.

However, other than tourism is coffee that pushes the economy of this place. The hills around the town are covered with coffee plantations and there are tours than try to explain how coffee is made.

Coffee Tours

While we were in Monteverde, we joined one of these tours. We decided to give credit to a smaller plantation instead of the super turistic ones. A more rustic and family-owned business, El Pueblo Coffee Tour. We were not disappointed. We had the show all to ourselves, a super-prepared guide and all the time to make questions and enjoy with no rush.

The Plant of Coffee

Since Costa Rica is a quite small country, to compete on the market producers decided to bet on quality instead of quantity. That's why, the only type produced here is the Arabica.

Before the coffee bean, the plant produces a nice white flower, similar to the jasmine.

After a while, the coffee beans appear.

As soon as they turn red, they are ready to be collected.

Interesting fact: between the coffee plants many fruit trees like mangos or bananos can be found. In fact, those plants help keep the soil fertile and healthy, thus leading to a higher coffee quality!

Coffee Harvesting

Coffee is still harvested by hand. Beans do not get mature at the same time, so manual labor is needed. Laborer use a very simple tool to collect coffee, one which allow them to have both hands free.

Workers do not get paid by hours, but by the number of cajuelas that they can fill. A cajuela is a standard box, which contains around 13kg of beans. It's divided into quarters, so that the worker can get paid for the quarter, too.

Each cajuela is paid around 3.50$.

Coffee Drying

In the farm we visited, drying was perfomed naturally, through the heat of the sun. There are three ways in which the bean is left to dry: lavado, miel and naturàl.

• Lavado: The beans are peeled and washed to remove the jelly.

- Miel: The jelly on the beans is maintained to give it more sweet flavour.

- Naturàl: The bean is left to dry with its peel on, to give it a more fruity taste.

Back in the days, to peel the beans for the lavado and the miel variety, the pìlon was used. The bean is very hard, thus this tool does not damage it.

However, today the peeling procedure is done using a machine.

Coffee Roasting

The last step in the production of coffee is roasting. Coffee is put inside a sort of hoven, and is left there at high temperature according to the level of roasting that is needed. The more roasting, the less caffeine there is and the more bitter the coffee. Usually you have light, medium and dark roast.

Coffee Tasting

In the end, we also had a coffee tasting. We tried different roasting and different varieties.

Our guide explained us the best way to taste coffee and helped us defining the different flavours that we perceived. He also taught us the best way to prepare it: infusion time, water temperature, coffe makers and so on.

My favorite one was the dark one, while my gf enjoyed the light roast more. Of course, we bought some packs of these varieties!

---

Thanks for tuning in!

I hope you enjoyed this brief overview of the Costa Rican coffee.

Pura Vida

Tuma

@ 266815e0:6cd408a5

Its been a little over a year since NIP-90 was written and merged into the nips repo and its been a communication mess.

Every DVM implementation expects the inputs in slightly different formats, returns the results in mostly the same format and there are very few DVM actually running.

NIP-90 is overloaded

Why does a request for text translation and creating bitcoin OP_RETURNs share the same input i tag? and why is there an output tag on requests when only one of them will return an output?

Each DVM request kind is for requesting completely different types of compute with diffrent input and output requirements, but they are all using the same spec that has 4 different types of inputs (text, url, event, job) and an undefined number of output types.

Let me show a few random DVM requests and responses I found on wss://relay.damus.io to demonstrate what I mean:

This is a request to translate an event to English json { "kind": 5002, "content": "", "tags": [ // NIP-90 says there can be multiple inputs, so how would a DVM handle translatting multiple events at once? [ "i", "<event-id>", "event" ], [ "param", "language", "en" ], // What other type of output would text translations be? image/jpeg? [ "output", "text/plain" ], // Do we really need to define relays? cant the DVM respond on the relays it saw the request on? [ "relays", "wss://relay.unknown.cloud/", "wss://nos.lol/" ] ] }

This is a request to generate text using an LLM model json { "kind": 5050, // Why is the content empty? wouldn't it be better to have the prompt in the content? "content": "", "tags": [ // Why use an indexable tag? are we ever going to lookup prompts? // Also the type "prompt" isn't in NIP-90, this should probably be "text" [ "i", "What is the capital of France?", "prompt" ], [ "p", "c4878054cff877f694f5abecf18c7450f4b6fdf59e3e9cb3e6505a93c4577db2" ], [ "relays", "wss://relay.primal.net" ] ] }

This is a request for content recommendation json { "kind": 5300, "content": "", "tags": [ // Its fine ignoring this param, but what if the client actually needs exactly 200 "results" [ "param", "max_results", "200" ], // The spec never mentions requesting content for other users. // If a DVM didn't understand this and responded to this request it would provide bad data [ "param", "user", "b22b06b051fd5232966a9344a634d956c3dc33a7f5ecdcad9ed11ddc4120a7f2" ], [ "relays", "wss://relay.primal.net", ], [ "p", "ceb7e7d688e8a704794d5662acb6f18c2455df7481833dd6c384b65252455a95" ] ] }

This is a request to create a OP_RETURN message on bitcoin json { "kind": 5901, // Again why is the content empty when we are sending human readable text? "content": "", "tags": [ // and again, using an indexable tag on an input that will never need to be looked up ["i", "09/01/24 SEC Chairman on the brink of second ETF approval", "text"] ] }

My point isn't that these event schema's aren't understandable but why are they using the same schema? each use-case is different but are they all required to use the same i tag format as input and could support all 4 types of inputs.

Lack of libraries

With all these different types of inputs, params, and outputs its verify difficult if not impossible to build libraries for DVMs

If a simple text translation request can have an event or text as inputs, a payment-required status at any point in the flow, partial results, or responses from 10+ DVMs whats the best way to build a translation library for other nostr clients to use?

And how do I build a DVM framework for the server side that can handle multiple inputs of all four types (url, text, event, job) and clients are sending all the requests in slightly differently.

Supporting payments is impossible

The way NIP-90 is written there isn't much details about payments. only a payment-required status and a generic amount tag

But the way things are now every DVM is implementing payments differently. some send a bolt11 invoice, some expect the client to NIP-57 zap the request event (or maybe the status event), and some even ask for a subscription. and we haven't even started implementing NIP-61 nut zaps or cashu A few are even formatting the amount number wrong or denominating it in sats and not mili-sats

Building a client or a library that can understand and handle all of these payment methods is very difficult. for the DVM server side its worse. A DVM server presumably needs to support all 4+ types of payments if they want to get the most sats for their services and support the most clients.

All of this is made even more complicated by the fact that a DVM can ask for payment at any point during the job process. this makes sense for some types of compute, but for others like translations or user recommendation / search it just makes things even more complicated.

For example, If a client wanted to implement a timeline page that showed the notes of all the pubkeys on a recommended list. what would they do when the selected DVM asks for payment at the start of the job? or at the end? or worse, only provides half the pubkeys and asks for payment for the other half. building a UI that could handle even just two of these possibilities is complicated.

NIP-89 is being abused

NIP-89 is "Recommended Application Handlers" and the way its describe in the nips repo is

a way to discover applications that can handle unknown event-kinds

Not "a way to discover everything"

If I wanted to build an application discovery app to show all the apps that your contacts use and let you discover new apps then it would have to filter out ALL the DVM advertisement events. and that's not just for making requests from relays

If the app shows the user their list of "recommended applications" then it either has to understand that everything in the 5xxx kind range is a DVM and to show that is its own category or show a bunch of unknown "favorites" in the list which might be confusing for the user.

In conclusion

My point in writing this article isn't that the DVMs implementations so far don't work, but that they will never work well because the spec is too broad. even with only a few DVMs running we have already lost interoperability.

I don't want to be completely negative though because some things have worked. the "DVM feeds" work, although they are limited to a single page of results. text / event translations also work well and kind 5970 Event PoW delegation could be cool. but if we want interoperability, we are going to need to change a few things with NIP-90

I don't think we can (or should) abandon NIP-90 entirely but it would be good to break it up into small NIPs or specs. break each "kind" of DVM request out into its own spec with its own definitions for expected inputs, outputs and flow.

Then if we have simple, clean definitions for each kind of compute we want to distribute. we might actually see markets and services being built and used.

@ b0a838f2:34ed3f19

• DSpace - Turnkey repository application providing durable access to digital resources. (Source Code) BSD-3-Clause Java
• EPrints - Digital document management system with a flexible metadata and workflow model primarily aimed at academic institutions. (Demo, Source Code) GPL-3.0 Perl
• Fedora Commons Repository - Robust and modular repository system for the management and dissemination of digital content especially suited for digital libraries and archives, both for access and preservation. (Source Code) Apache-2.0 Java
• InvenioRDM - Highly scalable turn-key research data management platform with a beautiful user experience. (Demo, Source Code, Clients) MIT Python
• Islandora - Drupal module for browsing and managing Fedora-based digital repositories. (Demo, Source Code) GPL-3.0 PHP
• Samvera Hyrax - Front-end for the Samvera framework, which itself is a Ruby on Rails application for browsing and managing Fedora-based digital repositories. (Source Code) Apache-2.0 Ruby

@ b0a838f2:34ed3f19

• Atsumeru - Manga/comic/light novel media server with clients for Windows, Linux, macOS and Android. (Source Code, Clients) MIT Java/Docker
• BookLogr - Manage your personal book library with ease. (Demo) Apache-2.0 Docker
• Calibre Web - Browse, read and download eBooks using an existing Calibre database. GPL-3.0 Python
• Calibre - E-book library manager that can view, convert, and catalog e-books in most of the major e-book formats and provides a built-in Web server for remote clients. (Demo, Source Code) GPL-3.0 Python/deb
• Kapowarr - Build and manage a comic book library. Download, rename, move and convert issues of the volume to your liking. (Source Code) GPL-3.0 Docker/Python
• Kavita - Cross-platform e-book/manga/comic/pdf server and web reader with user management, ratings and reviews, and metadata support. (Demo, Source Code) GPL-3.0 .NET/Docker
• kiwix-serve - HTTP daemon for serving wikis from ZIM files. (Source Code) GPL-3.0 C++
• Komga - Media server for comics/mangas/BDs with API and OPDS support, a modern web interface for exploring your libraries, as well as a web reader. (Source Code) MIT Java/Docker
• Librum - Modern e-book reader and library manager that supports most major book formats, runs on all devices and offers great tools to boost productivity. (Source Code) GPL-3.0 C++
• Stump - A fast, free and open source comics, manga and digital book server with OPDS support. (Source Code) MIT Rust
• The Epube - Self-hosted web EPUB reader using EPUB.js, Bootstrap, and Calibre. (Source Code) GPL-3.0 PHP

@ b0a838f2:34ed3f19

• DocKing - Document management service/microservice that handles templates and renders them in PDF format, all in one place. (Demo, Source Code) MIT PHP/Nodejs/Docker
• Docspell - Auto-tagging document organizer and archive. (Source Code) GPL-3.0 Scala/Java/Docker
• Documenso - Digital document signing platform (alternative to DocuSign). (Source Code) AGPL-3.0 Nodejs/Docker
• Docuseal - Create, fill, and sign digital documents (alternative to DocuSign). (Demo, Source Code) AGPL-3.0 Docker
• EveryDocs - Simple Document Management System for private use with basic functionality to organize your documents digitally. GPL-3.0 Docker/Ruby
• Gotenberg - Developer-friendly API to interact with powerful tools like Chromium and LibreOffice for converting numerous document formats (HTML, Markdown, Word, Excel, etc.) into PDF files, and more. (Source Code) MIT Docker
• I, Librarian - Organize PDF papers and office documents. It provides a lot of extra features for students and research groups both in industry and academia. (Demo, Source Code) GPL-3.0 PHP
• Mayan EDMS - Electronic document management system for your documents with preview generation, OCR, and automatic categorization among other features. (Source Code) GPL-2.0 Docker/K8S
• OpenSign ⚠ - Document signing software (alternative to DocuSign). (Source Code) AGPL-3.0 Nodejs/Docker
• Paperless-ngx - Scan, index, and archive all of your paper documents with an improved interface (fork of Paperless). (Demo, Source Code) GPL-3.0 Python/Docker
• Papermerge - Document management system focused on scanned documents (electronic archives). Features file browsing in similar way to dropbox/google drive. OCR, full text search, text overlay/selection. (Source Code) Apache-2.0 Docker/K8S
• PdfDing - PDF manager, viewer and editor offering a seamless user experience on multiple devices. It's designed to be minimal, fast, and easy to set up using Docker. AGPL-3.0 Docker
• SeedDMS - Document Management System with workflows, access rights, fulltext search, and more. (Demo, Source Code) GPL-2.0 PHP
• Stirling-PDF - Local hosted web application that allows you to perform various operations on PDF files, such as merging, splitting, file conversions and OCR. Apache-2.0 Docker/Java
• Teedy - Lightweight document management system packed with all the features you can expect from big expensive solutions (Ex SismicsDocs). (Demo, Source Code) GPL-2.0 Docker/Java

@ b0a838f2:34ed3f19

• AdGuard Home - User-friendly ads & trackers blocking DNS server. (Source Code) GPL-3.0 Docker
• blocky - Fast and lightweight DNS proxy as ad-blocker for local network with many features (alternative to Pi-hole). (Source Code) Apache-2.0 Go/Docker
• Maza ad blocking - Local ad blocker. Like Pi-hole but local and using your operating system. (Source Code) Apache-2.0 Shell
• Pi-hole - Blackhole for Internet advertisements with a GUI for management and monitoring. (Source Code) EUPL-1.2 Shell/PHP/Docker
• Technitium DNS Server - Authoritative/recursive DNS server with ad blocking functionality. (Source Code) GPL-3.0 Docker/C#

@ 91bea5cd:1df4451c

Básico

bash lsblk # Lista todos os diretorios montados.

Para criar o sistema de arquivos:

bash mkfs.btrfs -L "ThePool" -f /dev/sdx

Criando um subvolume:

bash btrfs subvolume create SubVol

Montando Sistema de Arquivos:

bash mount -o compress=zlib,subvol=SubVol,autodefrag /dev/sdx /mnt

Lista os discos formatados no diretório:

bash btrfs filesystem show /mnt

Adiciona novo disco ao subvolume:

bash btrfs device add -f /dev/sdy /mnt

Lista novamente os discos do subvolume:

bash btrfs filesystem show /mnt

Exibe uso dos discos do subvolume:

bash btrfs filesystem df /mnt

Balancea os dados entre os discos sobre raid1:

bash btrfs filesystem balance start -dconvert=raid1 -mconvert=raid1 /mnt

Scrub é uma passagem por todos os dados e metadados do sistema de arquivos e verifica as somas de verificação. Se uma cópia válida estiver disponível (perfis de grupo de blocos replicados), a danificada será reparada. Todas as cópias dos perfis replicados são validadas.

iniciar o processo de depuração :

bash btrfs scrub start /mnt

ver o status do processo de depuração Btrfs em execução:

bash btrfs scrub status /mnt

ver o status do scrub Btrfs para cada um dos dispositivos

bash btrfs scrub status -d / data btrfs scrub cancel / data

Para retomar o processo de depuração do Btrfs que você cancelou ou pausou:

btrfs scrub resume / data

Listando os subvolumes:

bash btrfs subvolume list /Reports

Criando um instantâneo dos subvolumes:

Aqui, estamos criando um instantâneo de leitura e gravação chamado snap de marketing do subvolume de marketing.

bash btrfs subvolume snapshot /Reports/marketing /Reports/marketing-snap

Além disso, você pode criar um instantâneo somente leitura usando o sinalizador -r conforme mostrado. O marketing-rosnap é um instantâneo somente leitura do subvolume de marketing

bash btrfs subvolume snapshot -r /Reports/marketing /Reports/marketing-rosnap

Forçar a sincronização do sistema de arquivos usando o utilitário 'sync'

Para forçar a sincronização do sistema de arquivos, invoque a opção de sincronização conforme mostrado. Observe que o sistema de arquivos já deve estar montado para que o processo de sincronização continue com sucesso.

bash btrfs filsystem sync /Reports

Para excluir o dispositivo do sistema de arquivos, use o comando device delete conforme mostrado.

bash btrfs device delete /dev/sdc /Reports

Para sondar o status de um scrub, use o comando scrub status com a opção -dR .

bash btrfs scrub status -dR / Relatórios

Para cancelar a execução do scrub, use o comando scrub cancel .

bash $ sudo btrfs scrub cancel / Reports

Para retomar ou continuar com uma depuração interrompida anteriormente, execute o comando de cancelamento de depuração

bash sudo btrfs scrub resume /Reports

mostra o uso do dispositivo de armazenamento:

btrfs filesystem usage /data

Para distribuir os dados, metadados e dados do sistema em todos os dispositivos de armazenamento do RAID (incluindo o dispositivo de armazenamento recém-adicionado) montados no diretório /data , execute o seguinte comando:

sudo btrfs balance start --full-balance /data

Pode demorar um pouco para espalhar os dados, metadados e dados do sistema em todos os dispositivos de armazenamento do RAID se ele contiver muitos dados.

Opções importantes de montagem Btrfs

Nesta seção, vou explicar algumas das importantes opções de montagem do Btrfs. Então vamos começar.

As opções de montagem Btrfs mais importantes são:

**1. acl e noacl

**ACL gerencia permissões de usuários e grupos para os arquivos/diretórios do sistema de arquivos Btrfs.

A opção de montagem acl Btrfs habilita ACL. Para desabilitar a ACL, você pode usar a opção de montagem noacl .

Por padrão, a ACL está habilitada. Portanto, o sistema de arquivos Btrfs usa a opção de montagem acl por padrão.

**2. autodefrag e noautodefrag

**Desfragmentar um sistema de arquivos Btrfs melhorará o desempenho do sistema de arquivos reduzindo a fragmentação de dados.

A opção de montagem autodefrag permite a desfragmentação automática do sistema de arquivos Btrfs.

A opção de montagem noautodefrag desativa a desfragmentação automática do sistema de arquivos Btrfs.

Por padrão, a desfragmentação automática está desabilitada. Portanto, o sistema de arquivos Btrfs usa a opção de montagem noautodefrag por padrão.

**3. compactar e compactar-forçar

**Controla a compactação de dados no nível do sistema de arquivos do sistema de arquivos Btrfs.

A opção compactar compacta apenas os arquivos que valem a pena compactar (se compactar o arquivo economizar espaço em disco).

A opção compress-force compacta todos os arquivos do sistema de arquivos Btrfs, mesmo que a compactação do arquivo aumente seu tamanho.

O sistema de arquivos Btrfs suporta muitos algoritmos de compactação e cada um dos algoritmos de compactação possui diferentes níveis de compactação.

Os algoritmos de compactação suportados pelo Btrfs são: lzo , zlib (nível 1 a 9) e zstd (nível 1 a 15).

Você pode especificar qual algoritmo de compactação usar para o sistema de arquivos Btrfs com uma das seguintes opções de montagem:

• compress=algoritmo:nível
• compress-force=algoritmo:nível

Para obter mais informações, consulte meu artigo Como habilitar a compactação do sistema de arquivos Btrfs .

**4. subvol e subvolid

**Estas opções de montagem são usadas para montar separadamente um subvolume específico de um sistema de arquivos Btrfs.

A opção de montagem subvol é usada para montar o subvolume de um sistema de arquivos Btrfs usando seu caminho relativo.

A opção de montagem subvolid é usada para montar o subvolume de um sistema de arquivos Btrfs usando o ID do subvolume.

Para obter mais informações, consulte meu artigo Como criar e montar subvolumes Btrfs .

**5. dispositivo

A opção de montagem de dispositivo** é usada no sistema de arquivos Btrfs de vários dispositivos ou RAID Btrfs.

Em alguns casos, o sistema operacional pode falhar ao detectar os dispositivos de armazenamento usados em um sistema de arquivos Btrfs de vários dispositivos ou RAID Btrfs. Nesses casos, você pode usar a opção de montagem do dispositivo para especificar os dispositivos que deseja usar para o sistema de arquivos de vários dispositivos Btrfs ou RAID.

Você pode usar a opção de montagem de dispositivo várias vezes para carregar diferentes dispositivos de armazenamento para o sistema de arquivos de vários dispositivos Btrfs ou RAID.

Você pode usar o nome do dispositivo (ou seja, sdb , sdc ) ou UUID , UUID_SUB ou PARTUUID do dispositivo de armazenamento com a opção de montagem do dispositivo para identificar o dispositivo de armazenamento.

Por exemplo,

• dispositivo=/dev/sdb
• dispositivo=/dev/sdb,dispositivo=/dev/sdc
• dispositivo=UUID_SUB=490a263d-eb9a-4558-931e-998d4d080c5d
• device=UUID_SUB=490a263d-eb9a-4558-931e-998d4d080c5d,device=UUID_SUB=f7ce4875-0874-436a-b47d-3edef66d3424

**6. degraded

A opção de montagem degradada** permite que um RAID Btrfs seja montado com menos dispositivos de armazenamento do que o perfil RAID requer.

Por exemplo, o perfil raid1 requer a presença de 2 dispositivos de armazenamento. Se um dos dispositivos de armazenamento não estiver disponível em qualquer caso, você usa a opção de montagem degradada para montar o RAID mesmo que 1 de 2 dispositivos de armazenamento esteja disponível.

**7. commit

A opção commit** mount é usada para definir o intervalo (em segundos) dentro do qual os dados serão gravados no dispositivo de armazenamento.

O padrão é definido como 30 segundos.

Para definir o intervalo de confirmação para 15 segundos, você pode usar a opção de montagem commit=15 (digamos).

**8. ssd e nossd

A opção de montagem ssd** informa ao sistema de arquivos Btrfs que o sistema de arquivos está usando um dispositivo de armazenamento SSD, e o sistema de arquivos Btrfs faz a otimização SSD necessária.

A opção de montagem nossd desativa a otimização do SSD.

O sistema de arquivos Btrfs detecta automaticamente se um SSD é usado para o sistema de arquivos Btrfs. Se um SSD for usado, a opção de montagem de SSD será habilitada. Caso contrário, a opção de montagem nossd é habilitada.

**9. ssd_spread e nossd_spread

A opção de montagem ssd_spread** tenta alocar grandes blocos contínuos de espaço não utilizado do SSD. Esse recurso melhora o desempenho de SSDs de baixo custo (baratos).

A opção de montagem nossd_spread desativa o recurso ssd_spread .

O sistema de arquivos Btrfs detecta automaticamente se um SSD é usado para o sistema de arquivos Btrfs. Se um SSD for usado, a opção de montagem ssd_spread será habilitada. Caso contrário, a opção de montagem nossd_spread é habilitada.

**10. descarte e nodiscard

Se você estiver usando um SSD que suporte TRIM enfileirado assíncrono (SATA rev3.1), a opção de montagem de descarte** permitirá o descarte de blocos de arquivos liberados. Isso melhorará o desempenho do SSD.

Se o SSD não suportar TRIM enfileirado assíncrono, a opção de montagem de descarte prejudicará o desempenho do SSD. Nesse caso, a opção de montagem nodiscard deve ser usada.

Por padrão, a opção de montagem nodiscard é usada.

**11. norecovery

Se a opção de montagem norecovery** for usada, o sistema de arquivos Btrfs não tentará executar a operação de recuperação de dados no momento da montagem.

**12. usebackuproot e nousebackuproot

Se a opção de montagem usebackuproot for usada, o sistema de arquivos Btrfs tentará recuperar qualquer raiz de árvore ruim/corrompida no momento da montagem. O sistema de arquivos Btrfs pode armazenar várias raízes de árvore no sistema de arquivos. A opção de montagem usebackuproot** procurará uma boa raiz de árvore e usará a primeira boa que encontrar.

A opção de montagem nousebackuproot não verificará ou recuperará raízes de árvore inválidas/corrompidas no momento da montagem. Este é o comportamento padrão do sistema de arquivos Btrfs.

**13. space_cache, space_cache=version, nospace_cache e clear_cache

A opção de montagem space_cache** é usada para controlar o cache de espaço livre. O cache de espaço livre é usado para melhorar o desempenho da leitura do espaço livre do grupo de blocos do sistema de arquivos Btrfs na memória (RAM).

O sistema de arquivos Btrfs suporta 2 versões do cache de espaço livre: v1 (padrão) e v2

O mecanismo de cache de espaço livre v2 melhora o desempenho de sistemas de arquivos grandes (tamanho de vários terabytes).

Você pode usar a opção de montagem space_cache=v1 para definir a v1 do cache de espaço livre e a opção de montagem space_cache=v2 para definir a v2 do cache de espaço livre.

A opção de montagem clear_cache é usada para limpar o cache de espaço livre.

Quando o cache de espaço livre v2 é criado, o cache deve ser limpo para criar um cache de espaço livre v1 .

Portanto, para usar o cache de espaço livre v1 após a criação do cache de espaço livre v2 , as opções de montagem clear_cache e space_cache=v1 devem ser combinadas: clear_cache,space_cache=v1

A opção de montagem nospace_cache é usada para desabilitar o cache de espaço livre.

Para desabilitar o cache de espaço livre após a criação do cache v1 ou v2 , as opções de montagem nospace_cache e clear_cache devem ser combinadas: clear_cache,nosapce_cache

**14. skip_balance

Por padrão, a operação de balanceamento interrompida/pausada de um sistema de arquivos Btrfs de vários dispositivos ou RAID Btrfs será retomada automaticamente assim que o sistema de arquivos Btrfs for montado. Para desabilitar a retomada automática da operação de equilíbrio interrompido/pausado em um sistema de arquivos Btrfs de vários dispositivos ou RAID Btrfs, você pode usar a opção de montagem skip_balance .**

**15. datacow e nodatacow

A opção datacow** mount habilita o recurso Copy-on-Write (CoW) do sistema de arquivos Btrfs. É o comportamento padrão.

Se você deseja desabilitar o recurso Copy-on-Write (CoW) do sistema de arquivos Btrfs para os arquivos recém-criados, monte o sistema de arquivos Btrfs com a opção de montagem nodatacow .

**16. datasum e nodatasum

A opção datasum** mount habilita a soma de verificação de dados para arquivos recém-criados do sistema de arquivos Btrfs. Este é o comportamento padrão.

Se você não quiser que o sistema de arquivos Btrfs faça a soma de verificação dos dados dos arquivos recém-criados, monte o sistema de arquivos Btrfs com a opção de montagem nodatasum .

Perfis Btrfs

Um perfil Btrfs é usado para informar ao sistema de arquivos Btrfs quantas cópias dos dados/metadados devem ser mantidas e quais níveis de RAID devem ser usados para os dados/metadados. O sistema de arquivos Btrfs contém muitos perfis. Entendê-los o ajudará a configurar um RAID Btrfs da maneira que você deseja.

Os perfis Btrfs disponíveis são os seguintes:

single : Se o perfil único for usado para os dados/metadados, apenas uma cópia dos dados/metadados será armazenada no sistema de arquivos, mesmo se você adicionar vários dispositivos de armazenamento ao sistema de arquivos. Assim, 100% do espaço em disco de cada um dos dispositivos de armazenamento adicionados ao sistema de arquivos pode ser utilizado.

dup : Se o perfil dup for usado para os dados/metadados, cada um dos dispositivos de armazenamento adicionados ao sistema de arquivos manterá duas cópias dos dados/metadados. Assim, 50% do espaço em disco de cada um dos dispositivos de armazenamento adicionados ao sistema de arquivos pode ser utilizado.

raid0 : No perfil raid0 , os dados/metadados serão divididos igualmente em todos os dispositivos de armazenamento adicionados ao sistema de arquivos. Nesta configuração, não haverá dados/metadados redundantes (duplicados). Assim, 100% do espaço em disco de cada um dos dispositivos de armazenamento adicionados ao sistema de arquivos pode ser usado. Se, em qualquer caso, um dos dispositivos de armazenamento falhar, todo o sistema de arquivos será corrompido. Você precisará de pelo menos dois dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid0 .

raid1 : No perfil raid1 , duas cópias dos dados/metadados serão armazenadas nos dispositivos de armazenamento adicionados ao sistema de arquivos. Nesta configuração, a matriz RAID pode sobreviver a uma falha de unidade. Mas você pode usar apenas 50% do espaço total em disco. Você precisará de pelo menos dois dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid1 .

raid1c3 : No perfil raid1c3 , três cópias dos dados/metadados serão armazenadas nos dispositivos de armazenamento adicionados ao sistema de arquivos. Nesta configuração, a matriz RAID pode sobreviver a duas falhas de unidade, mas você pode usar apenas 33% do espaço total em disco. Você precisará de pelo menos três dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid1c3 .

raid1c4 : No perfil raid1c4 , quatro cópias dos dados/metadados serão armazenadas nos dispositivos de armazenamento adicionados ao sistema de arquivos. Nesta configuração, a matriz RAID pode sobreviver a três falhas de unidade, mas você pode usar apenas 25% do espaço total em disco. Você precisará de pelo menos quatro dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid1c4 .

raid10 : No perfil raid10 , duas cópias dos dados/metadados serão armazenadas nos dispositivos de armazenamento adicionados ao sistema de arquivos, como no perfil raid1 . Além disso, os dados/metadados serão divididos entre os dispositivos de armazenamento, como no perfil raid0 .

O perfil raid10 é um híbrido dos perfis raid1 e raid0 . Alguns dos dispositivos de armazenamento formam arrays raid1 e alguns desses arrays raid1 são usados para formar um array raid0 . Em uma configuração raid10 , o sistema de arquivos pode sobreviver a uma única falha de unidade em cada uma das matrizes raid1 .

Você pode usar 50% do espaço total em disco na configuração raid10 . Você precisará de pelo menos quatro dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid10 .

raid5 : No perfil raid5 , uma cópia dos dados/metadados será dividida entre os dispositivos de armazenamento. Uma única paridade será calculada e distribuída entre os dispositivos de armazenamento do array RAID.

Em uma configuração raid5 , o sistema de arquivos pode sobreviver a uma única falha de unidade. Se uma unidade falhar, você pode adicionar uma nova unidade ao sistema de arquivos e os dados perdidos serão calculados a partir da paridade distribuída das unidades em execução.

Você pode usar 1 00x(N-1)/N % do total de espaços em disco na configuração raid5 . Aqui, N é o número de dispositivos de armazenamento adicionados ao sistema de arquivos. Você precisará de pelo menos três dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid5 .

raid6 : No perfil raid6 , uma cópia dos dados/metadados será dividida entre os dispositivos de armazenamento. Duas paridades serão calculadas e distribuídas entre os dispositivos de armazenamento do array RAID.

Em uma configuração raid6 , o sistema de arquivos pode sobreviver a duas falhas de unidade ao mesmo tempo. Se uma unidade falhar, você poderá adicionar uma nova unidade ao sistema de arquivos e os dados perdidos serão calculados a partir das duas paridades distribuídas das unidades em execução.

Você pode usar 100x(N-2)/N % do espaço total em disco na configuração raid6 . Aqui, N é o número de dispositivos de armazenamento adicionados ao sistema de arquivos. Você precisará de pelo menos quatro dispositivos de armazenamento para configurar o sistema de arquivos Btrfs no perfil raid6 .