CAPSLOCKFTW

joined 1 year ago
[–] CAPSLOCKFTW@feddit.de 16 points 1 year ago* (last edited 1 year ago) (1 children)

Fennec F-Droid is based on the latest Firefox release (codenamed Fenix). It has proprietary bits and telemetry removed, but still connects to various Mozilla and Google services that can track users.

Edit: Quickly checked an article from Mike Kuketz (german): https://www.kuketz-blog.de/firefox-datensendeverhalten-android-app-f-droid-version-browser-check-teil6/

Fennec contacts mozilla servers to get new lists for the anti fingerprinting and anti tracking technologies. Also xml files with info about vulnarabilities etc. It sends not much.

Google is contacted when you have google as standard search provider and search suggestions active.

Otherwise no tracking etc

[–] CAPSLOCKFTW@feddit.de 9 points 1 year ago (3 children)

I second Mull. Fennec is okay as well.

[–] CAPSLOCKFTW@feddit.de 6 points 1 year ago (1 children)

I have large hands.

[–] CAPSLOCKFTW@feddit.de 4 points 1 year ago

I'm following this one since 2020 and it is really going places. Latest weekly I played was very playable and fun! Great work!

[–] CAPSLOCKFTW@feddit.de 1 points 1 year ago

If you want to host miltiple things with only one ip I woild always recommend a reverse proxy, so it is good that you mention that but since it isn't strictly necessary, it is no alternative imo.

[–] CAPSLOCKFTW@feddit.de 1 points 1 year ago (2 children)

A reverse proxy solves another problrm, doesn't it? In any case it requires one of the solutions I mentioned to make your stuff accessible from outside.

[–] CAPSLOCKFTW@feddit.de 2 points 1 year ago

Might be, I don't know it 😅

[–] CAPSLOCKFTW@feddit.de 4 points 1 year ago (7 children)

Additionally, is a self hosted server only accessible inside my home? What about accessing the services outside, like Bitwarden or Nextcloud apps that require syncing and availability of data wherever I am? If it is useless outside, there would be no point for me personally to self host in the first place since I am perfectly fine with using cloud services for now and the convenience that comes with it. Plus, no one else in my family cares about self hosting and I don't wish to spend the effort to convince them to in vain, so setting up a server for convenience of everyone at home is also out of the question.

It is only accessible from your local network (if it is there in the first place, you can always selfhost on rented virtual private server), until you make it accessible. There a different ways to achieve that:

  • Wireguard tunnel
  • cloudflare tunnel
  • (reverse) ssh tunnel
  • dynDNS
  • opening ports on your router

Which is the way for you depends on the circumstances, how your ISP connects you to the internet mainly

[–] CAPSLOCKFTW@feddit.de 20 points 1 year ago (1 children)

Most Wifi bulbs work locally with home assistant for example. And you can stop their communication with the internet with some basic network administration. Otherwise, Zigbee bulbs do not communicate over the internet, they can't. You will need a zigbee router, but there are open source solutions for that.

[–] CAPSLOCKFTW@feddit.de 4 points 1 year ago

TimeLimit or OpenTimeLimit

[–] CAPSLOCKFTW@feddit.de 2 points 1 year ago* (last edited 1 year ago)

I use reverse ssh tunnels, technically running on my home server. For each service i want to expose on the internet, i have a systemd-unit which handles a said reverse tunnel to the vps. Basically, the port running the service locally gets tunneled to a port on the vps, that happens via ssh, so reasonably secure (login as root disabled, login with password disabled, with a special user with little to no rights running the systemd service locally and remotely to log in via ssh). On the remote vps, there is a reverse proxy running, nginx, which works like the service would be running on the remote vps, really. There are some services actually running there, a mail server for example. The config files aren't really different, everything nginx handles gets passed to a localhost port. A nginx instance is also running on the local home server to serve all the local services and the global ones locally, and the dns on my main router resolves the adresses of the global services to the local ones. SSL-Certificates are acquired by the remote vps and copied to the local home server, so that the end users don't have any difference in their ux regardless if they are in the local network or somewhere outside.

Edit: I mostly use this approach because my ISP uses dualStack lite and I could not access anything local from outside with any other technique. But I like it, it is really basic.

view more: next ›