Initial project structure: documentation, server concept, agents instructions

2026-09-24 12:20:27 +02:00
commit c24472dfd3
11 changed files with 1358 additions and 0 deletions
@@ -0,0 +1,18 @@
 # Rust
 target/
 **/*.rs.bk
 # Node / frontend
 node_modules/
 dist/
 # Local config & secrets
 .env
 .env.*
 *.local.toml
 config/*.toml
 # Logs & OS
 *.log
 .DS_Store
 Thumbs.db
@@ -0,0 +1,54 @@
 # AGENTS.md — Anarcho-Kommunistisches Internet
 > Arbeitsanweisungen und Ziele für Coding-Agents und Contributor:innen.
 > Lies diese Datei zuerst, bevor du etwas am Projekt änderst.
 ## Vision
 Ein Nachbarschaftsnetz: Häuser werden per Glasfaser (oder notfalls Funk)
 direkt miteinander verbunden. Die Bandbreite aller Internetanschlüsse wird
 gepoolt, sodass jeder Haushalt vom gesamten Netz profitiert — schwache
 Anschlüsse werden stärker, niemand zahlt mehr, und ausgehender Traffic wird
 auf viele Hausanschlüsse verteilt, was Backtracking für außenstehende
 erschwert (Privacy als Nebenprodukt, nicht als Produktpromise).
 Das Projekt besteht aus zwei Hälften:
 1. `documentation/` — Idee, Ethos, Architektur, Rechtslage, Roadmap
 2. `server/` — die Software ("Node"), die das technisch möglich macht
 ## Konventionen
 - Sprache: Dokumentation auf Deutsch, Code/Kommentare/Commit-Messages auf Englisch
 - Markdown für Doku, keine Binärdateien ins Repo
 - Code-Lizenz: AGPL-3.0 (passt zum Ethos; `freenet-core` ist ebenfalls AGPL-3.0)
 - Keine Secrets ins Repo (Passwörter, Token, private IP-Listen realer Nachbarn)
 - Persönliche Daten von Nachbarn (Namen, Adressen) bleiben außerhalb des Repos
 ## Server (geplant)
 - Sprache: Rust
 - Dezentraler Kern: [Freenet 2023](https://freenet.org/) (`freenet-core`,
  AGPL-3.0, <https://github.com/freenet/freenet-core>) für verteilte Inhalte
  und Apps. Wichtig: Freenet bietet **keine Anonymität** (klar im
  [FAQ](https://freenet.org/about/faq/) benannt) — nicht damit werben.
 - Kernfeatures: Multi-Exit-Bandbreiten-Pooling, segmentierte Downloads,
  Fairness-Scheduler, Nachbarschafts-Cache
 - Status: Konzeptphase, Details in `server/README.md`
 ## Git / Gitea
 - Remote: `https://git.dieterunterstrich.de/<user>/anarcho-kommunistisches-internet.git`
 - Branch: `main`
 - Credentials liegen im credential-helper `store` — niemals ausgeben oder committen
 - Repo-Setup: `scripts/bootstrap-gitea.sh` (erzeugt das Repo via Gitea-API und pusht)
 - **WICHTIG:** Nur dieses eine Repo anfassen. Keine anderen Repos auf dem
  Gitea-Server verändern, löschen, forken oder beschreiben.
 ## Arbeitsregeln für Agents
 - Erst Doku lesen (v. a. `documentation/ideen/architektur.md` und
  `documentation/ideen/recht.md`), dann ändern
 - Kleine, beschreibbare Commits; keine offen gelassenen TODOs in `main`
 - Keine rechtlich heiklen Features einbauen, ohne dass sie in `recht.md` bedacht sind
 - Recherche-Ergebnisse gehören in die Doku (mit Quellen), nicht nur in den Chat
@@ -0,0 +1,661 @@
                    GNU AFFERO GENERAL PUBLIC LICENSE
                       Version 3, 19 November 2007
 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.
                            Preamble
  The GNU Affero General Public License is a free, copyleft license for
 software and other kinds of works, specifically designed to ensure
 cooperation with the community in the case of network server software.
  The licenses for most software and other practical works are designed
 to take away your freedom to share and change the works.  By contrast,
 our General Public Licenses are intended to guarantee your freedom to
 share and change all versions of a program--to make sure it remains free
 software for all its users.
  When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
 have the freedom to distribute copies of free software (and charge for
 them if you wish), that you receive source code or can get it if you
 want it, that you can change the software or use pieces of it in new
 free programs, and that you know you can do these things.
  Developers that use our General Public Licenses protect your rights
 with two steps: (1) assert copyright on the software, and (2) offer
 you this License which gives you legal permission to copy, distribute
 and/or modify the software.
  A secondary benefit of defending all users' freedom is that
 improvements made in alternate versions of the program, if they
 receive widespread use, become available for other developers to
 incorporate.  Many developers of free software are heartened and
 encouraged by the resulting cooperation.  However, in the case of
 software used on network servers, this result may fail to come about.
 The GNU General Public License permits making a modified version and
 letting the public access it on a server without ever releasing its
 source code to the public.
  The GNU Affero General Public License is designed specifically to
 ensure that, in such cases, the modified source code becomes available
 to the community.  It requires the operator of a network server to
 provide the source code of the modified version running there to the
 users of that server.  Therefore, public use of a modified version, on
 a publicly accessible server, gives the public access to the source
 code of the modified version.
  An older license, called the Affero General Public License and
 published by Affero, was designed to accomplish similar goals.  This is
 a different license, not a version of the Affero GPL, but Affero has
 released a new version of the Affero GPL which permits relicensing under
 this license.
  The precise terms and conditions for copying, distribution and
 modification follow.
                       TERMS AND CONDITIONS
  0. Definitions.
  "This License" refers to version 3 of the GNU Affero General Public License.
  "Copyright" also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
  "The Program" refers to any copyrightable work licensed under this
 License.  Each licensee is addressed as "you".  "Licensees" and
 "recipients" may be individuals or organizations.
  To "modify" a work means to copy from or adapt all or part of the work
 in a fashion requiring copyright permission, other than the making of an
 exact copy.  The resulting work is called a "modified version" of the
 earlier work or a work "based on" the earlier work.
  A "covered work" means either the unmodified Program or a work based
 on the Program.
  To "propagate" a work means to do anything with it that, without
 permission, would make you directly or secondarily liable for
 infringement under applicable copyright law, except executing it on a
 computer or modifying a private copy.  Propagation includes copying,
 distribution (with or without modification), making available to the
 public, and in some countries other activities as well.
  To "convey" a work means any kind of propagation that enables other
 parties to make or receive copies.  Mere interaction with a user through
 a computer network, with no transfer of a copy, is not conveying.
  An interactive user interface displays "Appropriate Legal Notices"
 to the extent that it includes a convenient and prominently visible
 feature that (1) displays an appropriate copyright notice, and (2)
 tells the user that there is no warranty for the work (except to the
 extent that warranties are provided), that licensees may convey the
 work under this License, and how to view a copy of this License.  If
 the interface presents a list of user commands or options, such as a
 menu, a prominent item in the list meets this criterion.
  1. Source Code.
  The "source code" for a work means the preferred form of the work
 for making modifications to it.  "Object code" means any non-source
 form of a work.
  A "Standard Interface" means an interface that either is an official
 standard defined by a recognized standards body, or, in the case of
 interfaces specified for a particular programming language, one that
 is widely used among developers working in that language.
  The "System Libraries" of an executable work include anything, other
 than the work as a whole, that (a) is included in the normal form of
 packaging a Major Component, but which is not part of that Major
 Component, and (b) serves only to enable use of the work with that
 Major Component, or to implement a Standard Interface for which an
 implementation is available to the public in source code form.  A
 "Major Component", in this context, means a major essential component
 (kernel, window system, and so on) of the specific operating system
 (if any) on which the executable work runs, or a compiler used to
 produce the work, or an object code interpreter used to run it.
  The "Corresponding Source" for a work in object code form means all
 the source code needed to generate, install, and (for an executable
 work) run the object code and to modify the work, including scripts to
 control those activities.  However, it does not include the work's
 System Libraries, or general-purpose tools or generally available free
 programs which are used unmodified in performing those activities but
 which are not part of the work.  For example, Corresponding Source
 includes interface definition files associated with source files for
 the work, and the source code for shared libraries and dynamically
 linked subprograms that the work is specifically designed to require,
 such as by intimate data communication or control flow between those
 subprograms and other parts of the work.
  The Corresponding Source need not include anything that users
 can regenerate automatically from other parts of the Corresponding
 Source.
  The Corresponding Source for a work in source code form is that
 same work.
  2. Basic Permissions.
  All rights granted under this License are granted for the term of
 copyright on the Program, and are irrevocable provided the stated
 conditions are met.  This License explicitly affirms your unlimited
 permission to run the unmodified Program.  The output from running a
 covered work is covered by this License only if the output, given its
 content, constitutes a covered work.  This License acknowledges your
 rights of fair use or other equivalent, as provided by copyright law.
  You may make, run and propagate covered works that you do not
 convey, without conditions so long as your license otherwise remains
 in force.  You may convey covered works to others for the sole purpose
 of having them make modifications exclusively for you, or provide you
 with facilities for running those works, provided that you comply with
 the terms of this License in conveying all material for which you do
 not control copyright.  Those thus making or running the covered works
 for you must do so exclusively on your behalf, under your direction
 and control, on terms that prohibit them from making any copies of
 your copyrighted material outside their relationship with you.
  Conveying under any other circumstances is permitted solely under
 the conditions stated below.  Sublicensing is not allowed; section 10
 makes it unnecessary.
  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
  No covered work shall be deemed part of an effective technological
 measure under any applicable law fulfilling obligations under article
 11 of the WIPO copyright treaty adopted on 20 December 1996, or
 similar laws prohibiting or restricting circumvention of such
 measures.
  When you convey a covered work, you waive any legal power to forbid
 circumvention of technological measures to the extent such circumvention
 is effected by exercising rights under this License with respect to
 the covered work, and you disclaim any intention to limit operation or
 modification of the work as a means of enforcing, against the work's
 users, your or third parties' legal rights to forbid circumvention of
 technological measures.
  4. Conveying Verbatim Copies.
  You may convey verbatim copies of the Program's source code as you
 receive it, in any medium, provided that you conspicuously and
 appropriately publish on each copy an appropriate copyright notice;
 keep intact all notices stating that this License and any
 non-permissive terms added in accord with section 7 apply to the code;
 keep intact all notices of the absence of any warranty; and give all
 recipients a copy of this License along with the Program.
  You may charge any price or no price for each copy that you convey,
 and you may offer support or warranty protection for a fee.
  5. Conveying Modified Source Versions.
  You may convey a work based on the Program, or the modifications to
 produce it from the Program, in the form of source code under the
 terms of section 4, provided that you also meet all of these conditions:
    a) The work must carry prominent notices stating that you modified
    it, and giving a relevant date.
    b) The work must carry prominent notices stating that it is
    released under this License and any conditions added under section
    7.  This requirement modifies the requirement in section 4 to
    "keep intact all notices".
    c) You must license the entire work, as a whole, under this
    License to anyone who comes into possession of a copy.  This
    License will therefore apply, along with any applicable section 7
    additional terms, to the whole of the work, and all its parts,
    regardless of how they are packaged.  This License gives no
    permission to license the work in any other way, but it does not
    invalidate such permission if you have separately received it.
    d) If the work has interactive user interfaces, each must display
    Appropriate Legal Notices; however, if the Program has interactive
    interfaces that do not display Appropriate Legal Notices, your
    work need not make them do so.
  A compilation of a covered work with other separate and independent
 works, which are not by their nature extensions of the covered work,
 and which are not combined with it such as to form a larger program,
 in or on a volume of a storage or distribution medium, is called an
 "aggregate" if the compilation and its resulting copyright are not
 used to limit the access or legal rights of the compilation's users
 beyond what the individual works permit.  Inclusion of a covered work
 in an aggregate does not cause this License to apply to the other
 parts of the aggregate.
  6. Conveying Non-Source Forms.
  You may convey a covered work in object code form under the terms
 of sections 4 and 5, provided that you also convey the
 machine-readable Corresponding Source under the terms of this License,
 in one of these ways:
    a) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by the
    Corresponding Source fixed on a durable physical medium
    customarily used for software interchange.
    b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a
    copy of the Corresponding Source for all the software in the
    product that is covered by this License, on a durable physical
    medium customarily used for software interchange, for a price no
    more than your reasonable cost of physically performing this
    conveying of source, or (2) access to copy the
    Corresponding Source from a network server at no charge.
    c) Convey individual copies of the object code with a copy of the
    written offer to provide the Corresponding Source.  This
    alternative is allowed only occasionally and noncommercially, and
    only if you received the object code with such an offer, in accord
    with subsection 6b.
    d) Convey the object code by offering access from a designated
    place (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge.  You need not require recipients to copy the
    Corresponding Source along with the object code.  If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source.  Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.
    e) Convey the object code using peer-to-peer transmission, provided
    you inform other peers where the object code and Corresponding
    Source of the work are being offered to the general public at no
    charge under subsection 6d.
  A separable portion of the object code, whose source code is excluded
 from the Corresponding Source as a System Library, need not be
 included in conveying the object code work.
  A "User Product" is either (1) a "consumer product", which means any
 tangible personal property which is normally used for personal, family,
 or household purposes, or (2) anything designed or sold for incorporation
 into a dwelling.  In determining whether a product is a consumer product,
 doubtful cases shall be resolved in favor of coverage.  For a particular
 product received by a particular user, "normally used" refers to a
 typical or common use of that class of product, regardless of the status
 of the particular user or of the way in which the particular user
 actually uses, or expects or is expected to use, the product.  A product
 is a consumer product regardless of whether the product has substantial
 commercial, industrial or non-consumer uses, unless such uses represent
 the only significant mode of use of the product.
  "Installation Information" for a User Product means any methods,
 procedures, authorization keys, or other information required to install
 and execute modified versions of a covered work in that User Product from
 a modified version of its Corresponding Source.  The information must
 suffice to ensure that the continued functioning of the modified object
 code is in no case prevented or interfered with solely because
 modification has been made.
  If you convey an object code work under this section in, or with, or
 specifically for use in, a User Product, and the conveying occurs as
 part of a transaction in which the right of possession and use of the
 User Product is transferred to the recipient in perpetuity or for a
 fixed term (regardless of how the transaction is characterized), the
 Corresponding Source conveyed under this section must be accompanied
 by the Installation Information.  But this requirement does not apply
 if neither you nor any third party retains the ability to install
 modified object code on the User Product (for example, the work has
 been installed in ROM).
  The requirement to provide Installation Information does not include a
 requirement to continue to provide support service, warranty, or updates
 for a work that has been modified or installed by the recipient, or for
 the User Product in which it has been modified or installed.  Access to a
 network may be denied when the modification itself materially and
 adversely affects the operation of the network or violates the rules and
 protocols for communication across the network.
  Corresponding Source conveyed, and Installation Information provided,
 in accord with this section must be in a format that is publicly
 documented (and with an implementation available to the public in
 source code form), and must require no special password or key for
 unpacking, reading or copying.
  7. Additional Terms.
  "Additional permissions" are terms that supplement the terms of this
 License by making exceptions from one or more of its conditions.
 Additional permissions that are applicable to the entire Program shall
 be treated as though they were included in this License, to the extent
 that they are valid under applicable law.  If additional permissions
 apply only to part of the Program, that part may be used separately
 under those permissions, but the entire Program remains governed by
 this License without regard to the additional permissions.
  When you convey a copy of a covered work, you may at your option
 remove any additional permissions from that copy, or from any part of
 it.  (Additional permissions may be written to require their own
 removal in certain cases when you modify the work.)  You may place
 additional permissions on material, added by you to a covered work,
 for which you have or can give appropriate copyright permission.
  Notwithstanding any other provision of this License, for material you
 add to a covered work, you may (if authorized by the copyright holders of
 that material) supplement the terms of this License with terms:
    a) Disclaiming warranty or limiting liability differently from the
    terms of sections 15 and 16 of this License; or
    b) Requiring preservation of specified reasonable legal notices or
    author attributions in that material or in the Appropriate Legal
    Notices displayed by works containing it; or
    c) Prohibiting misrepresentation of the origin of that material, or
    requiring that modified versions of such material be marked in
    reasonable ways as different from the original version; or
    d) Limiting the use for publicity purposes of names of licensors or
    authors of the material; or
    e) Declining to grant rights under trademark law for use of some
    trade names, trademarks, or service marks; or
    f) Requiring indemnification of licensors and authors of that
    material by anyone who conveys the material (or modified versions of
    it) with contractual assumptions of liability to the recipient, for
    any liability that these contractual assumptions directly impose on
    those licensors and authors.
  All other non-permissive additional terms are considered "further
 restrictions" within the meaning of section 10.  If the Program as you
 received it, or any part of it, contains a notice stating that it is
 governed by this License along with a term that is a further
 restriction, you may remove that term.  If a license document contains
 a further restriction but permits relicensing or conveying under this
 License, you may add to a covered work material governed by the terms
 of that license document, provided that the further restriction does
 not survive such relicensing or conveying.
  If you add terms to a covered work in accord with this section, you
 must place, in the relevant source files, a statement of the
 additional terms that apply to those files, or a notice indicating
 where to find the applicable terms.
  Additional terms, permissive or non-permissive, may be stated in the
 form of a separately written license, or stated as exceptions;
 the above requirements apply either way.
  8. Termination.
  You may not propagate or modify a covered work except as expressly
 provided under this License.  Any attempt otherwise to propagate or
 modify it is void, and will automatically terminate your rights under
 this License (including any patent licenses granted under the third
 paragraph of section 11).
  However, if you cease all violation of this License, then your
 license from a particular copyright holder is reinstated (a)
 provisionally, unless and until the copyright holder explicitly and
 finally terminates your license, and (b) permanently, if the copyright
 holder fails to notify you of the violation by some reasonable means
 prior to 60 days after the cessation.
  Moreover, your license from a particular copyright holder is
 reinstated permanently if the copyright holder notifies you of the
 violation by some reasonable means, this is the first time you have
 received notice of violation of this License (for any work) from that
 copyright holder, and you cure the violation prior to 30 days after
 your receipt of the notice.
  Termination of your rights under this section does not terminate the
 licenses of parties who have received copies or rights from you under
 this License.  If your rights have been terminated and not permanently
 reinstated, you do not qualify to receive new licenses for the same
 material under section 10.
  9. Acceptance Not Required for Having Copies.
  You are not required to accept this License in order to receive or
 run a copy of the Program.  Ancillary propagation of a covered work
 occurring solely as a consequence of using peer-to-peer transmission
 to receive a copy likewise does not require acceptance.  However,
 nothing other than this License grants you permission to propagate or
 modify any covered work.  These actions infringe copyright if you do
 not accept this License.  Therefore, by modifying or propagating a
 covered work, you indicate your acceptance of this License to do so.
  10. Automatic Licensing of Downstream Recipients.
  Each time you convey a covered work, the recipient automatically
 receives a license from the original licensors, to run, modify and
 propagate that work, subject to this License.  You are not responsible
 for enforcing compliance by third parties with this License.
  An "entity transaction" is a transaction transferring control of an
 organization, or substantially all assets of one, or subdividing an
 organization, or merging organizations.  If propagation of a covered
 work results from an entity transaction, each party to that
 transaction who receives a copy of the work also receives whatever
 licenses to the work the party's predecessor in interest had or could
 give under the previous paragraph, plus a right to possession of the
 Corresponding Source of the work from the predecessor in interest, if
 the predecessor has it or can get it with reasonable efforts.
  You may not impose any further restrictions on the exercise of the
 rights granted or affirmed under this License.  For example, you may
 not impose a license fee, royalty, or other charge for exercise of
 rights granted under this License, and you may not initiate litigation
 (including a cross-claim or counterclaim in a lawsuit) alleging that
 any patent claim is infringed by making, using, selling, offering for
 sale, or importing the Program or any portion of it.
  11. Patents.
  A "contributor" is a copyright holder who authorizes use under this
 License of the Program or a work on which the Program is based.  The
 work thus licensed is called the contributor's "contributor version".
  A contributor's "essential patent claims" are all patent claims
 owned or controlled by the contributor, whether already acquired or
 hereafter acquired, that would be infringed by some manner, permitted
 by this License, of making, using, or selling its contributor version,
 but do not include claims that would be infringed only as a
 consequence of further modification of the contributor version.  For
 purposes of this definition, "control" includes the right to grant
 patent sublicenses in a manner consistent with the requirements of
 this License.
  Each contributor grants you a non-exclusive, worldwide, royalty-free
 patent license under the contributor's essential patent claims, to
 make, use, sell, offer for sale, import and otherwise run, modify and
 propagate the contents of its contributor version.
  In the following three paragraphs, a "patent license" is any express
 agreement or commitment, however denominated, not to enforce a patent
 (such as an express permission to practice a patent or covenant not to
 sue for patent infringement).  To "grant" such a patent license to a
 party means to make such an agreement or commitment not to enforce a
 patent against the party.
  If you convey a covered work, knowingly relying on a patent license,
 and the Corresponding Source of the work is not available for anyone
 to copy, free of charge and under the terms of this License, through a
 publicly available network server or other readily accessible means,
 then you must either (1) cause the Corresponding Source to be so
 available, or (2) arrange to deprive yourself of the benefit of the
 patent license for this particular work, or (3) arrange, in a manner
 consistent with the requirements of this License, to extend the patent
 license to downstream recipients.  "Knowingly relying" means you have
 actual knowledge that, but for the patent license, your conveying the
 covered work in a country, or your recipient's use of the covered work
 in a country, would infringe one or more identifiable patents in that
 country that you have reason to believe are valid.
  If, pursuant to or in connection with a single transaction or
 arrangement, you convey, or propagate by procuring conveyance of, a
 covered work, and grant a patent license to some of the parties
 receiving the covered work authorizing them to use, propagate, modify
 or convey a specific copy of the covered work, then the patent license
 you grant is automatically extended to all recipients of the covered
 work and works based on it.
  A patent license is "discriminatory" if it does not include within
 the scope of its coverage, prohibits the exercise of, or is
 conditioned on the non-exercise of one or more of the rights that are
 specifically granted under this License.  You may not convey a covered
 work if you are a party to an arrangement with a third party that is
 in the business of distributing software, under which you make payment
 to the third party based on the extent of your activity of conveying
 the work, and under which the third party grants, to any of the
 parties who would receive the covered work from you, a discriminatory
 patent license (a) in connection with copies of the covered work
 conveyed by you (or copies made from those copies), or (b) primarily
 for and in connection with specific products or compilations that
 contain the covered work, unless you entered into that arrangement,
 or that patent license was granted, prior to 28 March 2007.
  Nothing in this License shall be construed as excluding or limiting
 any implied license or other defenses to infringement that may
 otherwise be available to you under applicable patent law.
  12. No Surrender of Others' Freedom.
  If conditions are imposed on you (whether by court order, agreement or
 otherwise) that contradict the conditions of this License, they do not
 excuse you from the conditions of this License.  If you cannot convey a
 covered work so as to satisfy simultaneously your obligations under this
 License and any other pertinent obligations, then as a consequence you may
 not convey it at all.  For example, if you agree to terms that obligate you
 to collect a royalty for further conveying from those to whom you convey
 the Program, the only way you could satisfy both those terms and this
 License would be to refrain entirely from conveying the Program.
  13. Remote Network Interaction; Use with the GNU General Public License.
  Notwithstanding any other provision of this License, if you modify the
 Program, your modified version must prominently offer all users
 interacting with it remotely through a computer network (if your version
 supports such interaction) an opportunity to receive the Corresponding
 Source of your version by providing access to the Corresponding Source
 from a network server at no charge, through some standard or customary
 means of facilitating copying of software.  This Corresponding Source
 shall include the Corresponding Source for any work covered by version 3
 of the GNU General Public License that is incorporated pursuant to the
 following paragraph.
  Notwithstanding any other provision of this License, you have
 permission to link or combine any covered work with a work licensed
 under version 3 of the GNU General Public License into a single
 combined work, and to convey the resulting work.  The terms of this
 License will continue to apply to the part which is the covered work,
 but the work with which it is combined will remain governed by version
 3 of the GNU General Public License.
  14. Revised Versions of this License.
  The Free Software Foundation may publish revised and/or new versions of
 the GNU Affero General Public License from time to time.  Such new versions
 will be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
  Each version is given a distinguishing version number.  If the
 Program specifies that a certain numbered version of the GNU Affero General
 Public License "or any later version" applies to it, you have the
 option of following the terms and conditions either of that numbered
 version or of any later version published by the Free Software
 Foundation.  If the Program does not specify a version number of the
 GNU Affero General Public License, you may choose any version ever published
 by the Free Software Foundation.
  If the Program specifies that a proxy can decide which future
 versions of the GNU Affero General Public License can be used, that proxy's
 public statement of acceptance of a version permanently authorizes you
 to choose that version for the Program.
  Later license versions may give you additional or different
 permissions.  However, no additional obligations are imposed on any
 author or copyright holder as a result of your choosing to follow a
 later version.
  15. Disclaimer of Warranty.
  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
 APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
 HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
 OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
 THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
 IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
 ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
  16. Limitation of Liability.
  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
 THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
 GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
 USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
 DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
 PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
 EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
 SUCH DAMAGES.
  17. Interpretation of Sections 15 and 16.
  If the disclaimer of warranty and limitation of liability provided
 above cannot be given local legal effect according to their terms,
 reviewing courts shall apply local law that most closely approximates
 an absolute waiver of all civil liability in connection with the
 Program, unless a warranty or assumption of liability accompanies a
 copy of the Program in return for a fee.
                     END OF TERMS AND CONDITIONS
            How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
 possible use to the public, the best way to achieve this is to make it
 free software which everyone can redistribute and change under these terms.
  To do so, attach the following notices to the program.  It is safest
 to attach them to the start of each source file to most effectively
 state the exclusion of warranty; and each file should have at least
 the "copyright" line and a pointer to where the full notice is found.
    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>
    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU Affero General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.
    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Affero General Public License for more details.
    You should have received a copy of the GNU Affero General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.
 Also add information on how to contact you by electronic and paper mail.
  If your software can interact with users remotely through a computer
 network, you should also make sure that it provides a way for users to
 get its source.  For example, if your program is a web application, its
 interface could display a "Source" link that leads users to an archive
 of the code.  There are many ways you could offer source, and different
 solutions will be better for different programs; see section 13 for the
 specific requirements.
  You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU AGPL, see
 <https://www.gnu.org/licenses/>.
@@ -0,0 +1,36 @@
 # Dokumentation — Anarcho-Kommunistisches Internet
 Ein Nachbarschaftsnetz aus Glasfaser, in dem sich alle Haushalte ihre
 Internetbandbreite teilen: **vom Internetanschluss zum Gemeingut.**
 ## Inhaltsverzeichnis
 | Datei | Inhalt |
 |---|---|
 | [ethos.md](ethos.md) | Werte, Prinzipien und "Hausregeln" des Netzes |
 | [ideen/idee.md](ideen/idee.md) | Die Kernidee und ein ehrlicher Realitätscheck |
 | [ideen/architektur.md](ideen/architektur.md) | Technische Architektur (Physik → Routing → Pooling → Inhalt) |
 | [ideen/recht.md](ideen/recht.md) | Rechtslage in Deutschland (Störerhaftung, Abmahnrisiko, Verkabelung) |
 | [ideen/roadmap.md](ideen/roadmap.md) | Phasenplan vom Pilot bis zum Nachbarschafts-Backbone |
 ## Die Idee in einem Satz
 Häuser werden direkt per Glasfaser verbunden; jede Anfrage ins Internet kann
 über **alle** Anschlüsse des Viertels gleichzeitig laufen (segmentiert und
 fair gemesht), sodass die effektive Bandbreite ~ der Summe aller Anschlüsse
 ist — ohne Mehrkosten und mit besserer Versorgung schwacher Haushalte.
 ## Status
 Konzeptphase. Die Software in `server/` ist noch nicht implementiert; der
 erste Meilenstein ist ein PoC "segmentierter Download über zwei Haushalte"
 (siehe [Roadmap](ideen/roadmap.md)).
 ## Verwandte Projekte (Prior Art)
 - [Freifunk](https://freifunk.net/) — deutschlandweite Community-Netz-Initiative
 - [NYC Mesh](https://www.nycmesh.net/) — Mitglieder teilen ihre Anschlüsse, Supernodes + Peering
 - [guifi.net](https://www.guifi.net/) — Spanien, Community-Fiber in großem Maßstab
 - [Althea](https://www.althea.net/) — Mesh mit Bezahl-Protokoll (Kontrast: wir sind bewusst kostenlos/fair-share)
 - [Yggdrasil](https://yggdrasilnetwork.org/) — Overlay-Routing-Kandidat für unsere Ebene 2
 - [lancache](https://lancache.net/) — Nachbarschafts-Cache-Prinzip für große Downloads
@@ -0,0 +1,74 @@
 # Ethos
 Was dieses Netz ist und wie es sich verhält. Diese Werte gelten für Technik
 genauso wie für den Umgang miteinander.
 ## 1. Gemeingut statt Markt
 Die Infrastruktur (Glasfaser, Router, Uplinks) gehört den Teilnehmenden
 gemeinsam und wird geteilt, nicht verkauft. Bandbreite ist ein **Commons**:
 Niemand erwirbt mehr Rechte, indem er mehr bezahlt oder mehr Hardware hat.
 Anders als z. B. [Althea](https://www.althea.net/) (Mikrozahlungen pro
 weitergeleitetem Paket) wollen wir bewusst **keine Bezahlung** im Kern —
 der Fairness-Scheduler (siehe Architektur) ist unsere Währung.
 ## 2. Fairness als Algorithmus, nicht als Gnade
 Jeder Haushalt bekommt standardmäßig einen gleichberechtigten, fairen Anteil
 (max-min Fairness). Stärkere Anschlüsse teilen freiwillig — genau das ist der
 "anarcho-kommunistische" Kern: voneinander abhängig, freiwillig, ohne Zwang
 und ohne Markt. Dauernutzung ohne Gegenleistung wird fair gedealt (Gespräch,
 Karma, Drosselung als letztes Mittel) — nicht bestraft.
 ## 3. Freiwilligkeit und Do-ocracy
 Teilnahme ist freiwillig, Austritt jederzeit möglich. Entscheidungen trifft,
 wer Arbeit leistet (Do-ocracy), abgestimmt im offenen Gespräch. Niemand kann
 gezwungen werden, als Exit für andere zu dienen — Exit-Bereitschaft ist eine
 **explizite, jederzeit widerrufliche Zustimmung pro Haushalt**.
 ## 4. Privacy als Grundrecht, Anonymität als Nirgendwo-Garantie
 - Der eigene Traffic läuft so weit wie möglich nicht über die eigene Leitung:
  Verteilung über viele Hausanschlüsse macht Zuordnung für ISPs und Dritte
  deutlich schwerer. Das ist ein echter Sicherheitsgewinn für alle.
 - Aber wir versprechen **keine Anonymität**: Freenet selbst sagt klar, dass
  es keine Anonymität wie Tor/I2P bietet. Metadaten, TLS-Verkehr und Exit-
  Knoten bleiben sichtbar. Wer echte Anonymität braucht, legt zusätzlich
  Tor/I2P über das Netz.
 - Nodes loggen minimal. Keine Nutzungsprofile, keine Werbepreise.
 ## 5. Legaler Betrieb als Überlebensbedingung
 Ein Netz, dessen öffentliches Gesicht "Piraterie" ist, wird abgemahnt,
 zerlegt und diskreditiert — und zieht Risiko auf die schwächsten Teilnehmer
 (siehe [recht.md](ideen/recht.md)). Deshalb:
 - Das Netz wird als Infrastrukturprojekt betrieben (Zugang, Resilienz,
  Gemeingut), nicht als Tauschbörsen-Produkt.
 - Jede:r bleibt für das eigene Tun verantwortlich; das Netz dokumentiert,
  dass viele Menschen Zugang haben (schützt den Anschlussinhaber).
 - Technisch kühles Denken ja, "Es ist legal, weil verteilt" — nein.
 ## 6. Transparenz und offene Technik
 Alles ist offen: Code (AGPL-3.0), Doku, Pläne, auch die Fehler. Hardware
 besteht möglichst aus Standardkomponenten (Mini-PC, SFP-Medienwandler,
 Standard-Glasfaser), die alle reparieren und beschaffen können.
 ## 7. Resilienz und Selbsthilfe
 Das Netz soll funktionieren, wenn das Internet gerade nicht funktioniert:
 lokale Dienste, lokale Caches, lokale Kommunikation (siehe NYC Mesh).
 Jede:r im Haus kann Teilnahme, Installation und Betrieb lernen — Wissen wird
 geteilt wie Bandbreite.
 ## Die "Pico Peering" Hausregel
 Basierend auf dem [Pico Peering Agreement](https://picopeer.net/) halten wir
 fest: **Wer mitmacht, teilt. Wer teilt, wird geteilt.** Konkret:
 1. Ich verbinde mein Haus mit dem Netz und lasse Traffic durch.
 2. Ich benutze das Netz fair (Fair-Share).
 3. Ich stelle nichts Unlawfuls bereit und verantwortet mein eigenes Handeln.
 4. Konflikte werden im Viertel geklärt, nicht beim Anwalt.
@@ -0,0 +1,140 @@
 # Architektur
 Von unten (Physik) nach oben (Inhalte). Der AKI-Node ist das Herzstück —
 eine kleine Box im Wohnungsregal, die zu Hause sitzt und das Viertel verbindet.
 ## Übersicht
 ```mermaid
 flowchart TD
    subgraph HausA[Haus A]
        GA[Geräte A] --> NA[AKI-Node A]
    end
    subgraph HausB[Haus B]
        GB[Geräte B] --> NB[AKI-Node B]
    end
    subgraph HausC[Haus C]
        GC[Geräte C] --> NC[AKI-Node C]
    end
    NA <-->|"Glasfaser (bzw. Funk-Fallback)"| NB
    NB <-->|"Glasfaser"| NC
    NA -->|"ISP-Uplink A"| WA((Internet))
    NB -->|"ISP-Uplink B"| WA
    NC -->|"ISP-Uplink C"| WA
 ```
 Entscheidend: **jeder Haushalt behält seinen eigenen Uplink**. Es gibt keinen
 zentralen Exit (anders als klassische Community-Meshes mit einem Supernode),
 sondern viele — das verteilt nicht nur Last, sondern auch Risiko und Zensur-
 Angriffsfläche.
 ## Schicht 0 — Physik (Nachbarschaftsglasfaser)
 - **Bevorzugt:** Glasfaser Haus-zu-Haus (z. B. 2-Faser-Duplex G.657A2, LC-
  Stecker), Medienwandler bzw. SFP-Port direkt im Node. Innenrohr entlang
  der Fassade, kurze Gräben im Garten, Kabelkanal.
 - **Pragmatisch für den Start:** was da ist — existierendes LAN-Kabel im
  Mehrfamilienhaus (bis 100 m), Richtfunk 60-GHz-PTP (5–15 Gbit/s,
  Sichtlinie nötig) als Überbrückung.
 - **Topologie:** anfangs Stern/Ring (2–5 Häuser), später vermascht. Jede
  Faser ist ein separates Link; Redundanz schlägt Eleganz.
 ## Schicht 1 — Routing (Overlay über alle Haushalte)
 Kandidaten (Auswahl offen, Kriterium: simpel, wartbar, verschlüsselt):
 | Kandidat | Pro | Con |
 |---|---|---|
 | **Yggdrasil** | Out-of-the-box e2e-verschlüsseltes IPv6-Overlay, null Konfiguration, self-contained | experimentell, Performance über wenige Gbit/s hinaus |
 | Babel + WireGuard | bewährt (Althea-Ansatz), Router-Hardware tauglich | mehr Konfigurationsaufwand |
 | cjdns | Battle-tested in Hyperboria | ältere Codebasis |
 Empfehlung für den PoC: **Yggdrasil**. Jeder AKI-Node peert über die
 Glasfaser-Links mit seinen Nachbarn; Geräte der Haushalte hängen per NAT/
 Firewall getrennt dahinter (Home-LAN ≠ Mesh-LAN).
 ## Schicht 2 — Bandbreiten-Pooling (der eigentliche Kern)
 ### Exit-Pool
 Jeder Haushalt bietet seinem Node an, wie viel Uplink er "spendiert"
 (Kontingent, standardmäßig fair-share). Der Exit-Pool ist die aggregierte
 Kapazität. Exit ist **opt-in pro Haushalt und jederzeit widerruflich**.
 ### Segmentierter Multi-Exit-Download (`aki-fetch`)
 ```mermaid
 sequenceDiagram
    participant User
    participant Node (HAUS)
    participant Exits (alle Haushalte)
    participant Origin (Origin-Server)
    User->>Node: GET bigfile.iso
    Node->>Node: Plan (Dateigröße, Range-Splits, Exit-Kontingente)
    par parallel über alle Exits
        Node->>Exits: Range 0–25%
        Node->>Exits: Range 25–50%
        Node->>Exits: Range 50–75%
        Node->>Exits: Range 75–100%
    end
    Exits->>Origin: (je ein GET mit Range)
    Origin-->>Exits: Daten
    Exits-->>Node: Segmente (verschlüsselt über Mesh)
    Node-->>User: Datei (Hash-verifiziert, reassembliert)
 ```
 - HTTP Range Splits + Shadow-Verifizierung (Content-Hash)
 - Fallback: entfällt ein Exit, übernimmt ein anderer das Segment
 - Für nicht-rangefähige Quellen: klassische Proxy-Rotation
 ### Generischer Traffic (alles andere)
 VPN-artiges Overlay: pro Gerät ein verschlüsselter Tunnel zu *einem*
 gewählten Exit, Exit-Wahl rotiert; Browsing/Video-Calls laufen über einen
 Exit, große Transfers über alle. Video-Calls werden explizit auf einen
 Exit gepinnt (kein Splitting).
 ### Fairness-Scheduler (`aki-fair`)
 - Max-min Fairness über alle aktiven Nutzer:innen des Netzes
 - Exit-Kontingente (Volumenlimit, Wartungszeit) werden respektiert
 - Karma statt Bezahlung: wer dauerhaft deutlich mehr zieht als er gibt,
  wird fair angesprochen (Drosselung als letztes Mittel, nie als Strafe
  für Berechtigte mit Bedarf)
 ### Nachbarschafts-Cache (`aki-cache`)
 - Transparenter Shared-Cache (lancache-Prinzip): große, popluläre Objekte
  (Steam, Konsolen-Updates, OS-Images, Software-Pakete) kommen aus dem
  Viertel statt aus dem Internet
 - DNS-basiert, pro Haushalt kleine Cache-Slots; gemeinsam sind sie groß
 ## Schicht 3 — Inhalte & Apps (Freenet)
 - `freenet-core` (Rust, AGPL-3.0) läuft als Sidecar auf ausgewählten Nodes
  und stellt verteilte Inhalte/Apps im Viertel bereit: Nachbarschafts-Wiki,
  Microblogging, lokale Services — ohne zentralen Server, auch offline
  erreichbar.
 - Freenet ist **keine Anonymitätslösung** (siehe FAQ) und wird auch nicht
  als solche beworben.
 - Unsere Software nutzt Freenet über `freenet-stdlib` bzw. die
  WebSocket-API (nicht-derivativ), unsere eigene Codebasis bleibt AGPL-3.0.
 ## Sicherheit und Vertrauen
 - Nodes authentifizieren sich gegenseitig per Keypair; Onboarding im
  persönlichen Gespräch (Nachbar:innen sind der Trust-Anchor, nicht PKI).
 - Strikte Netz-Trennung: Mesh-LAN hat keinen Zugriff auf Home-LAN der
  Teilnehmer (Client-Isolation).
 - Kill-Switch: jeder Haushalt kann seine Faser physisch/softwareseitig
  abklemmen; der Node fällt auf "nur eigener Anschluss" zurück.
 - Minimale Logs (DSGVO, siehe [recht.md](recht.md)).
 ## Offene Fragen
 - DSLite/Carrier-NAT-Haushalte: Synchrone Exits gehen, aber
  Konfigurationsaufwand pro Router-Modell prüfen.
 - ISP-AGB: Weitergabe an "Dritte" kann verboten sein (per ISP prüfen,
  siehe recht.md).
 - Wie viel Cache lohnt sich real bei 3–10 Haushalten? (Messung in Phase 2)
@@ -0,0 +1,76 @@
 # Die Kernidee — und ein ehrlicher Realitätscheck
 ## Ursprungsidee
 > Man spannt Glasfaser von Haus zu Haus und baut ein lokales Netz auf. Wenn
 > man über das Internet etwas nachfragt, läuft die Anfrage nicht (nur) über
 > den eigenen Anschluss, sondern die Last wird aufs gesamte Netz verteilt.
 > Jede:r nutzt die Gesamtkapazität der Nachbarschaft, ohne dass es mehr
 > kostet. Schwache Haushalte werden gestärkt. Nebenbei wird Traffic verteilt
 > und ist für Außenstehende schwerer zuzuordnen (Privacy).
 Diese Idee ist gut — und sie ist nicht abstrakt: NYC Mesh läuft genau so
 ("members share their internet"), Freifunk und guifi.net zeigen es in
 großem Maßstab. Was hier neu gedacht ist, ist der **konsequente Exit-Jede**
 statt Exit-Nirgends: Jeder Haushalt bleibt bei seinem ISP, aber Anfragen
 verlassen das Viertel an *allen* Punkten gleichzeitig.
 ## Was technisch funktioniert
 1. **Segmentierte Downloads über mehrere Exits.** Große Dateien werden in
   Byte-Bereiche gesplittet (HTTP Range Requests) und parallel über die
   Glasfaseranschlüsse mehrerer Haushalte geladen. Das ist Multi-WAN-
   Aggregation, nur verteilt über das Viertel. Ein DSL-50000-Haushalt kann
   damit realistisch 5× herunterladen, wenn 4 Nachbarn mitspielen.
 2. **Fair-Share-Scheduling.** Wer gerade nichts lädt, gibt seinen Anteil
   automatisch. Ein einzelner Stream profitiert von fremder Kapazität,
   mehrere Lade gleichzeitig bekommen faire Anteile.
 3. **Nachbarschafts-Cache.** Beliebte Inhalte (Updates, Games, Videos,
   Software-Pakete) liegen im Viertel. Das entlastet die Uplinks stärker
   als jedes Pooling — siehe [lancache](https://lancache.net/).
 4. **Privacy durch Verteilung.** Der ISP sieht pro Haushalt nur einen
   Bruchteil des ursprünglichen Traffics; Zuordnung "IP → Person" wird
   deutlich schwächer. Backtracking von außen muss die Frage lösen:
   "Welcher der 12 Anschlüsse im Viertel hat das eigentlich gezogen?"
 5. **Resilienz.** Fällt ein Anschluss aus, laufen die anderen weiter — auch
   lokaler Traffic funktioniert ohne Internet komplett (Ethos §7).
 ## Was nicht so einfach ist
 1. **Ein einzelner TCP-Stream kennt kein Pooling.** Ohne Segmentierung oder
   Multipath bleibt ein einzelner Download auf der Geschwindigkeit *eines*
   Uplinks. Der Gewinn kommt aus unserer Download-Software, nicht aus dem
   Kabel — deshalb bauen wir `server/`.
 2. **Alltagstraffic braucht eine Exit-Wahl.** Video-Calls, Banking etc.
   können nicht sinnvoll gesplittet werden. Für generischen Traffic braucht
   es ein VPN-Overlay mit Load-Balancing (mehrerer Exits gleichzeitig),
   damit z. B. Web-Browsing über "die Nachbarschaft" läuft statt über die
   eigene Leitung.
 3. **Physik ist der eigentliche Engpass.** Glasfaser spannen heißt: Genehmigungen,
   Vermieter, Grundstücke, Arbeit. Realistisch beginnt man mit dem, was da
   ist (Kabel im Mehrfamilienhaus, Garten, kurze Richtfunkstrecken), und
   baut Glasfaser dort, wo ohnehin gegraben wird (siehe Recht).
 4. **Volumen-/Drosseltarife.** Wer ein Volumenlimit hat, zahlt mit Volumen,
   wenn Nachbarn über seinen Exit laden. Lösung: Exits haben harte Kontingente
   und der Scheduler respektiert sie ("Exit-Karenz"), plus Karma.
 5. **Privacy ist ein Nebenprodukt, keine Anonymität.** Freenet sagt es
   selbst (FAQ): keine Anonymität wie Tor/I2P. Metadaten bleiben. Wer echte
   Anonymität will, legt Tor/I2P über das Netz. Wir verkaufen deshalb
   Privacy-by-Design, nicht Anonymität.
 6. **Recht.** Abmahnungen landen zuerst beim Anschlussinhaber, egal wer
   geladen hat; bewusstes Ermöglichen von Rechtsbrüchen kann eigene Haftung
   erzeugen. Details und Gegenmaßnahmen: [recht.md](recht.md).
 ## Der technische Kern (warum es Software braucht)
 Das Netz ohne Software ist "nur" ein LAN. Die Mehrwerte entstehen durch
 einen **AKI-Node** pro Haushalt, der folgendes macht:
 - Overlay-Routing über alle Haushalte (Kandidat: Yggdrasil)
 - Exit-Pool verwalten: Wer darf über wen raus, mit welchem Kontingent
 - Segmentierten Multi-Exit-Downloader (API + CLI + Browser-Integration)
 - Fairness-Scheduler über alle Haushalte
 - Transparenten Nachbarschafts-Cache
 - (Später) Freenet als Inhalts- und App-Ebene im Viertel
 Siehe [architektur.md](architektur.md) und [server/README.md](../../server/README.md).
@@ -0,0 +1,93 @@
 # Rechtslage (Deutschland)
 > ⚠️ Keine Rechtsberatung. Stand: September 2026, aus öffentlich zugänglichen
 > Quellen zusammengestellt. Für den Ernstfall: Anwält:in für Urheberrecht/
 > Telekommunikationsrecht fragen — im Kollektiv, nicht alleine.
 ## 1. Urheberrecht / Filesharing — das größte Risiko
 ### Wie die Rechtsprechung heute funktioniert
 - Wer im Netz einer IP-Adresse etwas rechtswidrig bereitstellt, führt zur
  **Täterschaftsvermutung** gegen den Anschlussinhaber (BGH, 12.05.2010,
  I ZR 121/08). Diese Vermutung kann erschüttert werden, indem man darlegt,
  dass **andere selbstständigen Zugang** zum Anschluss hatten ("sekundäre
  Darlegungslast") — man muss nicht den Täter benennen (LG Frankenthal,
  06.08.2019, 6 O 398/17; AG Bochum, 16.04.2014, 67 C 57/14 — WG-Fall).
 - **Störerhaftung** des Zugangsvermittlers für Unterlassung/Schadensersatz
  wurde 2017 weitgehend abgeschafft (§ 8 Abs. 1 S. 2 TMG a.F., heute in
  DDG/DSA weitergeführt; BGH "Dead Island", I ZR 64/17). Es bleibt ein
  **Sperranspruch** (§ 7 Abs. 4 TMG a.F.): Rechteinhaber können verlangen,
  dass der Anschlussinhaber konkrete rechtsverletzende Inhalte sperrt,
  wenn es ihm zumutbar ist (Verbraucherzentrale: das kann Registrierung,
  Passwortzwang bis hin zur vollständigen Zugangssperre bedeuten).
 - **Abmahnungen landen trotzdem zuerst beim Anschlussinhaber** — Rechteinhaber
  wissen nicht, wer wirklich geladen hat; die Ermittlung läuft über die
  zentrale IP-Adresse (Verbraucherzentrale Berlin).
 - Wer **Kenntnis** von einer Rechtsverletzung über seinen Anschluss hat und
  nicht einschreitet, kann haften (Störerhaftung bei konkretem Hinweis).
 - Wer **bewusst und gezielt** Infrastruktur bereitstellt, um Rechtsbrüche
  zu ermöglichen, kann als Teilnehmer/Beihelfer behandelt werden
  (Analogie: BGH zu Tor-Exit-Betreibern mit Vorbelastung).
 ### Was das für das AKI-Netz bedeutet
 1. **Exit-Haushalt = Verantwortung bleibt beim Exit-Haushalt.** Wenn
   fremder Traffic über meinen Anschluss ins Internet geht, gilt:
   - Ich muss darlegen können, dass andere Zugang hatten → das Netz
     dokumentiert (lokal, nicht zentral!) die Teilnehmerschaft.
   - Bei Kenntnis einer konkreten Verletzung muss ich handeln können →
     deshalb braucht der AKI-Node technische Wege, einzelne Nutzer/Segmente
     zu sperren, ohne das ganze Netz zu killen.
 2. **Kein "Das ist ja verteilt, also legal."** Wer lädt, bleibt Täter —
   unabhängig davon, über welchen Exit. Verteilung ändert die Ermittlungs-
   lage (schwerere Zuordnung), nicht die Haftung des wirklich Tätigen.
 3. **Piraterie ist kein Feature.** Ethos §5: Das Netz wird als
   Infrastrukturprojekt betrieben. Downloads großteils über Overlays
   (Freenet/I2P/Tor) zu leiten ist ein technischer Schutz für *alle*
   — aber die Werbung dazu gehört nicht auf die Projekt-Homepage.
 4. **Sekundäre Darlegungslast brauchen wir als Feature:** Der Node führt
   (lokal, minimal, DSGVO-konform) eine Teilnehmerliste, die im Ernstfall
   belegt: "Auf meinem Anschluss hatten N Personen unabhängigen Zugang."
 ## 2. ISP-AGB / Vertragslage
 - Viele deutsche Provider verbieten in AGB die **Weitergabe an Dritte**.
  Konsequenz: pro ISP prüfen, ggf. Tarif wählen, der das erlaubt, oder
  Formulierung als "privates WLAN-Netz im eigenen Haushaltsverbund"
  (Nachbarn ≠ Gäste ist eine Grauzone). Offenlegen, nicht verstecken.
 - Netzneutralität: Pooling ist kein Problem, solange wir nicht nach
  Inhalten filtern oder drosseln.
 ## 3. Physik: Kabel verlegen
 - **Mehr-/Eigentumsfamilienhäuser:** einfachste Route — Innenausbau mit
  Zustimmung Eigentümer:in.
 - **Kabel über fremde Grundstücke:** braucht Zustimmung (Dienstbarkeit/
  Gestattungsvertrag). § 918 BGB (Notwegrecht) greift nicht automatisch
  für Leitungen über fremdes Grund; sauberer Weg ist Zustimmung durch
  Vertrag.
 - **Unterirdische Verlegung in öffentlichen Flächen/Straßen:** Bauanfrage
  bei der Gemeinde, ggf. Tiefbauamt — das ist der reguläre Weg für
  Nachbarschafts-Fiber-Projekte (guifi.net und Community-Fiber-Initiativen
  in Deutschland machen es vor).
 - **Richtfunk als Alternative:** keine Grabungsrechte nötig, nur
  Sichtlinie und ggf. Denkmalschutz am Gebäude.
 ## 4. Datenschutz
 - Nodes loggen minimal (nur Betriebsmetriken, keine Inhalts-/Nutzungs-
  profiles).Logs bleiben lokal, nichts geht zentral ab.
 - Teilnehmerdaten (Namen, Adressen) bleiben **außerhalb des Repos** und
  außerhalb der Nodes, wo es nicht nötig ist.
 ## 5. Zusammengefasste Regeln für die Software
 Damit Agents und Developer das im Code umsetzen:
 1. Exit ist opt-in, dokumentiert und jederzeit widerrufbar.
 2. Node kann einzelne Teilnehmer/Segmente sperren (Sperrpflicht-Umsetzung).
 3. Logs: minimal, lokal, keine Inhaltslogs.
 4. Keine Funktion, deren alleiniger Zweck das Verstecken von Rechtsbrüchen ist.
 5. Heavy-Traffic-Default: Freenet/Overlay bevorzugen, wo sinnvoll.
 6. Datenschutz by default; keine zentrale Datensammlung.
@@ -0,0 +1,56 @@
 # Roadmap
 Kleine Schritte, alles muss für sich allein funktionieren. Jede Phase
 endet mit etwas, das man benutzen kann.
 ## Phase 0 — Grundlagen (jetzt)
 - [x] Doku-Grundstruktur (Ethos, Idee, Architektur, Recht, Roadmap)
 - [x] AGENTS.md mit Projektregeln
 - [x] Gitea-Repo + initialer Push
 - [ ] Prior Art vertiefen: Freifunk-Community in der Nähe kontaktieren
 - [ ] ISP-AGB-Check für die Teilnehmer-Haushalte
 ## Phase 1 — Pilot (2–3 Haushalte)
 Ziel: Beweis, dass Pooling über zwei Anschlüsse real funktioniert.
 - [ ] AKI-Node auf Mini-PC (Raspberry Pi / N100-Box), Yggdrasil-Overlay
      zwischen 2 Haushalten (Kabel oder kurzstrecke WLAN/60-GHz)
 - [ ] `aki-fetch` PoC: segmentierter Download (HTTP-Range-Splitting) über
      2 Exits, plus Baseline-Messung (1-Exit vs. 2-Exit, gleiche Datei)
 - [ ] Fair-Share-Scheduler v0: zwei gleichzeitige Downloads, faire Aufteilung
 - [ ] Doku: Messwerte, Erkenntnisse, Stolpersteine → hier in das Repo
 ## Phase 2 — MVP-Software
 Ziel: ein Paket, das 3–10 Haushalte installieren können.
 - [ ] `aki-node` Daemon: Discovery, Peering, Metriken (per-Exit Bandbreite/
      Latenz), Onboarding-Flow (QR/Knopfdruck)
 - [ ] Exit-Pool: Kontingente, opt-in/opt-out, Kill-Switch
 - [ ] `aki-fetch`: API + CLI + einfache Browser-Integration
 - [ ] `aki-cache`: lancache-artiger transparenter Cache (DNS-basiert)
 - [ ] Fairness-Scheduler v1 (max-min, Exit-Kontingente, Karma)
 - [ ] Telemetrie: keine zentrale Sammlung; lokale Metriken im Node
 ## Phase 3 — Nachbarschafts-Rollout
 - [ ] Onboarding-Doku für Nachbarn (Hardware-Einkaufsliste, Schritt-für-Schritt)
 - [ ] Physische Ausbaupläne pro Häuserblock (Glasfaser wo gegraben wird,
      Richtfunk als Standard-Alternative)
 - [ ] Gemeinschafts-Verträge: Gestattungsverträge für Kabel über Grundstücke,
      Nachbarschafts-Abkommen (Pico-Peering-artig)
 ## Phase 4 — Inhalte & Apps (Freenet)
 - [ ] `freenet-core` als Sidecar auf 1–2 Nodes
 - [ ] Nachbarschafts-Wiki / lokale Dienste als Freenet-Contracts
 - [ ] Offline-Fähigkeit: Netz funktioniert ohne Internet (lokale Dienste)
 ## Phase 5 — Vernetzung darüber hinaus
 - [ ] Peering mit Freifunk-Clouds oder anderen Nachbarschaftsnetzen
 - [ ] Echtes Backbone: eigene Glasfaser in Straßen, ggf. IXP-Peering
      (langfristig, NYC-Mesh-Stil)
 - [ ] Federated Viertel: mehrere AKI-Netze verbinden sich
@@ -0,0 +1,96 @@
 #!/usr/bin/env sh
 # Bootstrap: creates the repo on Gitea (via API) and pushes this project.
 #
 # Requirements:
 #   - python3 (for parsing/decoding credentials from ~/.git-credentials)
 #   - curl, git
 #
 # The credentials live in ~/.git-credentials (credential-helper "store").
 # This script NEVER prints credentials.
 #
 # Only touches the repository named in REPO_NAME. No other repos on the
 # Gitea server are created, modified or deleted.
 set -eu
 HOST="git.dieterunterstrich.de"
 REPO_NAME="anarcho-kommunistisches-internet"
 DESCRIPTION="Nachbarschafts-Netz: gepoolte Bandbreite, Gemeingut, Privacy by Design"
 CRED_FILE="${HOME}/.git-credentials"
 command -v python3 >/dev/null 2>&1 || { echo "ERROR: python3 required" >&2; exit 1; }
 command -v curl >/dev/null 2>&1 || { echo "ERROR: curl required" >&2; exit 1; }
 if [ ! -f "$CRED_FILE" ]; then
    echo "ERROR: $CRED_FILE not found" >&2
    exit 1
 fi
 # Parse credentials for HOST (no output of secrets)
 set -- $(python3 - "$CRED_FILE" "$HOST" <<'PYEOF'
 import sys, urllib.parse, shlex
 cred_file, host = sys.argv[1], sys.argv[2]
 line = None
 with open(cred_file) as f:
    for raw in f:
        if host in raw.strip():
            line = raw.strip()
 if not line:
    sys.exit(3)
 u = urllib.parse.urlparse(line)
 user = urllib.parse.unquote(u.username or "")
 pw = urllib.parse.unquote(u.password or "")
 print(shlex.quote(user))
 print(shlex.quote(pw))
 PYEOF
 ) || { echo "ERROR: no credentials for $HOST in $CRED_FILE" >&2; exit 1; }
 GITEA_USER="$1"
 GITEA_PASS="$2"
 if [ -z "$GITEA_USER" ] || [ -z "$GITEA_PASS" ]; then
    echo "ERROR: could not parse credentials for $HOST" >&2
    exit 1
 fi
 RESP_FILE=$(mktemp)
 trap 'rm -f "$RESP_FILE"' EXIT
 echo "Creating repository $REPO_NAME on $HOST (owner: $GITEA_USER) ..."
 STATUS=$(curl -s -o "$RESP_FILE" -w "%{http_code}" \
    -X POST "https://$HOST/api/v1/user/repos" \
    -u "$GITEA_USER:$GITEA_PASS" \
    -H "Content-Type: application/json" \
    -d "{\"name\":\"$REPO_NAME\",\"description\":\"$DESCRIPTION\",\"private\":false,\"auto_init\":false}")
 case "$STATUS" in
    201) echo "Repository created." ;;
    409) echo "Repository already exists - continuing." ;;
    401) echo "ERROR: authentication failed (HTTP 401). Is 2FA enabled or password wrong? A token may be needed." >&2; exit 1 ;;
    403) echo "ERROR: forbidden (HTTP 403)." >&2; exit 1 ;;
    *)   echo "ERROR: unexpected HTTP status $STATUS" >&2; sed -e 's/[^-]*-/x-/g' "$RESP_FILE" >/dev/null 2>&1; cat "$RESP_FILE" >&2; exit 1 ;;
 esac
 REMOTE_URL="https://$HOST/$GITEA_USER/$REPO_NAME.git"
 cd "$(dirname "$0")/.."
 if [ ! -d .git ]; then
    git init -b main
 fi
 if git remote get-url origin >/dev/null 2>&1; then
    git remote set-url origin "$REMOTE_URL"
 else
    git remote add origin "$REMOTE_URL"
 fi
 if ! git diff --cached --quiet 2>/dev/null || [ -n "$(git status --porcelain)" ]; then
    git add -A
    git commit -m "Initial project structure: documentation, server concept, agents instructions"
 fi
 echo "Pushing to $REMOTE_URL (branch: main) ..."
 git push -u origin main
 echo "Done."
@@ -0,0 +1,54 @@
 # AKI Node — Server/Software (Konzeptphase)
 Die Software, die aus "Nachbarschafts-LAN" ein gepooltes Bandbreitennetz
 macht. Sprache: **Rust**. Status: **Konzeptphase — noch nichts implementiert.**
 ## Zielbild
 Pro Haushalt läuft ein AKI-Node (Mini-PC oder Einplatinenrechner), der:
 1. Das Nachbarschafts-Overlay bildet (Yggdrasil als erste Wahl)
 2. Seinen eigenen ISP-Uplink als **Exit** anbietet (opt-in, Kontingent)
 3. Downloads über **alle verfügbaren Exits** segmentiert und parallel lädt
 4. Traffic fair zwischen allen Teilnehmenden aufteilt (max-min Fairness)
 5. Einen geteilten Nachbarschafts-Cache bedient (lancache-Prinzip)
 6. (später) `freenet-core` als Sidecar laufen lässt für verteilte Inhalte/Apps
 ## Geplante Komponenten
 | Crate/Binary | Zweck |
 |---|---|
 | `aki-node` | Daemon: Discovery, Peering, Metriken, Onboarding |
 | `aki-exit` | Exit-Dienst: kontingentierter Uplink-Proxy für Nachbarn (verschlüsselt) |
 | `aki-fetch` | Segmentierter Multi-Exit-Downloader (HTTP-API + CLI) |
 | `aki-fair` | Fairness-Scheduler (max-min, Exit-Kontingente, Karma) |
 | `aki-cache` | Transparenter Nachbarschafts-Cache (DNS-basiert) |
 | `aki-freenet` | Integration von `freenet-core` (Contracts für Nachbarschafts-Inhalte) |
 ## MVP (Phase 2 der [Roadmap](../documentation/ideen/roadmap.md))
 Kleinster brauchbarer Schnitt:
 1. Zwei Nodes peeren (Yggdrasil)
 2. Ein Download wird über beide Uplinks gleichzeitig per HTTP-Range
   gesplittet, reassembliert, hash-verifiziert
 3. Fair-Share: zwei gleichzeitige Downloads teilen sich die Gesamt-
   kapazität fair
 4. Exit opt-in per Konfig-Datei; Kill-Switch (Exit aus = Node nutzt nur
   den eigenen Uplink)
 ## Nicht-Ziele (bewusst)
 - Keine Bezahl-/Krypto-Infrastruktur (Kontrast: Althea)
 - Keine Anonymitätsversprechen (Freenet selbst bietet keine; wir auch nicht)
 - Kein Zentralserver, keine zentrale Datensammlung
 - Kein "Piracy as a Feature" (siehe `documentation/ideen/recht.md`)
 ## Technologiestack (Vorschlag)
 - Rust (tokio), `axum` für APIs
 - Yggdrasil als Overlay (später evtl. Babel + WireGuard)
 - `freenet-stdlib` / WebSocket-API für Freenet-Integration
 - HTTP Range Requests + SHA-256-Verifizierung für Segmentierung
 - Lizenz: AGPL-3.0 (freenet-core ist AGPL-3.0; Nutzung über stdlib/API
  erlaubt trotzdem freie Wahl — wir wählen aus Ethos-Gründen AGPL)