SlimSocial-for-Facebook
SlimSocial-for-Facebook copied to clipboard
rignaneseleo
Proxy setting
It is sad that it is not possible to access FB via Tor (by setting custom proxy localhost:9050 or whatever port Tor is configured to use, and thus routing the program's traffic through it). Not even with the new version, v10.0.1.
Please add custom proxy setting (address:port). Would be fantastic to have it, and SlimSocial-for-Facebook would be the only FB client to have this great feature.
I'll add this on the next release.
Is there a proxy I can use for testing?
Oh, really looking forward! :-)
Is there a proxy I can use for testing?
Not really, Tor runs on a device locally, localhost. Can just install Orbot and run it in proxy mode, then the proxy would be localhost:9050 or 127.0.0.1:9050. https://github.com/guardianproject/orbot/releases
ok thanks!
Does facebook.com run on TOR or you need the .onion domain?
No .onion domain is not required, facebook.com opens normally with Tor.
FB does have an official .onion domain (for desktop website at least), but it is super slow. So usually I just open the regular facebook.com (via Tor localhost proxy), nothing wrong and works allright.
(Maybe an advanced/privacy setting to choose between facebook.com and .onion could be added, but this is probably a different/separate feature request. I'm just looking for a custom proxy setting, but maybe someone else will see this thread and open a new issue for the facebook.com/.onion selection setting, who knows)
I pushed the custom proxy feature.
Can you compile and test if it works correctly?
Installed and tried it, but didn't manage to get through - every time I try to set the cursor in the "email address" field, the "Obnovuji..." popup message appears and the screen refreshes and reloads, so I'm never able to type my mail/password and log in because of this
(another thing is that the settings screen is suddenly in Czech :D didn't manage to find the manual jazyk setting to change it)
the czech bug was my fault, and is fixed on the new version you can find in the releases.
Can you please open a new issue with the other bug and more details? I think many users are experiencing the same bug but I don't...
Hi,
Can you please open a new issue with the other bug and more details? I think many users are experiencing the same bug but I don't...
It seems to no longer be the case, everything is ok in v10.0.9 :-)
Does the proxy work?
Unfortunately it seems like no, I tested it with my noname trash account, and it shows the real location instead of the exit node location :-/ Even though the proxy setting is set to where Orbot is running (localhost:9050)
If you have a FB account by chance, can test it by logging in on SlimSocial, and then log in on the PC and see the login locations using this link
Can I jam this issue too? I though proxy will be work even I'm using certain VPN-based hosts protections, e.g. AdAway, NetGuard, personalDNSFilter, etc. to block contacting to Facebook directly and using proxy instead, but it still doesn't work as intended, the app seems using direct connections (logged DNS requests by hosts filter app) even I've turn proxy settings in app to on.
Note that proxy may work if I've exclude this app to be filtered (aka. allowlist/whitelist)
