boldewyn / bookmarks Goto Github PK

On creating new bookmarks, and when DELICIOUS_AUTH === True, fetch tag suggestions from Delicious.

The bookmarks should be filterable and should be re-paginated on the fly.

When one clicks on a tag in the tag cloud, it should add to the already used tags. Tag filter removal is implemented, so there is always a way back, but we have currently no way forward.

We need to implement proper pagination for search.

The plugin is almost written, but we have to sort out the "Twitter OAuth Consumer Secret in Open Source app" issue.

The base is laid out with consistent use of __(), but we need to implement the catalog selection and lookup.

This is for all convenience, statistics, Twitter plugin, and because all link shorteners want an API key.

Structure: http://domain/path/ or http://domain/path/-

Should the ID be the numeric db row ID? Should we change the db scheme to make the ID alnum?

Do it.

Soemthing goes wrong when trying to convert the SimpleXML element to an array of attributes.

http://www.bibsonomy.org/help/doc/api.html

https://gforge.cs.uni-kassel.de/frs/download.php/26/bibsonomy-client-php.zip

This may be hosted separately 'cause of the library being LGPL'ed.

CRC32 has a too large possibility for collisions.

We could use pack(index) . substring(crc32(url)), which is still acceptably random enough to not be guessed.

The templates to generate those are missing yet.

The Validator at W3C shows some issues, missing mandatory elements, ...

http://developers.digg.com/toolkits

The PHP toolkit needs a gazillion others from PEAR.

Also we have to sort out how to embed an API key.

Many requests would better be intercepted and presented in a (modal) window, e.g., sharing.

Currently, results don't paginate but are simply cut off.

When creating a new bookmark, show an autosuggestion list of already used tags. (This is different from #3, because it works entirely on own data.)

It would be cool, if an installation of Bookmarks could follow a second one and display the most recent bookmarks in a separate view (or on the home screen).

It should be compatible to the Delicious API (like Pinboard does it).

On import delete bookmarks, that were deleted in the external service. Make this configurable.

For this to work we must track, which URL was imported from where, and check if it's gone on new import. It gets nasty, when a user imports from more than one source.

This is low prio and assumably a WONTFIX, especially since we have the functionality already the other way round.

When / is requested, and index.php is the default index page, get_script_path() has no means to decide between mod_rewrite-solution and PATH_INFO-solution.

When bookmarking, fetching a snapshot of the bookmarked page would be useful.

We can tell people to "recycle" their Delicious ones, but we should also offer an own, on the help page with proper Host set.

They just released their API. However, it seems to have the same issues as Twitter, namely disclosure of the OAuth secret.

Assume you import from Delicious, but have also a Bibsonomy account. There is no easy possibility to sync both services, i.e., to bulk-upload the bookmarks from Delicious to Bibsonomy.