fluidinfo / tickery Goto Github PK

Explore Twitter with Fluidinfo

License: Apache License 2.0

Shell 0.48% Python 99.52%

tickery's Introduction

Welcome!
--------

Tickery is an open-source application written on Fluidinfo
(http://fluidinfo.com/). You can play with our running version at
http://tickery.net

Tickery provides a fun way to explore sets of Twitter friends. There's much
more to the story however, as its underlying data is stored in Fluidinfo.
This means it can be added to by anyone (i.e., you!), and searched on in
any way.

We've open-sourced Tickery to help programmers see the insides of a
substantial application written to use Fluidinfo. Although the Tickery
documentation is currently very light, we hope to be able to change this.
You're welcome to help, of course.

Learning about Tickery
----------------------

The best place to read an introduction to Tickery is in two articles on the
Fluidinfo blog:

  Meet Tickery
  http://blogs.fluidinfo.com/fluidinfo/2010/01/21/meet-tickery/

  Tickery, for programmers
  http://blogs.fluidinfo.com/fluidinfo/2010/01/21/tickery-for-programmers/

Running Tickery
---------------

You'll find instructions on how to run your own version of Tickery in the
doc directory. If you have Sphinx (http://sphinx.pocoo.org) installed, you
can build the documentation by running 'make' in the doc dir and then
looking at doc/_build/html/index.html in your browser. If you don't have
Sphinx installed and don't want to install it, just look directly at the
doc/*.rst files.

Questions?
----------

For discussion of Tickery, we suggest you join the Fluidinfo users mailing
list at http://groups.google.com/group/fluiddb-users or join us in
#fluidinfo on irc.freenode.net Please say hi, we're very interested in
helping people to understand both Tickery and Fluidinfo.


Happy hacking!

The Fluidinfo team
[email protected]

tickery's People

Contributors

Stargazers

Watchers

Forkers

jdunck jkakar

tickery's Issues

Error pulling screenname out of pending job on shutdown

On Tickery shutdown when the user addition queue is not empty, Tickery tries to print the still pending jobs. There's a small error following the move to the new dispatch queue. We have

        pending = yield self.rdq.stop()
        if pending:
            log.msg('Pending user additions canceled: %r' %
                    [p.screenname for p in pending])

and the shutdown error is:

      File "/home/terry/fluidinfo/src/tickery/tickery/adder.py", line 248, in close
        [p.screenname for p in pending])
    exceptions.AttributeError: 'Job' object has no attribute 'screenname'

The Job items that come back from rdq.stop() have a jobarg in them, and we should be looking in there.

Calling cancel on a user from the admin interface raises an error

When I try to cancel a user addition via the admin interface, I get this error:

"unsupported operand type(s) for +: 'set' and 'list'

That's being sent back to the client and not printed with a traceback, so it may not be entirely obvious where the error is.

Factor out RetryingCall to use the newly packaged version

There is now a package called txretry containing the RetryingCall class. Use it.

Add priorities to user addition

We should have 3 different priorities: interactive use (medium), admin direct add of a user (high), admin bulk add (low). This will allow us to bulk add users without interfering with interactive use by regular people, and will allow us to add someone directly with high priority, jumping them to the head of the queue. These priorities could ideally be set from the admin interface, but let's not try to do that in this branch.

Use the /values endpoint

Tickery doesn't use /values because it didn't exist at the time and then it took a long time for it to get added to txFluidDB. So it has some inefficiencies (like adding the additional 3 or so Twitter tags in several calls instead of one). Let's speed that up.

fluidinfo / tickery Goto Github PK

tickery's Introduction

tickery's People

Contributors

Stargazers

Watchers

Forkers

tickery's Issues

Error pulling screenname out of pending job on shutdown

Calling cancel on a user from the admin interface raises an error

Factor out RetryingCall to use the newly packaged version

Add priorities to user addition

Use the /values endpoint

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent