When sending the Veterans Today or PressTV URL, (Veteranstoday.com / PressTV.com) in a direct message, a "Message not sent" notification pops up and says,
"Error posting message. There was an error in sending your message to -attempted recipient-. It has been saved in the conversation. Please try resending later. (Error: forbidden)"
Obviously many questions arise, silly ones usually, 'What if Twitter just made a mistake?' is a good one. Another hilarious statement might sound like, 'Those websites aren't popular enough, Twitter probably just thinks they're spam.'. However these people are to no surprise guilty of blatant disregard for what we know. PressTV and VT are arguably the last two news programs in the world that are actually telling viewers what is going on. Veterans Today is just horrifying the NWO and Illuminati shills with all the intelligence they leak. These guys have the utmost incredible network of former intelligence and government staff. You don't know about them because you're not supposed to. Top writers of the Veterans Today team are often on RT News speaking the truth. Oh and for all you haven't heard of PressTV, it's because they were banned from North American Satelites. Now you can only watch them if you can access their webpage. The best question, is always the most simple.
The best question, is why?
To those who question the validity of this article, instead of spitting out baseless claims and idiotic theories, let's do some research! :)
On the official Twitter 'Error Codes & Responses' page, there is a chart that looks like this:
| OK | Success! |
| Not Modified | There was no new data to return. |
| Bad Request | The request was invalid or cannot be otherwise served. An accompanying error message will explain further. In API v1.1, requests without authentication are considered invalid and will yield this response. |
| Unauthorized | Authentication credentials were missing or incorrect. Also returned in other circumstances, for example all calls to API v1 endpoints now return 401 (use API v1.1 instead). |
| Forbidden | The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits. |
| Not Found | The URI requested is invalid or the resource requested, such as a user, does not exists. Also returned when the requested format is not supported by the requested method. |
| Not Acceptable | Returned by the Search API when an invalid format is specified in the request. |
| Gone | This resource is gone. Used to indicate that an API endpoint has been turned off. For example: "The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1." |
| Enhance Your Calm | Returned by the version 1 Search and Trends APIs when you are being rate limited. |
| Unprocessable Entity | Returned when an image uploaded to POST account/update_profile_banner is unable to be processed. |
| Too Many Requests | Returned in API v1.1 when a request cannot be served due to the application's rate limit having been exhausted for the resource. See Rate Limiting in API v1.1. |
| Internal Server Error | Something is broken. Please post to the group so the Twitter team can investigate. |
| Bad Gateway | Twitter is down or being upgraded. |
| Service Unavailable | The Twitter servers are up, but overloaded with requests. Try again later. |
| Gateway timeout | The Twitter servers are up, but the request couldn't be serviced due to some failure within our stack. Try again later. |
Our code is #403, otherwise known as "forbidden".
The description of the "error" is 'The request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. This code is used when requests are being denied due to update limits.'
This seems like a passage from a Bill in Washington. On the surface, it would appear our request was being denied due to 'update limits'... When we look at the update limits, it describes limiting tweets, messages, follows, all on a quantitative basis. I send about two or three messages and tweets a day so I am quite sure I am within the numerical threshhold.
So again the question pops up, why?
According to Twitter, as we just read, Error #403 comes as a result of these 'limits'. Upon the realization that there is no correlation between these limits and the URLs failing to send, we must realize Error #403 says two things not one. It mentions that the code is used when requests are denied due to these limits. Before that however, it says "The request is understood, but it has been refused or access is not allowed."
Hint: They don't have to tell you why it's not allowed.
Yes, the reason they are "forbidden" is quite literally for that reason, they are forbidden and ultimately CENSORED.
For those of you who think that these sites aren't sending because they don't have ' https:// '
Newsflash, beforeitsnews.com doesn't and it sends successfully in direct message everytime!
Again, I will repeat. This only applies to direct messaging on twitter. We all know that you can send tweets with said news programs. It is important to understand that direct message, is the only way to truly communicate 1v1 on twitter.
Check the Error Codes and Limits here: https://dev.twitter.com/docs/error-codes-responses
Stew Webb with Glenn Canady
Glenn was notified today by a 19 year old patriot that Twitter is blocking all messages
with Veterans Today.com and PressTV.com in them.
Glenn verified this today and took screen shots.
These are the only websites being prevented from being sent in direct messages. Glenn tried other websites and they work just fine! Twitter is apparently trying to censor and stop the growth of the #1 news site on the planet now putting out all the truth – Veterans Today!
*Mobile version shows Error #403 (forbidden)
Web Version:
Glenn and I am urging all twitter users to get the word out about Twitter’s evil right now!
Send this story viral so they must back down or be destroyed by the alternative media.
Why is Twitter censoring VeteransToday and PressTV?
Was this evil censorship by Twitter against Veterans Today.com and PressTV.com due to the huge interview Gordon Duff did with Stew Webb on June 4, 2014 ?
In this interview Gordon dropped some major Intel and it has caused major waves throughout the US government! Gordon took a lot of heat for his information concerning the confirmed use of mini nukes on 9/11. It has certainly driven the shills in alternative media nuts. Here’s the interview that is being talked about everywhere now. Gordon unloaded on this one! Please share it everywhere you can!
Read the full story here: http://www.veteranstoday.com/2014/06/12/twitter-goes-evil-and-blocks-veterans-today/
More to come
No comments:
Post a Comment