How carry out I disable Facebook chat availability? My chat is offline and also I am utilizing Windows 7 via Firefox. When I login via my various other account through my mobile Facebook and open a chat conversation I see the account that I use on my computer is active "just now" whenever I move the computer mouse or refresh the page.

You are watching: Waiting for 5 edge chat facebook

How carry out I disable that? Is there some particular heartbeat message that is possible to be blocked via AdBlock Plus or something?



Okay I have actually discovered the solution to block this status.

Basically Facebook supplies a timer and also so it will certainly send a heartbeat message to their servers with the idle time eextremely x minutes.

Here is an instance of such internet request: you check out that link you"ll watch that &idle=117 is the complete seconds the account has been idle for. The state=offline stands for whether the chat is active or offline

Note that I have actually replaced my userid which is a number of 15 digits.

So to disable this simply add the complying with preeminence in your AdBlock filters:

https://*-edge-chat.facebook.comOne drawback of this technique is that you will not receive messperiods in genuine time. You must refresh the page to get the messages.

Improve this answer
edited Oct 2 "15 at 1:23

49.9k3838 gold badges151151 silver badges293293 bronze badges
answered Oct 2 "15 at 1:01

a guy in lovea man in love
36911 gold badge22 silver badges88 bronze badges
Would something prefer this job-related in Safari via iOS 9 content blockers?
Oct 20 "15 at 13:23
Add a comment |
Due to the fact that I"m offering extra details, I"m writing my own answer based upon the original (instead of editing and enhancing it).

Yes, there is a way to carry out this, but this strategy functions just for the web-based Facebook and Messenger; you can"t perform something equivalent for the mobile apps.

Basically, Facebook uses timed researches on the server side to check if the client is still easily accessible. So the front end (loaded Facebook internet page) will certainly periodically send an HTTP request (XHR) via the idle time to their servers.

Here"s an example of such request: I"ve reput the user ID which usually would be a number.

If you check out the URL over, you"ll check out the part saying idle=117. This denotes the full number of seconds the account has been idle for. The state=offline means whether the chat is turned on or off.

So, to disable this, simply include the adhering to dominion to your ad blocker"s tradition list of filters:

||*^$xmlhttprequestTo disable on both, Facebook and Messenger, you have the right to add the following two lines:

||*^$xmlhttprequest||*^$xmlhttprequestOr the single line, making use of regex:

/^https?://d+-edge-chat.(facebook|messenger).com/?/$xmlhttprequestA few drawbacks of this approach are that you"ll not be able to get messeras in genuine time and also you"ll not show up online even if the chat is on. You"ll need to refresh the web page to receive brand-new messperiods.

In order to prevent both of these drawbacks, here"s one workabout. You can add this line instead:

/^https?://*state=offline/$xmlhttprequestOr, include this for both, Facebook and also Messenger:

/^https?://d+-edge-chat.(facebook|messenger).com/pull?.*state=offline/$xmlhttprequestThe finish result of this will certainly be the following:

When your chat is off, you"ll not show up online, your last activity will not be reported, and you will not have the ability to get messeras in actual time.When your chat is on, you will show up digital, your last activity will certainly be reported, and also you"ll be able to obtain messages in genuine time.

See more: The Foreign Purchases, Interest Rate, And Real-Balances Effects Explain Why The

Unfortunately, tright here seems to be no various other solution considering that Facebook"s front end deserve to fetch messeras just once the client periodically reports that they"re energetic, for this reason the fetching is done once the last activity is reported. Both of these actions are made possible by a solitary back-end manuscript (*, via the same request; therefore, you can not have one without the other.