I'm curious to hear what others are #SelfHosting! Here's my current setup:

Hardware & OS

• Hardware: #RaspberryPi500 (8 GB RAM, 512 GB SD card) #RPi #RPi500 #SingleBoardComputers #HomeLab
• OS: #Stormux, an accessible #Linux distro based on #ArchLinuxARM #LinuxAccessibility #AccessibleTech

Infrastructure & Networking

• Dashboard: #Glance (#Docker) #DockerApps
• Reverse Proxy: #Caddy
• DNS: #Cloudflare
• Domain Registrar: #Porkbun
• Networking & Remote Access: #Tailscale (non-Docker), love its SSH agent and magic DNS features. #NetworkSecurity

Security & Monitoring

• Ad Blocking: #AdGuardHome (non-Docker). Previously used PiHole but find AdGuardHome slightly faster. #PrivacyTools
• Server Monitoring: #Beszel (non-Docker). Tried Grafana/Prometheus/Alertmanager (accessible but overkill) and Netdata (poor screen reader accessibility). Beszel isn't perfect but best compromise so far. #ServerMonitoring
• Server Overview: #Cockpit (non-Docker)
• Security Tools: #Fail2ban, #FirewallD, #ClamAV, and #Rkhunter (non-Docker). Tried CrowdSec but couldn't get it working on Stormux. #CyberSecurity
• Service Uptime Monitoring: #UptimeKuma (Docker), accessible and easy to use. #MonitoringTools

Authentication & Identity Management

• Authelia (Docker): Just set this up for two-factor authentication and single sign-on. Seems to be working well so far!
  
• LLDAP (Docker): Lightweight LDAP server for managing authentication. Also seems to be working pretty well!
  #AuthenticationTools #IdentityManagement

Productivity & Personal Tools

• Docker Management: #Dockge (Docker). More accessible than Portainer; main issue is built-in terminal isn't readable with screen readers. #DockerCompose
• Docker Logs Viewer: #Dozzle (Docker), great web interface and easy searching.
• Git Hosting: #Forgejo (non-Docker), my personal Git server. #GitServer
• Backups: #IDrive (non-Docker), backs up all my devices easily. #BackupSolutions
• Notes: #Joplin server (Docker). Accessibility improving; love the VSCode extension. #NoteTakingApps
• Bookmarks: #Linkding (Docker). Accessible bookmark manager with good browser extension support. #BookmarkManager
• Recipes: #Mealie (Docker), starting to learn cooking!  #CookingApps
• RSS Feeds: #Miniflux (non-Docker), excellent accessibility. Originally wanted better podcast support but other options had major accessibility issues. #RSSReader
• Automation & Workflows: #N8N (Docker). Haven't explored deeply yet—open to ideas! #AutomationTools #WorkflowAutomation
• Pastebin Service: #PrivateBin (non-Docker). Considering alternatives or CLI tool for easier console access. #PastebinAlternative
• File Sharing & Editing: #Samba (non-Docker), easy file management from my Windows 11 mini PC. #FileSharing #Windows11
• Search Engine: #SearXNG (non-Docker), accessible and searches multiple engines at once. #PrivacySearchEngine
• IRC Client: #TheLounge (non-Docker). Some accessibility issues but best I've found so far for always-connected IRC. #IRCClient
• Read Later Service: #Wallabag (Docker). Biggest issue is Wallabagger Chrome extension doesn't work for me yet. #ReadItLater

Notifications & Development Workflow

• Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
• Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote

Accessibility Focus ️

Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!

I've also experimented with:

• Ollama (#Ollama): Not enough RAM on my Pi.
• Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.

I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services!

What's your setup like? Any cool services you'd recommend I try?

#SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY

@selfhost @selfhosted @selfhosting

RetroShare is a free, cross-platform software for serverless communication, including letters, instant messages, and file exchanges over an encrypted F2F/P2P network. This network is built on GPG algorithms and the Perfect Forward Secrecy protocol.

https://bastyon.com/post?s=5b8ca60211e5f0df4ed3316953990e2650f0881ace9ec7a0325327e5c33b6dbf&ref=PFN2jQQL5PSwEdGP7h5T7JzkZMzeps98P2

What is RetroShare?
RetroShare is part of the darknet class of networks, where connections and data exchanges are limited to a specific group of participants, excluding external contacts. In this network, participants' IP addresses are hidden from each other, except within a trusted circle.
Instead of using IP addresses for packet addressing, RetroShare employs a 128-bit random identifier—an anonymous ID. This makes it nearly impossible to determine the IP addresses of participants, even within a user's close network. In essence, monitoring file-sharing or communication activities is exceedingly difficult, and determining the number of participants in the dark network is non-trivial.
Key Features of Dark Networks
Dark networks like RetroShare share two important characteristics:
Difficult Monitoring: It's hard for external parties to monitor user activities, as they are not connected to the network.
Invisible Connectivity: It is impossible to know whether a user is connected to such a network from outside the immediate environment, making RetroShare hard to detect.
This distinguishes dark (private) anonymous networks from public anonymous networks, where participants' IP addresses can be observed directly or indirectly. Furthermore, connecting to an arbitrary node in RetroShare requires confirmation from the counterpart, which adds an extra layer of privacy.
A Simple Guide to Connecting to RetroShare
This article is for those who want to quickly connect to the RetroShare network without delving into the complexities of accessing it via Tor or I2P. Here's a simple guide to getting started with RetroShare:
Download and Install the Client Program
Visit the official RetroShare website: retroshare.net.
RetroShare is cross-platform, which means it supports various operating systems, including mobile ones! Linux users can build from source, but for simplicity, we’ll use an AppImage.
Set Up the Program
It's recommended to route all traffic through a VPN for added security. Leave it enabled for the duration of RetroShare’s usage. If you’re communicating only with trusted individuals (e.g., family), it’s not critical.
Download the AppImage here: RetroShare AppImage.
Make the file executable by right-clicking and enabling the "Allow execution of the file as a program" option.
Open a terminal and navigate to the file's location: /root/RetroShare-0.6.4.20180313.0e6d27ad-x86_64.AppImage.
RetroShare will launch, and a new profile creation window will appear. Before proceeding, click on “Options” in the top-right corner.
Configure Your Profile
Fill in the following fields:
Name
Device Name
Password (and confirm)
Chat Name
Encryption Key (be sure to set it to 4096 bits)
Node Settings (leave as default)
Entropy (wait until the bar is full)
Once done, click "Let’s Get Started." RetroShare will generate your certificate, which can be shared via closed channels or in person. You can then request and add the certificate of the person you're communicating with.
Network Settings
Before diving into the network, it’s essential to modify some default settings:
Expand the service data exchange channel and increase the number of tunnels available to other users.
Higher values mean you contribute more to the network by handling both your own and transit traffic from other users. The default is set for a 20 Mbit/s network speed, but you can increase it based on your actual connection speed.
Check the “Use relay servers” box if you have a restrictive router or firewall. This ensures easier access to the network.
Set the destination folder for downloaded files to avoid confusion later. By default, files are saved in a hidden directory like: /root/.retroshare/LOC06_c098e80721a7d1685271211cbe361c03/Downloads.
Finding Trusted Peers
If you don’t have friends using RetroShare but wish to join the dark network, finding trusted peers can be challenging. However, RetroShare now makes this process easier. You can find trusted peers in the built-in chat by exchanging certificates with other users or robots on websites like retroshare.ch.
Enter your certificate in the provided window, press "Submit," and obtain the server certificate. Copy it and add it to your RetroShare certificate list.
Connecting and Building Your Network
Once connected, RetroShare will notify you, and the first node will appear in your list. You can set the trust level for each node according to your discretion.
RetroShare’s Features
Now that you're connected, RetroShare offers a wide range of services:
Contact List
Chat
Post Office
File Sharing
Channels
Forum
Publications
Unlike regular networks, RetroShare keeps the connection details of users within your trusted environment hidden from others in the network. Only those within your immediate network can know you’re connected to RetroShare.
Enhancements with Tor Network Integration
Starting from RetroShare version 0.6, the platform integrates with the Tor network for added privacy. As long as Tor is reliable, RetroShare remains secure, even if the user’s exchange of certificates is disorganized or the settings are unconventional.
The Dark Network and the Role of Authorities
Anyone who exchanges their personal certificate with a RetroShare node becomes a full-fledged member of the dark web and can receive data from anonymous sources. Interestingly, a representative from a punitive or detective agency, after exchanging certificates with two or more nodes, can become a transit point for encrypted data across the network, without knowing the source or destination. This ensures that even law enforcement, while helping grow the network, cannot trace the traffic.
Final Thoughts
Take care of yourself, user! This article is purely informational and does not advocate for any particular actions. The author holds no responsibility, as the ideas presented here are hypothetical, with all coincidences to real events or names being purely accidental.
Author: Telegram Channel @ZapiskiLizermana (Lizerman's Notes)
Швейцарский нож среди мессенджеров
https://omimedia.blogspot.com/2025/03/blog-post.html
#RetroShare #Darknet #Privacy #Security #Encryption #P2P #Anonymous #SafeChat #OpenSource #DigitalPrivacy #CryptoNetwork #MessagingApp #FileSharing #TechForPrivacy #Tor #I2P #PeerToPeer #EncryptedNetwork #Decentralized #PrivateComms #SecureFiles #AnonymousMessaging #DataPrivacy #RetroShareGuide