It should definitely be possible to setup NGINX & HTTPS to have your i2p router accessable at that domain, but id recommend just using the ssh tunnel with key-based authentication only, it adds an extra layer of authentication and encryption that cant be bruteforced or guessed.
But I strongly advise against having your I2P router bind to a public ip address with just plaintext HTTP
I'm using Nheko, I know for sure that it works on Linux, I'm using it on my machine, but on the github it lists MacOS and Widnows in the tags, so I figure they are supported. It's a native program written in Qt and C++.
Idk if im allowed to link it here, but for anyone having trouble accessing TG, they offer an onion service on tor, which is gonna be a whole lot harder to block, you can find the link on their official proxy list
Nheko is my favourite client, it uses QT and is written in C++, its lightweight and works well on my machines with low resources, it also respects my system theme
I think staying inside the tor network helps reduce the load on exit nodes, which helps all tor users who need to access the clearnet. I think there is even a HTTP header that can be put on the clearnet site that will put a button on the tor browser that tells users that there is a onion available.
I figure that the administrators of your homeserver could see your IP address, I doubt that it would be sent to anyone you are just chatting with.
If its just / owned by the mint user, you should just able to run chown root:root / as root/sudo, dont use -R. This should make root become the owner of /. Now if all files and directories in the partition are owned by the mint user, this might be a bigger problem
I did a internet search on "AAAD" and I found this github repository. I'm not sure if it is the same, but they seem to serve the same purpose and share the same name. I took a look into the code and I saw something about Settings.Secure.ANDROID_ID in AboutPaymentActivity.kt, so I did some searching on that, and according to a person on stackoverflow, Settings.Secure.ANDROID_ID is a ID unique to every app on your phone, this ID will persist across uninstalls and reinstalls. The only reason it should change is if the package name or signing key changes. Also it should be different for different users on the phone, but im guessing it might not be possible to add more users on android auto, im not sure, I've never really used one.
Now, about circumventing it, you could modify the source code and remove the license verification checks and rebuild, but this might not be legal, I'm not to good with legal stuff, but the license had a few words that suggest it might be non-free, but if software licenses arent an issue, feel free! There is also the option of just resigning the apk with your own key, which should change the ID, I believe you can do this in luckypatcher with one click, but lucky patcher is kind of sketchy and might not be able to work on android auto, I dont know much about them.
I hope this helps, im sorry I couldnt find any like anything that could just reset it and be done with it, maybe someone else might chime in with a more helpful answer.
If Firefox can read it from disk without a password, any other program running as your user can read it from disk without a password. But to prevent this you can encrypt your Firefox profile with a password.
I use SSH with port fowarding to securely access my services running on my server to anywhere I have internet. Its easy to setup, just expose any device running a ssh server like openssh to the internet, probably on a port that isnt 22, and with key only authentication.
Then on whatever device you want to get your services on you can do like
ssh -p 8022 -L 8010:192.168.75.111:80 user@serverspublicip
Where 8022 is the port of the ssh server exposed to the internet (default is 22), 8010 is the port its gonna bind to on the device you are using the client (it will bind to 127.0.0.1 by default), 192.168.75.111:80 is the address/hostname and the port of where your services are on your local network, and user@serverspublicip is your username and the ip address of where your ssh server is.
You can also use ssh to make a SOCKS proxy in your network like this
ssh -g -D 1080 user@serverspublicip
This will make a socks proxy into your network on your device at 127.0.0.1:1080.
All of this can also be done on just about any mobile phone running android by using termux.
I just gave it a try on my system and it worked just like it did before! Ill have to change my scripts to mount to /run/nextroot instead of /mnt, but i am very relieved that it is still possible. I was having trouble with it all morning. Thank you so much for your reply! It is much appreciated!
I've never used this app, but it looks like its using i2pd, I would look for the
i2pd.conf, and change the bandwidth flag from L (32kb/s) to like O (256kb/s) or P (2048kb/s), but performance may still not be very good if your router is firewalled.But you might just be getting bad peers, the speed of a tunnel will be limited by its weakest peer, I would try increasing tunnel quantity on both sides, and allowing inbound traffic on both routers if they arent un-firewalled already, if possible.