On Aug 15, 10:56 pm, Kevin Mesiab wrote:
> If you store them as blobs, we're going to revoke your compiler privileges.
Good thing that lately I was mainly doing PHP or Python, so no
compiler privileges were needed - only parser
Any other comments on the question in hand?
Thanks,
w you implemented it in your apps and other ideas
related.
Thanks,
--
Arik Fraimovich
follow me on twitter: http://twitter.com/arikfr
On Aug 9, 10:13 pm, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone.
Everything seems to behave much better now.
Thank you and the rest of the team !
--
Arik Fraimovich
large social graphs.
What is defined as "large social graphs"?
--
Arik Fraimovich
follow me on twitter: http://twitter.com/arikfr
Patrick & weex - thank you both for your answers. I guess I will go
with #2. Thanks.
On May 15, 3:06 am, weex wrote:
> Option two. That's what I do as well for Tweet Scan user search.
> Database fields should be atomic and I bet the profile schema doesn't
> change in a way that breaks your (prop
I came to the point in my application development, that I need to
start caching profiles. I guess that many of you already doing such
caching and can share some tips from your experience.
Basically what I thought about is to store the cached profiles in a DB
table. What I wasn't sure about is the
You guys rock ! :)
On May 13, 2:10 am, Doug Williams wrote:
> Wait, no really...
>
> I have a NASA contact that worked with us to make tweets flow from space.
> I'll ping him and see if we can get a source parameter patched into the
> update logic.
>
> Yay geeks!
>
> Thanks,
> Doug
> --
>
> Doug
Someone already developed an application that forwards mentions to DM
(see here: http://apiwiki.twitter.com/Application-Ideas).
When I tried it, it didn't work that good, but I think he did some
changes since then.
On May 11, 8:15 am, TjL wrote:
> I've been banging my head against this for seve
> DK was abandonded by Yahoo awhile ago, but DKIM is very stable.
> Twitter runs DKIM signing and verification code on all of our mail
> servers, as does Google, Facebook, Yahoo, and many other major sites.
OK. Will study further and implement the necessary check.
And Dale - I somehow missed
> I do have to question having your client verify DKIM again, though.
> These activities should be dealt with inside of your MTA and not a
> mail destination script hanging off of the MTA. What exactly are you
> trying to protect against? A user forging an email to your MTA as
> twitter?
Y
> > user=example@postmaster.twitter.com. If you set the address to be
> > something random and non public, like MD5(time)@yourdomain.com, it
> Ah, but then your email address wouldn't be very human readable and
> you'd have to change your email address all the time (if you were
> using the
On May 4, 1:26 pm, John Adams wrote:
> On May 4, 2009, at 12:02 AM, Dale Cook wrote:
>
> > So my question is, is there anyway to authenticate that the email is
> > actually coming from twitter and not someone else?
>
> It's pretty easy to prove the mail was sent from us. We use
> DomainKeys. Va
We at Topify thought of using that method, but decided not to. It
seems to be too intrusive to change someone's email that way. I prefer
the user does that on his own.
Actually, I think they should deprecate this method - never seen an
application that uses it and don't want to stumble at one tha
On Apr 13, 10:37 pm, Matt Sanford wrote:
> It is currently the case that you will get the Accept/Deny page
> every time. We're working on a redirect like Zachary mentioned and
> hope to have it out by the end of the week.
Is this kind of usage you will encourage or is it still be better
near
future?
Thanks,
Arik Fraimovich (@arikfr)
15 matches
Mail list logo
