you can use something like smspool.net to verify the account with a one time use #. then google will allow you to link an authenticator app to the account. removing the # from the account afterwards does not remove the TOTP code either.
- Posts
- 0
- Comments
- 24
- Joined
- 2 yr. ago
- Posts
- 0
- Comments
- 24
- Joined
- 2 yr. ago
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
self hosting is the only way to guarantee logs arent shared.
however it also means that your server address only pulls requests for things YOU look at, not the whole pool of people using the server. imo this is a bad trade off as it would allow the services to track my browsing easily anyway.
personally I would recommend looking at libredirect with a large # of frontend instances selcted & a vpn/tor. these websites normally work without javascript, so assuming you have a privacy focused browser your IP is the only tracking metric they really have. spreading your requests out over different servers whilst using a proxy would make this really difficult to correlate as it would require that mutliple instance operators were malicious & collaborating.