administrators

Private

Posts

  • RE: [THS] Verificación de ¿Edad? — el FIN del INTERNET ANONIMO

    Resumen del video
    La implementación de la verificación de edad obligatoria en internet se presenta públicamente como una medida para proteger a los menores, pero su objetivo real es acabar con el anonimato en línea y establecer un sistema global de control de identidad. Al igual que ocurre con iniciativas como el chat control, el argumento de "proteger a los niños" funciona como un escudo retórico inatacable que impide cuestionar los métodos empleados. En la práctica, verificar la edad equivale a verificar la identidad, ya que el sistema debe identificar a todos los usuarios, adultos incluidos, para poder filtrar a los menores.

    Esta tendencia se está consolidando como una ola legislativa coordinada a nivel global. En el Reino Unido, la Online Safety Act exige verificación robusta en plataformas con contenido sensible, imponiendo multas millonarias y afectando a grandes sitios web, foros e incluso proyectos como Wikipedia. En la Unión Europea, se avanza hacia la integración de estas verificaciones con las carteras de identidad digital (EIDAS 2.0) previstas para 2026. Australia ya ha prohibido el acceso de menores de 16 años a redes sociales con fuertes sanciones, y varios estados de EE. UU. están impulsando leyes similares que enfrentan batallas judiciales.

    El impacto en la privacidad es severo. Los usuarios deberán entregar documentos, selfies o datos biométricos a terceros verificadores, muchas veces empresas privadas no auditadas que operan como DNI de facto de internet. Esto genera enormes bases de datos vulnerables que registran el acceso a foros políticos, grupos de apoyo o contenido sensible, aumentando el riesgo de filtraciones masivas con consecuencias graves, como se demostró en el caso de Ashley Madison. Además, la vigilancia constante produce un efecto disuasorio: la simple conciencia de ser monitoreado fomenta la autocensura al acceder a información sobre disidencia, salud sexual o adicciones.

    Estas medidas resultan ineficaces y generan daños colaterales significativos. Los menores decididos saltan fácilmente las restricciones mediante VPNs, mientras que los adultos promedio terminan entregando su identidad. Las plataformas pequeñas y aplicaciones sin recursos económicos para costear verificadores externos se verán obligadas a cerrar o a no operar en estas regiones, consolidando un oligopolio tecnofeudal. El mayor daño recae sobre colectivos vulnerables, como comunidades LGTBIQ+, foros de víctimas o recursos de salud mental, que dependen del anonimato para proteger a sus usuarios y garantizar su seguridad.

    La verificación de edad actúa como una puerta de entrada para normalizar la identificación digital en todos los aspectos de la vida cotidiana. Aunque se promueve el uso de tecnologías de conocimiento cero (ZK) que supuestamente no revelarían la identidad, la falta de transparencia, software cerrado y auditoría independiente hace imposible garantizar su funcionamiento real. Históricamente, toda infraestructura creada para un propósito específico termina siendo desviada para otros fines, como demostró el uso de una base de datos fiscal en Ámsterdam por parte del régimen nazi. La tendencia apunta hacia una sociedad estratificada donde la trazabilidad constante y la imposición de clases digitales limiten las libertades individuales.

    Frente a este escenario, existen alternativas viables tanto técnicas como sociales. En lugar de la identificación masiva, se deben priorizar el acompañamiento familiar, la educación digital y el control parental localizado en dispositivos, que protegen sin vigilar a toda la población. A nivel técnico, se recomienda el uso de VPNs sin registros, navegadores que minimicen la huella digital, redes como Tor, claves GPG y la migración hacia internet federado y autoalojado (Fediverso, Oasis). Políticamente, es crucial contactar a representantes europeos, apoyar a organizaciones defensoras de la privacidad como EDRI, EFF o Xnet, y difundir la diferencia entre protección infantil real y vigilancia masiva.

    El anonimato no es sinónimo de ocultamiento, sino una herramienta fundamental para pensar, leer y expresarse libremente. Exigir la identidad para acceder a internet transforma la red en un espacio controlado por corporaciones y Estados, donde los usuarios se convierten en productos rastreables. La verdadera protección de los menores reside en la educación y el acompañamiento, no en la entrega obligatoria de datos biométricos. Mantener una internet abierta, federada y privada sigue siendo posible, pero requiere conciencia, herramientas adecuadas y acción colectiva antes de que el control se vuelva irreversible.

  • RE: Videos Peertube
  • RE: HAMNET MeshCore Western Cape Tech Talk Video

    Video Summary
    The presentation, hosted by the Boerland Amateur Radio Club and facilitated by Hamnet (the emergency communications division of the South African Radio League), examines the rapid growth and practical application of MeshCore and Meshtastic networks in South Africa. Hamnet’s involvement is driven by the need for resilient, license-free communication systems that can bridge disaster management teams with the public when traditional infrastructure fails during storms, load shedding, or other emergencies. The network has expanded quickly in Cape Town, reaching over 120 nodes in just three months, with active participation from both licensed radio amateurs and unlicensed citizens.

    Both platforms utilize affordable LoRa hardware on license-free frequencies (primarily 868 MHz and 433 MHz in South Africa) to enable encrypted direct messaging, public channels, private groups, and IoT telemetry. While no operating license is required, all users must comply with ACARSA regulations, which cap transmission power at 27 dBm (500 mW) and enforce a strict 10% hourly duty cycle. These limits are necessary to prevent interference with industrial telemetry, smart meters, and alarm systems that share the same spectrum.

    The two networks differ significantly in architecture and efficiency. Meshtastic relies on managed flood routing, broadcasting messages across all repeaters up to a maximum of seven hops. This ensures wide initial reach but generates higher background noise and drains batteries faster due to frequent autonomous location beaconing. MeshCore, conversely, uses learned path routing that remembers optimal routes, minimizing broadcasts and supporting up to 64 hops. This creates a quieter network, extends companion node battery life, and allows virtually unlimited virtual channels. MeshCore also features room servers, which act as offline digital bulletin boards capable of storing messages for users who log in later—a valuable capability for disaster coordination and asynchronous communication.

    Each platform excels in different operational scenarios. MeshCore is optimized for dense urban environments and city-wide infrastructure, offering predictable routing without channel saturation, making it ideal for neighborhood networks, community alerts, and disaster management fallback systems. Meshtastic remains stronger for tactical, ad-hoc deployments, search and rescue operations, and real-time team tracking in remote or mountainous terrain, supported by mature visualization software. While a MeshCore SAR app exists to provide similar tracking and template-based alerting, it is still undergoing field testing.

    Proper configuration is essential for interoperability and compliance. In South Africa, users should select an ITU Region 1 preset (such as EU/UK Narrow), which automatically sets the center frequency to 869.618 MHz, bandwidth to 62.5 kHz, and spread factor to 8. The CRC error correction should be set to 8 for improved noise resilience, and the duty cycle must be manually adjusted from the default 50% down to the legal 10%. Repeater placement on high sites with integrated solar panels and battery backups is highly recommended to ensure continuity during power outages. Users are encouraged to slightly offset their node locations for privacy and to utilize tools like MeshMapper to visualize network coverage, signal strength, and repeater performance.

    Successful deployment requires community coordination and respect for property rights; installing repeaters on municipal or private structures requires explicit permission from owners. To prevent radio desensitization, Meshtastic and MeshCore antennas should not be mounted horizontally adjacent to each other; vertical stacking with at least one to 1.5 meters of separation is preferred, or horizontal placement with a minimum of two to three meters between them. The preference for 868 MHz over 433 MHz in Cape Town was driven by the higher legally permitted transmission power (500 mW versus 100 mW), which compensates for the lower frequency's reduced penetration. Looking ahead, Hamnet plans to formally engage disaster management authorities and encourage broader community participation through regional Discord channels and suburb-based groups. Reticulum is also highlighted as a promising future protocol that supports multi-path routing across LoRa, internet, and HF radio, though it remains in an exploratory research phase. New users are advised to actively announce their presence on public channels and test equipment from elevated locations to ensure line-of-sight connectivity.

  • RE: Videos Peertube

    Hilo con resumen del video: HAMNET MeshCore Western Cape Tech Talk Video

  • RE: I Got FieldStation42 Running on Orange Pi Zero 3 (Impossible?)

    Video Summary
    Due to high Raspberry Pi prices, this tutorial explores using an Orange Pi 03 with 1GB of RAM as a practical alternative for running Field Station 42, a free open-source Linux application that automates retro TV station broadcasting. After consulting the software’s creator, who noted that smooth video playback is the primary requirement, the project proceeds with the Orange Pi 03. This compact single-board computer features an Allwinner H618 quad-core processor, Wi-Fi 5, Bluetooth 5.0, Gigabit Ethernet, and 4K micro HDMI output. Paired with Field Station 42’s scheduling engine for shows, movies, commercials, and station IDs, it creates a fully automated cable-style TV setup.

    The installation begins by flashing the Armbian Bookworm Minimal image to an SD card, which excludes a desktop environment to conserve system resources. After booting and connecting via SSH with default credentials, the system prompts for a new root password and standard user account. To ensure stability and match the tested environment, armbian-config is used to switch to Linux kernel version 6.6.75. Kernel upgrades are then frozen to prevent future compatibility issues. A custom repository is added to install a hardware-accelerated FFmpeg build, followed by the installation of all required system dependencies.

    Since Field Station 42 relies on mpv for video playback, the player’s configuration directory and file are created with appropriate settings. X11 is manually configured via a .xinitrc file to prevent screen sleep, launch necessary background processes, and open a terminal window upon startup. Automatic login on tty1 is enabled by editing the corresponding systemd service, ensuring the system boots directly into a graphical session without requiring a physical keyboard. After reloading the systemd daemon and restarting the display manager, the screen successfully shows a ready terminal window.

    To preserve the SD card’s lifespan, media files are stored on an external drive formatted with NTFS or ext4. The drive is identified using lsblk -f, and its UUID is recorded. A permanent mount point is created at /mnt/fs42-files, and /etc/fstab is updated with a UUID-based entry to ensure reliable mounting across reboots. After reloading the system configuration and applying the mounts, the external storage is ready for use.

    The official Field Station 42 repository is cloned from GitHub, and the installation script is executed to set up a Python virtual environment and required packages. A new channel directory is created, and symbolic links are placed in the catalog folder pointing to media folders on the external drive. Separate directories for station IDs and commercials are also prepared. An example configuration file is copied to the conf folder, renamed to match the channel, and edited to define the station’s name, channel number, media paths, and a 24-hour broadcast schedule using tags that correspond to the symbolic links.

    With the Python virtual environment activated, the catalog builder scans the linked media and prepares the station. An initial player startup issue is resolved by running the service installation script, which enables fs42.service for automatic boot-up while temporarily disabling advanced features like the cable box interface and remote control support. After restarting the service, the TV station launches successfully. The tutorial confirms that the Orange Pi 03 with 1GB of RAM reliably runs Field Station 42, laying the groundwork for future expansions including guide channels, multiple stations, and advanced peripheral integration.

  • RE: Videos Peertube
  • RE: Discoveries: tactical-retreat (free cs) - #1

    Video Summary
    The host introduces Tactical Retreat, an open-source reimplementation of Counter-Strike 1.5 built on the Quake engine. Recently discovered through community discussions about libre first-person shooters, the project features completely free code but currently relies on proprietary Counter-Strike assets. The host explains that this licensing limitation is acceptable for coverage, particularly because a parallel initiative called RadSynd is actively working to replace all proprietary content with fully libre alternatives, potentially creating a completely free Counter-Strike clone in the future.

    To avoid the complexity of extracting proprietary assets, the host tests a web-based port of the game. During gameplay, they note several technical limitations, including noticeable lag, frame rate drops, and persistent networking issues that prevent cross-network multiplayer connections, a problem also observed in similar projects like Nazi Zombies Portable. Playing offline against AI bots in deathmatch mode, the host finds the movement mechanics unfamiliar compared to modern Counter-Strike titles and notes that the bots lack intelligence. Despite some graphical glitches like missing skyboxes and shadows, the host appreciates features like weapon silencers and compares the overall feel to Assault Cube, believing the game has strong potential as a libre multiplayer FPS once the assets are fully liberated.

    The host attempts to set up the native desktop version but encounters significant frustration due to poorly organized documentation, confusing repository links, and missing data files required for maps to function. After failing to locate the necessary assets despite following the provided instructions, they decide to continue using the web port. During this segment, the host also briefly discusses their hardware upgrade plans, explaining their intention to wait for the release of Zen 6 processors and DDR5 memory to build a long-lasting PC rather than upgrading frequently, noting that their current system still runs on a 2015 CPU.

    Finally, the host experiments with running the web port in different browsers to improve performance. Switching from LibreWolf to Ungoogled Chromium resolves memory limitations and allows the game to run high-quality models without crashing. The test reveals that Chromium handles the web-based engine more efficiently, though it introduces minor quirks like altered resolution settings and unexpected audio source spawning. The episode concludes with the host acknowledging the browser's impact on performance while reiterating interest in the project's future development.

Member List