fetching my certificates from /etc/ssl/certs directory.
What should I do to adjust to the new CA?
Thanks in advance.
On Jul 19, 5:54 am, John Adams j...@twitter.com wrote:
On Mon, Jul 18, 2011 at 8:17 PM, pgarvie garvie.p...@gmail.com wrote:
Has Twitter done something with its SSL
On Mon, Jul 18, 2011 at 8:17 PM, pgarvie garvie.p...@gmail.com wrote:
Has Twitter done something with its SSL certificates lately? As in
sometime this afternoon? We've been seeing a ton of
sun.security.validator.ValidatorExceptions coming out of Twitter4J
since about 5:30PM, USCentral.
The
On Fri, Jan 28, 2011 at 3:02 AM, JonM j...@altstudio.co.uk wrote:
The following URLs won't parse using the tweet button:
'url' parameter does not contain a valid URL.
http://www.pitchero.com/clubs/stockport/j/team-news-1249.htmlnews_id=247910
Well, that's not a valid URL.
See the RFC.
On Tue, Jan 4, 2011 at 6:39 AM, Felipe Knorr Kuhn fkn...@gmail.com wrote:
Hello everyone,
Although this is probably not the best list to discuss this, perhaps you
guys have some experience to share.
A friend of mine is being threated by a Twitter user via DMs and public
messages.
He
a0 through a4 should offer identical crossdomain.xml files.
They are all going through a CDN, so it might be the case that the CDN
endpoint you are hitting has a stale file.
I just checked all of the CDN endpoints from here and they are returning the
same data. Try again?
-john
On Wed, Dec 15,
, the calls where a registered app sends requests, you can allow
it to go through?
-Nischal
On Sep 28, 10:49 am, John Adams j...@twitter.com wrote:
We talked with GAE and have resolved this issue.
-j
On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty
nischalshett...@gmail.comwrote
We're not currently blocking google app engine; Could you pass along some
source IPs and we'll research?
-john
On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote:
My app http://www.justunfollow.com is not able to connect to Twitter
from the Google Appengine. I had
be the blocking issue, had one a
few months back for Appengine apps. Seems to work fine on my local dev
environment.
-N
On Sep 28, 6:49 am, John Adams j...@twitter.com wrote:
We're not currently blocking google app engine; Could you pass along some
source IPs and we'll research?
-john
At the moment SSL tweet buttons are unsupported.
-j
On Thu, Sep 9, 2010 at 3:23 PM, Jordan McKible jmcki...@gmail.com wrote:
As far as I can tell, the Tweet button javascript does not work on
https pages without warnings. Chrome in particular gives one of those
big red page warnings
Whitelisting only affects your rate limits. It does not remove
authentication or change security requirements.
-j
On Thu, Aug 26, 2010 at 9:09 AM, David Toussaint
david.toussa...@azionare.de wrote:
Thanks! I am aware of that switch already but I was not aware that it
is necessary to use any
I filed a bug with our webclient team. Thanks for finding this.
-john
On Sat, Aug 14, 2010 at 12:43 PM, Tom van der Woerdt i...@tvdw.eu wrote:
On 8/14/10 9:29 PM, Tom van der Woerdt wrote:
On 8/14/10 9:27 PM, Chris White wrote:
It appears that the new twitter share link can be used to
On Thu, Jul 29, 2010 at 4:29 AM, Hemanth hemant...@gmail.com wrote:
I have a sharepoint portal page with few web parts. One of these web
parts is a sharepoint page viewer web part. When I configure the page
viewer web part with the URL www.twitter.com and click on OK button,
my portal page
Setting up an open (or private) proxy in an attempt to get around our rate
limits will possibly result in your application or IP being banned.
The rate limits are there so that everyone can share the service.
-j
On Fri, Jul 23, 2010 at 9:07 AM, Ryan W rwilli...@gmail.com wrote:
I've given up
Please post or forward your app's IP range so we can investigate. Thanks.
-j
On Fri, Jul 23, 2010 at 11:50 AM, nischalshetty
nischalshett...@gmail.comwrote:
Alrite, I can see intermittent errors. So all's not well yet...
-Nischal
On Jul 23, 11:35 pm, nischalshetty nischalshett...@gmail.com
On Jul 23, 11:55 pm, John Adams j...@twitter.com wrote:
Please post or forward your app's IP range so we can investigate.
Thanks.
-j
On Fri, Jul 23, 2010 at 11:50 AM, nischalshetty
nischalshett...@gmail.comwrote:
Alrite, I can see intermittent errors. So all's not well yet
The mobile site has used a wildcard certificate for the last two years; Did
you recently begin experiencing this issue or was your code working in the
past?
-j
On Thu, Jul 22, 2010 at 6:43 AM, bjcoredev jme...@gmail.com wrote:
It seems that SUN WTK 2.5.2 doesn't accept wildcard certificates
accept wildcard SSL
certificates so twitter clients using twitter API written in J2ME
running under these platform can't access the url
https://api.twitter.com/oauth/access_token
anymore so can't process xAuth authentication wich will be mandatory
on 15 august
So .
On 22 juil, 20:20, John
We have renewed the existing wildcard certificate and will be deploying it
soon to api.twitter.com and oauth.twitter.com.
It's from the same vendor, so there should be no issues.
-j
On Fri, Jul 16, 2010 at 11:26 AM, Carlos carlosju...@gmail.com wrote:
After getting SSL errors on Windows
What the main site currently does is to provide SSL images directly from s3
when a user is on https and to provide images over our CDN (twimg.com) when
using a non-ssl connection.
i.e.:
https://s3.amazonaws.com/twitter_production/profile_images/64195496/IMG_1875_normal.JPG
vs.
Twitter Trust Safety has been notified and will be dealing with this
issue.
-j
On Mon, Jul 12, 2010 at 3:06 PM, Jann Gobble janngob...@gmail.com wrote:
We (at Barracuda Networks) have investigated and blocked both of these
domains for our customer base because of the type/number of links we
t.co is not a crawler; Are you referring to the URL unpacking process or
something else?
-john
On Thu, Jun 10, 2010 at 11:46 PM, Ken k...@cimas.ch wrote:
If tco is to be the new three-letter agency and gatekeeper, we would
like to treat it nice and whitelist its crawler. If tco is
There is a fair amount of framebusting code and anti-XSRF/CSRF code designed
to stop Twitter from being opened in a popup window or IFRAME.
That might be what's blocking such requests.
-j
On Fri, Jun 4, 2010 at 12:11 AM, tweetphp zubi...@gmail.com wrote:
THis simple javascript code does not
I think you're referring to ITAR, most of which was repealed in 1997.
Until 1996–1997, ITAR classified strong cryptography as arms and prohibited
their export from the U.S. Times have changed quite a bit since then.
I don't speak for our terms of service group, and this is by no means an
confirm if this is a valid cert from twitter.com or if something
fishy is going on?
It's valid, for the next couple of weeks.
-john
--
John Adams
Twitter Operations
On Apr 27, 2010, at 10:51 AM, Jonathon Hill wrote:
Awesome! I've been looking forward to it. Any word on the other's
slides? I was told they would all be posted after @chirp.
Many slides from Chirp are on www.slideshare.net
Mine's here:
allow you to connect and we'll send you a status indicating that
we've rate-limited you.
If we find it necessary to ban an IP or IP Block, we will block all
traffic from the IP for an extended amount of time, and not in the on-
off way that you are experiencing.
-j
---
John Adams (@netik
of the
computationally expensive MD5 on an image hack.
We still retain the original file (basename) on images.
-j
---
John Adams (@netik)
Twitter Operations
j...@twitter.com
http://twitter.com/netik
On Dec 28, 2009, at 2:53 AM, Drekey wrote:
My company developed a small Flash/AS3 app that pulled some twitts and
twitters from twitters. All was working well even when we put it
online, so the http://static.twitter.com/crossdomain.xml should be
allowing by then.
Our crossdomain.xml file
On Dec 20, 2009, at 9:17 AM, shiplu wrote:
Used all these ips.
128.121.146.100
128.121.146.228
128.121.243.228
168.143.161.20
168.143.162.116
168.143.162.36
168.143.162.52
168.143.162.68
168.143.171.84
It is possible your IP or network was blacklisted on our routers or
firwealls.
Could
On Dec 3, 2009, at 1:09 AM, M. Edward (Ed) Borasky wrote:
It looks like the retweet capability on the standard Twitter web
interface has been turned off. I didn't see an entry on the Twitter
status page about this. Did I miss an announcement?
Retweet should be back on now, Sorry for the
On Nov 17, 2009, at 10:50 AM, David Dellanave wrote:
Could this be related to when an API request returns raw HTML like
the over-loaded page? That would be my first guess.
SSL/TLS negotiation happens much earlier in the transaction, so no,
raw HTML is not a cause of this.
-john
On Nov 15, 2009, at 1:16 PM, Tim Haines wrote:
Hi there,
I'm doing some dev work and I'm getting occasional ssl errors when
making calls against api.twitter.com/1. The most recent was posting
to favorites/create.
Is it possible some of the servers have bad certificates? Or is it
On Thu, Nov 5, 2009 at 8:20 PM, Marcel Molina mar...@twitter.com
wrote:
We've confirmed this and reported it to our operations team. We've
identified the problem and are actively fixing it. Thanks for the
detailed report. I'll let you know when the gzip compression is
restored.
This
On Oct 31, 2009, at 7:04 PM, Zac Bowling wrote:
http://twitter.com/suspended
I'm seeing some profiles redirect to this. It looks like a user.
Weird?
It is a user, unfortunately.
There was a small web server change in the way that suspended accounts
are processed, and the normal
wrote:
Great news guys, I noticed that the search and oauth API's aren't
in
the version one API stream though.
Is this intentional?
--
Marcel Molina
Twitter Platform Teamhttp://twitter.com/noradio
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
--
John Adams
This was patched yesterday afternoon.
-j
On Aug 25, 2009, at 11:38 PM, Costa Rica wrote:
Hello Twitter,
Any official word on this apparent vulnerability around the Source
parameter and cross site scripting?
http://www.davidnaylor.co.uk/massive-twitter-cross-site-scripting-vulnerability.html
On Jul 31, 2009, at 3:37 PM, Josh Roesslein wrote:
Well 64 bit should last for a while. Curious how long it will be
until 128 bit will be required.
Mathematica tells me:
Fri 24 Sep 58821 22:55:00
I think you'll be fine for a long time at 64 bit.
-john
---
John Adams
Twitter Operations
On Jul 31, 2009, at 4:04 PM, Andrew Badera wrote:
but why not go with 128 bit decimal/floating point precision
datatypes to begin with, and never have this issue? if anyone says
overhead I'm gonna whack 'em like a popup weasel. in this day and
age of CPU cycles and RAM, you might as well
On May 29, 2009, at 2:14 AM, jmathai wrote:
What's the geographical distribution of the api servers? And, are
requests routed to the nearest farm/colo?
All servers are currently on the west coast.
-j
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
* of the notifications has
improved. I certainly think that is the right way to go.
- TjL
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
this sorted shortly.
-john
On May 6, 2009, at 3:13 PM, TjL wrote:
FWIW I think nore...@twitter.com is the right choice, it's certainly
a lot easier for image display, etc.
But it sounds like John Adams thinks this is going to change back. I
hope this will be clarified.
On Wed, May 6, 2009 at 5
servers, as does Google, Facebook, Yahoo, and many other major sites.
With regards to maintainability, it depends if you're the admin, or
the developer, I suppose. Both come with their own levels of
associated work.
-j
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
of the email,
and if it doesn't validate, it's not from us.
-j
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
: headers, or the
originating message path if you don't want to implement domain keys.
There exists many standard libraries to do so, though.
-j
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
to protect against? A user forging an email to your MTA as
twitter?
That's defensible by fixing your MTA's configuration (to validate DKIM
and SPF coming from twitter.com hosts) and not doing it in your script.
--john
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
this wrong, or missed
something. :-)
Any help would be much appreciated...
Dave
---
John Adams
Twitter Operations
j...@twitter.com
http://twitter.com/netik
On Apr 8, 2009, at 10:33 PM, orange80 wrote:
Yeah, I started checking the headers and realized that. It doesn't
seem like there's any hard limit on simultaneous connections though so
that helps quite a bit.
Our web servers do not support Keep-Alive.
-j
---
John Adams
Twitter Operations
j
, but then your application would have the user's password.
The scheme you propose is a good intermediary step for a transition,
but not as a long term solution.
From the user's perspective, it's just as easy as OAuth.
Although much harder to revoke!
-j
---
John Adams
Twitter Operations
j
On Mar 7, 2009, at 1:25 PM, Tom Nichols wrote:
2. Also, shouldn't any valid URL respond to the OPTIONS method with
an Allow header? i.e. I would expect
OPTIONS /statuses/destroy/12345.json
to return Allow: POST, DELETE
Right? I attempted this (on a status ID that my user owns) and I got
a
Actually, forcing an app to use the API is better for Twitter. You get
the data directly, and the system doesn't spend any time rendering the
HTML. Less data from us = less time tying up server resources.
There's no reason why you can't write a small amount of code to fetch
a user's
anymore. My recollection is
they mostly relied on vulnerabilities in IE... Kind of ironic
actually. I would not recommend this method as it probably could get
you banned from Twitter.
On Sun, Feb 15, 2009 at 12:11, John Adams j...@twitter.com wrote:
Actually, forcing an app to use the API
Officially supported, and recommended.
-j
On Nov 28, 2008, at 12:24 PM, Ed Finkler wrote:
I'm pretty sure it's officially supported.
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
On Fri, Nov 28, 2008 at 3:18 PM, Jon Colverson [EMAIL PROTECTED]
wrote:
52 matches
Mail list logo
