TL;DR:
- The design of both search and recommendations is to find and filter information
- Search is a "recommendation with a null query"
- Search is "I want this", recommendations is "you might like this"
TL;DR:
This page describes some ideas I've tinkered with in the last year or so. They are by no means complete. I also don't consider this to be a concrete proposal. I do hope this piece can serve to jumpstart some discussion about how Athens could become a platform for more than just storing information.
I've drawn on several ideas and tools developed by other people:
Ever wanted to delete all your likes/favorites from Twitter but only found broken/expensive tools? You are in the right place.
setInterval(() => {
for (const d of document.querySelectorAll('div[data-testid="unlike"]')) {
d.click()
}
=begin | |
Pocket Export.rb | |
My first 'real' Ruby script (hello world)! | |
More info here: http://blog.ctis.me/2015/12/archiving-your-pocket-articles-with-ruby.html | |
DEPENDENCIES: | |
pocket_export requires the following gems: | |
curb | |
nokogiri | |
#!/usr/bin/env python | |
#-*- coding: utf-8 -*- | |
# RescueTime Data Exporter | |
# Dan Nixon | |
# 18/09/2011 | |
import urllib | |
apiKey = "API_KEY" |
Driver: | |
-Write the code according to the navigator's specification | |
-Listen intently to the navigators instructions | |
-Ask questions wherever there is a lack of clarity | |
-Offer alternative solutions if you disagree with the navigator | |
-Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on | |
-Make sure code is clean | |
-Own the computer / keyboard | |
-Ignore larger issues and focus on the task at hand | |
-Trust the navigator - ultimately the navigator has the final say in what is written |