Startup times getting down below 20s definitely helps with this.
Absolutely. SSDs, systemd, and recent kernels definitely help. From the moment the EFI hands over to the kernel, my ca. 9 years old system is ready for login 3 seconds later.
Definitely seeing some people complain about the design changes
The great thing about Mastodon is, that you can freely chose what client you use. If you dislike the original client or web interface, just use Elk, Semaphore, Tusky, etc. whatever you prefer.
The best thing: It is Git-based. So you have a regular Git repository for your wiki and you don't need to learn a new workflow. You can also edit pages in the browser. Permissions are a no-brainer of course. For editing pages, Markdown is used, so you don't even need to learn a new markup language.
Since Codeberg is an open source platform run by a non-profit association all and everything is free to use.
And if you ever want to migrate to somewhere else, just git pull your wiki and you're good to go.
I just checked their FAQ. They have information about SSH, SMB, RDP, connecting private networks (VPN), etc. available. I did not dig deeper regarding specific ports, though.
You could always use a reverse proxy on your side just accepting port 443 connections (https) and forwarding to a specific docker container using a specific port without the outside world even knowing.
I never tried it personally but I assume you're pretty save.
Hereβs how it works:
The Tunnel daemon creates an encrypted tunnel between your origin web server and Cloudflareβs nearest data center, all without opening any public inbound ports.
After locking down all origin server ports and protocols using your firewall, any requests on HTTP/S ports are dropped, including volumetric DDoS attacks. Data breach attempts β such as snooping of data in transit or brute force login attacks β are blocked entirely.
The problem for me is I believe you need to open your network firewall for Lemmy and other federated services to work right?
Yes, of course. Or search for an external reverse proxy. Cloudflare offers something like this. (You set a Cloudflare server IP as target for your domain and then tell Cloudflare your IP and all traffic is routed over the Cloudflare ecosystem so your actual IP is not publicly used.)
I just opened port 443 and forwarded it to my Docker host and have NPM running there, handling all the forwarding to the individual containers, based on the request, but due to my day job I know what Iβm doing :)
You canβt even turn all of this off via UI, but need to use about:config or user.js (the later needs to be explicitly enabled via about:config first).
Hereβs my setup (except some specific settings based on my personal preferences that are not related to privacy).
By default, Mozilla collects [β¦] information about the number of open tabs and windows or number of webpages visited. [β¦] The data collected is associated with a randomly generated identifier that is unique to each Firefox client.
and
Firefox by default sends data about what features you use in Firefox to Leanplum, our mobile marketing vendor [β¦] Leanplum tracks events such as when a user loads bookmarks, opens new tab, opens a pocket trending story, clears data, saves a password and login, takes a screenshot, downloads media, interacts with search URL or signs into a Firefox Account.
and
[Leanplum collects] certain information, which may include your browserβs Internet Protocol (IP) address, your browser type, the nature of the device from which you are visiting the Service[β¦], the identifier for any handheld or mobile device that you may be using, the Web site that you visited immediately prior to accessing any Web-based Service, the actions you take on our Service, [β¦] We also may collect information regarding your interaction with e-mail messages, such as whether you opened, clicked on, or forwarded a message.
It IS a terrible name. But it also is an over one decade old brand.
It will be hard to propagate the new name and have it as recognizable as "Minetest".