[FacebookBridge] fix group title

[Jerther]

I think this fixes (partly at least) this issue: #2014

I also think that using ._de1 is not idea. I'm not sure but they look like dynamically generated tags that change over time (every FB update?) don't they?.

[Jerther]

In the last few days, I've spent a considerable amount of time trying to get a reliable RSS feed from Facebook pages and groups, and I feel the need to say I strongly agree with the main README's rant 😒

[em92]

Hi, @Jerther! Just checked this patch in my instance.
https://feed.eugenemolotov.ru/?action=display&bridge=Facebook&context=Group&g=https%3A%2F%2Fwww.facebook.com%2Fgroups%2F1063910640737972&limit=-1&format=Atom
After applying in started returning "Failed finding posts!". So it is required to make more edits in order to fix #2014

[Jerther]

Hi @em92 , thanks for the feedback. Can you make sure you are not getting this message because Facebook decided to "soft ban" your IP/server? I just want to make sure, although I'm sure you're already aware of that seperate issue.

After 4 days following only 6 pages, Facebook now requires my bridge to log in, so all feeds stopped working. And so with that, I can't test.

I think we're chasing our tail, and the strategy should be changed to allow log in in some way. I'm not sure I have the time to do that, but here are some strategies I can think of:

• Fake a log in cookie in the request header. Some fields could be added on the bridge configuration and would require the user to copy some values from the dev console of a browser.
• Use something like puppeteer to log in once and do all facebook feeds in one go, and maybe store the login cookie. Also, Facebook would see a Chrome browser. Some websites complain about unsupported browsers, although Facebook does not seem to. The configuration woule be changed to a multi-line text field and there would be one url per line.
• Same as the previous one, but handle only a single url. For multiple Facebook feeds, I believe logging in for every request would upset Facebook (some websites detect hammering) so a login cookie would need to be shared accross requests. So I think this is the same as the first strategy, but using puppeteer.

Nothing unfeasible I think, just time consuming, and time is not something I have a lot of ATM...

Now all this may already be discussed elsewhere, I'm not sure. If so, I'm sorry.

[khambrecht]

Hi, @Jerther! Just checked this patch in my instance.
https://feed.eugenemolotov.ru/?action=display&bridge=Facebook&context=Group&g=https%3A%2F%2Fwww.facebook.com%2Fgroups%2F1063910640737972&limit=-1&format=Atom
After applying in started returning "Failed finding posts!". So it is required to make more edits in order to fix #2014

can confirm this. Bridge worked fine for a specific group until 2021/06/02, and fails now with Unable to find group title!
After applying page title fix, I also get Failed finding posts!

[Jerther]

I think this pull request has become irrelevant as I cannot make any more dev since FB has banned my IP.

I got banned from Amazon the same way too.

So frustrating...

See my prefious posts for explanation and possible solutions.