[object Object] spacegauch0

JSON API

There are two JSON API styles:

The ID Style
The URL Style

The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.

The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

Unfollow everyone on twitter.com

By @foldleft.bsky.social, see also Unfollow everyone on bsky.app.

Go to https://twitter.com/YOUR_USER_NAME/following
Open the Developer Console. (COMMAND+ALT+I on Mac)
Paste this into the Developer Console and run it

// Unfollow everyone on twitter.com, by Jamie Mason (https://twitter.com/fold_left)

Background

Security in a single CouchDB can only be set up to do either:

Everyone can read/write everything (admin party)
Everyone can read, some can write
Some can read everything, and those same people can write everything

So in the very common situation where you want user data to be private, the current best practice is to give every user a database. This sounds nuts at first, but it turns out that databases are cheap in CouchDB; Cloudant boasts that 100k databases in a single Couch is not uncommon (source).

	Server:

	iMac
	Mac10,1
	Intel Core 2 Duo
	3,06 GHz

	Cache L2: 3 MB
	RAM: 8 GB
	bus: 1,07 GHz

	#!/usr/bin/ruby
	# Create display override file to force Mac OS X to use RGB mode for Display
	# see http://embdev.net/topic/284710

	require 'base64'

	data=`ioreg -l -d0 -w 0 -r -c AppleDisplay`

	edids=data.scan(/IODisplayEDID.*?<([a-z0-9]+)>/i).flatten
	vendorids=data.scan(/DisplayVendorID.*?([0-9]+)/i).flatten

	set :application, '<APP_NAME>'
	set :repo_url, "<git@PATH/REPO.git>"

	# ask :branch, proc { `git rev-parse --abbrev-ref HEAD`.chomp }

	set :deploy_to, "/home/deploy/rails/<APP_NAME>"
	# set :scm, :git

	set :format, :pretty
	set :log_level, :debug

	set :stage, :production

	# Simple Role Syntax
	# ==================
	# Supports bulk-adding hosts to roles, the primary
	# server in each group is considered to be the first
	# unless any hosts have the primary property set.
	role :app, %w{[email protected]}
	role :web, %w{[email protected]}
	role :db, %w{[email protected]}

	require 'mina/bundler'
	require 'mina/rails'
	require 'mina/git'
	require 'mina/rvm'
	require 'mina_sidekiq/tasks'

	set :rails_env, 'production'
	set :domain, 'YOUR_IP_OR_DOMAIN'
	set :deploy_to, "/home/rails/#{rails_env}"
	set :repository, '[email protected]:fousa/<YOUR_REPOSITORY>.git'

	unbind C-b
	set-option -g prefix `
	bind ` send-prefix