Open RyanGibb opened 5 months ago
Hopefully I'm not breaking etiquette here, but out of curiosity, how long have you been bridging for? My own FB account has been on it for 12 days and no such message at this point. No comments from other users who have been bridged a bit longer. The bridge itself has been installed only 17 days ago.
I get disconnected every once a week pretty much, the old bridge didn't do this so I think it does have to do with the bridge. I already ready that you should decrease the backfill paging. In my case, hosting the bridge in a different country than my residence might also not help, but I did that with the previous bridge as well, so not sure about that one.
Hopefully I'm not breaking etiquette here, but out of curiosity, how long have you been bridging for? My own FB account has been on it for 12 days and no such message at this point. No comments from other users who have been bridged a bit longer. The bridge itself has been installed only 17 days ago.
Not at all. I've been hosting it for 2 weeks now.
I get disconnected every once a week pretty much, the old bridge didn't do this so I think it does have to do with the bridge. I already ready that you should decrease the backfill paging. In my case, hosting the bridge in a different country than my residence might also not help, but I did that with the previous bridge as well, so not sure about that one.
I have backfill disabled. My bridge is hosted in different country though.
Hello. I also got the problem (version 0.2.0 of the bridge). I've been running the bridge for a month and I got this error last week (19th of march).
I'm running with backfill enabled, and am running the server in the same country as the users.
After switching to this bridge, I also started getting this all of a sudden (the bridge being disconnected, and "We suspect automated behaviour on your account." being displayed when I log-in on messenger.com).
As it is mention in the doc, I'll turn on 2-factor authentication and see if there is any difference.
@rmelotte where in the docs did you find that?
Just as an additional note on this: I have 2FA on, and it was fine on the old bridge, but I got the account disabled message twice using this bridge.
@rmelotte where in the docs did you find that?
Here: https://docs.mau.fi/bridges/go/meta/authentication.html
N.B. In some cases, Meta may decide your account has suspicious activity and block you until you do some tasks like completing a captcha, adding a phone number or resetting your password. It is recommended to have two-factor authentication enabled to reduce the risk of such blocks.
On Tue Mar 26, 2024 at 09:18, rmelotte @.***> wrote:
@rmelotte where in the docs did you find that?
Here: https://docs.mau.fi/bridges/go/meta/authentication.html
N.B. In some cases, Meta may decide your account has suspicious activity and block you until you do some tasks like completing a captcha, adding a phone number or resetting your password. It is recommended to have two-factor authentication enabled to reduce the risk of such blocks.
Ah, thanks. I got confused for a sec, but I do have 2fa already.
Same issue here, I've been running the old python based instagram bridge for months without issues. Switched to the new meta bridge in instagram mode yesterday and already got the first message today. Maybe this bridge is more aggressive on connecting to the servers? I have backfill disabled as far as possible. I have two-factor on and I was asked to complete a captcha.
I got logged out two days in a row after few months of use. I was using Messenger as a bridge, trying now Facebook to check if it makes any difference.
edit: I've not been logged out for for about a week now, i guess it's better to stick to facebook rather than messenger type bridge.
Following up on this, just updated to the newest version and my account got banned instantly.
Following up on this, just updated to the newest version and my account got banned instantly.
Like banned banned, or locked?
I'm using bridge in newest version(0.3.0) - no issues so far. I've been using it since 1 yr(previously was on Python version, right now on this). My account never had any notice about unauthorised access.
I'm hosting it on my own server in different country, but also I have VPN over there - so maybe facebook knows/tagged me that I'm using VPN and my real IP - therefore bridge(or VPS/VPN IP) isn't marked as suspicious.
Instagram is now also giving a similar warning:
Help us confirm that it's you We've noticed unusual activity from your account and have temporarily restricted certain actions. Follow the next steps to help us remove the restrictions on your account.
I'm using bridge in newest version(0.3.0) - no issues so far. I've been using it since 1 yr(previously was on Python version, right now on this). My account never had any notice about unauthorised access.
I'm hosting it on my own server in different country, but also I have VPN over there - so maybe facebook knows/tagged me that I'm using VPN and my real IP - therefore bridge(or VPS/VPN IP) isn't marked as suspicious.
I've also received notification about "unusual activity". I've reconfigured the bridge to use proxy, which passes through my home address - I hope it'll fix the META guys
The proxy is a good idea. I used to host the bridge at home, but now I get this warning since I've started hosting it in the cloud. For me, the bridge doesn't work for more than a couple hours until I get this warning.
I've run into this twice as well. I signed up a Facebook.com account, configured the Meta bridge with Messenger.com authentication a day or two later, and have faced one 24 hour soft-lock (during this time I was only allowed to have one active browser session to Facebook) and today woke up to another BS warning.
The irony is I'm here in Europe, where Meta begrudgingly present me occasional info about the EU-mandated Messenger-without-a-Facebook-account option, but when I tried to follow that registration flow I was given a generic error message with no information on how to proceed (gee, how convenient).
I'm using bridge in newest version(0.3.0) - no issues so far. I've been using it since 1 yr(previously was on Python version, right now on this). My account never had any notice about unauthorised access. I'm hosting it on my own server in different country, but also I have VPN over there - so maybe facebook knows/tagged me that I'm using VPN and my real IP - therefore bridge(or VPS/VPN IP) isn't marked as suspicious.
I've also received notification about "unusual activity". I've reconfigured the bridge to use proxy, which passes through my home address - I hope it'll fix the META guys
Update time ;) I had a lot of issues from Instagram about automated behavior, but I’ve disabled backfilling. Now it won’t complain ;)
I switched my account to DEMA, configured the meta bridge to messenger
mode and it's been running without harassment for a couple of weeks now. I think my particular issue was that I had originally configured the bridge in messenger mode, but was only maintaining an infrequently accessed browser session on Facebook.com rather than Messenger.com. Or maybe it was just because I started the bridge up on an account that had only been created a couple of days prior.
Out of interest, has anyone out there managed to successfully create a Messenger.com-only account in the EU? I've tried the registration flow via the Android app (on GrapheneOS) twice now about 3 weeks apart, and both times I get to the end of the flow (after receiving and providing a mobile number 2FA) and am rewarded with a generic "Server error, kindly go f**k yourself" message :thinking:
Could this be related to this bridge at all?