-
I don't know if it's a bug but when replying to a tweet, the _in_reply_to_status_id_ value must be _tweet.id_str_ and not _tweet.id_.
var s = '@'+tweet.user.screen_name+ ' the answer...';
client.pos…
-
I have been having a look at these issues (#364, #4237 ) which talk about configurable sharding.
For range based sharding is it possible for me to provide compound sharding keys ?
Something like what…
-
https://github.com/pennersr/django-allauth seems to be the latest hot thing (well maintained, tested etc).
-
related news: https://github.com/twitter/snowflake/
hopefully, the new version could be a bit friendlier.
anyways, i'll just share some tidbits of info i found earlier:
https://pbs.twimg.com/media/…
-
So far, the hardest part about writing the compiler for Alloy is naming it. As mentioned in issue #90, Alloy is already an existing language. I also said that I would change it by the time the languag…
-
Hi,
The Twitter/Snowflake IDs are all exactly 20 digits in length but with Particle they vary.
Is there a reason for this and/or any way to have them work in the same way?
Thanks
oasiz updated
9 years ago
-
The discussion from @meh on #941 say that new contributors will be "welcome and treated with respect."
A [code of conduct](https://robots.thoughtbot.com/adding-a-code-of-conduct-to-open-source-projec…
-
It looks like it is recommended to use the `id_str` field from the JSON tweet payload rather than the `id` field, which being a large integer (>53 bits) is prone to approximation error (see [https://d…
-
After running the following test http://3v4l.org/eHKCc and getting the following output for 5.5.3 (and other versions)
```
Same machine same time
1395792668864
1395792668864
1395792668864
13957926688…
bermi updated
9 years ago
-
An example is Twitter's snowflake IDs. They are 64 bit integers, I believe, which causes truncation in Excel and Calc when loaded in as numbers.
An example CSV:
```
"Network","ID"
"twitter",47938607…