Egeste.NET

A theoretically complete list of all zipcar ingress passcodes

Egeste — Sun, 03 Feb 2013 18:38:17 +0000

107NY3,
108NY3,
109NY3,
110NY3,
111NY3,
112NY3,
113NY3,
114NY3,
115NY3,
116NY3,
117NY3,
118NY3,
119NY3,
120NY3,
121NY3,
122NY3,
123NY3,
124NY3,
125NY3,
126NY3,
127NY3,
128NY3,
129NY3,
130NY3,
131NY3,
132NY3,
133NY3,
134NY3,
135NY3,
136NY3,
137NY3,
138NY3,
139NY3,
140NY3,
141NY3,
142NY3,
143NY3,
144NY3,
145NY3,
146NY3,
147NY3,
148NY3,
149NY3,
150NY3,
151NY3,
152NY3,
153NY3,
154NY3,
155NY3,
156NY3,
157NY3,
158NY3,
159NY3,
160NY3,
161NY3,
162NY3,
163NY3,
164NY3,
165NY3,
166NY3,
167NY3,
168NY3,
169NY3,
170NY3,
171NY3,
172NY3,
173NY3,
174NY3,
175NY3,
290TCR,
291TCR,
292TCR,
293TCR,
294TCR,
295TCR,
296TCR,
297TCR,
298TCR,
299TCR,
300TCR,
301TCR,
302TCR,
303TCR,
304TCR,
305TCR,
306TCR,
307TCR,
308TCR,
309TCR,
310TCR,
311TCR,
312TCR,
313TCR,
314TCR,
315TCR,
316TCR,
317TCR,
318TCR,
319TCR,
320TCR,
321TCR,
322TCR,
323TCR,
324TCR,
325TCR,
326TCR,
ADU3492,
ADU3493,
ADU3494,
ADU3495,
ADU3496,
ADU3497,
ADU3498,
ADU3499,
ADU3500,
ADU3501,
ADU3502,
ADU3503,
ADU3504,
ADU3505,
ADU3506,
ADU3507,
ADU3508,
ADU3509,
ADU3510,
ADU3511,
ADU3512,
ADU3513,
ADU3514,
ADU3515,
ADU3516,
FMN7278,
FMN7279,
FMN7280,
FMN7281,
FMN7282,
FMN7283,
FMN7284,
FMN7285,
FMN7286,
FMN7287,
FMN7288,
FMN7289,
FMN7290,
FMN7291,
FMN7292,
FMN7293,
FMN7294,
FMN7295,
FMN7296,
FMN7297,
FMN7298,
FMN7299,
FMN7300,
FMN7301,
FMN7302,
FMN7303,
FMN7304,
FMN7305,
FMN7306,
FMN7307,
FMN7308,
FMN7309,
FMN7310,
FMN7311,
FMN7312,
FMN7313,
FMN7314,
FMN7315,
FMN7316,
FMN7317,
FMN7318,
FMN7319,
FMN7320,
FMN7321,
FMN7322,
FMN7323,
FMN7324,
FMN7325,
FMN7326,
FMN7327,
FMN7328,
FMN7329,
FMN7330,
FMN7331,
FMN7332,
FMN7333,
FMN7334,
FMN7335,
FMN7336,
FMN7337,
FMN7338,
FMN7339,
FMN7340,
FMN7341,
FMN7342,
FMN7343,
FMN7344,
FMN7345,
FMN7346,
FMN7347,
FMN7348,
FMN7349,
FMN7350,
FMN7351,
FMN7352,
FMN7353,
FMN7354,
FMN7355,
FMN7356,
FMN7357,
FMN7358,
FMN7359,
FMN7360,
FMN7361,
FMN7362,
FMN7363,
FMN7364,
FMN7365,
FMN7366,
FMN7367,
FMN7368,
FMN7369,
FMN7370,
FMN7371,
FMN7372,
FMN7373,
FMN7374,
FMN7375,
FMN7376,
FMN7377,
FMN7378,
FMN7379,
FMN7380,
FMN7381,
FMN7382,
FMN7383,
FMN7384,
FMN7385,
FMN7386,
FMN7387,
FMN7388,
FMN7389,
FMN7390,
FMN7391,
FMN7392,
FMN7393,
FMN7394,
FMN7395,
FMN7396,
FMN7397,
FMN7398,
FMN7399,
FMN7400,
FMN7401,
FMN7402,
FMN7403,
FMN7404,
FMN7405,
FMN7406,
FMN7407,
FMN7408,
FMN7409,
FMN7410,
FMN7411,
FMN7412,
FMN7413,
FMN7414,
FMN7415,
FMN7416,
FMN7417,
FMN7418,
FMN7419,
FMN7420,
FMN7421,
FMN7422,
FMN7423,
FMN7424,
FMN7425,
FMN7426,
FMN7427,
FMN7428,
FMN7429,
FMN7430,
FMN7431,
FMN7432,
FMN7433,
FMN7434,
FMN7435,
FMN7436,
FMN7437,
FMN7438,
FMN7439,
FMN7440,
FMN7441,
FMN7442,
FMN7443,
FMN7444,
FMN7445,
FMN7446,
FMN7447,
FMN7448,
FMN7449,
FMN7450,
FMN7451,
FMN7452,
FMN7453,
FMN7454,
FMN7455,
FMN7456,
FMN7457,
FMN7458,
FMN7459,
FMN7460,
FMN7461,
FMN7462,
FMN7463,
FMN7464,
FMN7465,
FMN7466,
FMN7467,
FMN7468,
FMN7469,
FMN7470,
FMN7471,
FMN7472,
FMN7473,
FMN7474,
FMN7475,
FMN7476,
FMN7477,
FMN7478,
FMN7479,
FMN7480,
FMN7481,
FMN7482,
FMN7483,
FMN7484,
FMN7485,
FMN7486,
FMN7487,
FMN7488,
FMN7489,
FMN7490,
FMN7491,
FMN7492,
FMN7493,
FMN7494,
FMN7495,
FMN7496,
FMN7497,
FMN7498,
FMN7499,
FMN7500,
FMN7501,
FMN7502,
FMN7503,
FMN7504,
FMN7505,
FMN7506,
FMN7507,
FMN7508,
FMN7509,
FMN7510,
FMN7511,
FMN7512,
FMN7513,
FMN7514,
FMN7515,
FMN7516,
FMN7517,
FMN7518,
FMN7519,
FMN7520,
FMN7521,
FMN7522,
FMN7523,
FMN7524,
FMN7525,
FMN7526,
FMN7527,
FMN7528,
FMN7529,
FMN7530,
FMN7531,
FMN7532,
FMN7533,
FMN7534,
FMN7535,
FMN7536,
FMN7537,
FMN7538,
FMN7539,
FMN7540,
FMN7541,
FMN7542,
FMN7543,
FMN7544,
FMN7545,
FMN7546,
FMN7547,
FMN7548,
FMN7549,
FMN7550,
FMN7551,
FMN7552,
FMN7553,
FMN7554,
FMN7555,
FMN7556,
FMN7557,
FMN7558,
FMN7559,
FMN7560,
FMN7561,
FMN7562,
FMN7563,
FMN7564,
FMN7565,
FMN7566,
FMN7567,
FMN7568,
FMN7569,
FMN7570,
FMN7571,
FMN7572,
FMN7573,
FMN7574,
FMN7575,
FMN7576,
FMN7577,
FMN7578,
FMN7579,
FMN7580,
FMN7581,
FMN7582,
FMN7583,
FMN7584,
FMN7585,
FMN7586,
FMN7587,
FMN7588,
FMN7589,
FMN7590,
FMN7591,
FMN7592,
FMN7593,
FMN7594,
FMN7595,
FMN7596,
FMN7597,
FMN7598,
FMN7599,
FMN7600,
FYD4500,
FYD4501,
FYD4502,
FYD4503,
FYD4504,
FYD4505,
FYD4506,
FYD4507,
FYD4508,
FYD4509,
FYD4510,
FYD4511,
FYD4512,
FYD4513,
FYD4514,
FYD4515,
FYD4516,
FYD4517,
FYD4518,
FYD4519,
FYD4520,
FYD4521,
FYD4522,
FYD4523,
FYD4524,
FYD4525,
FYD4526,
FYD4527,
FYD4528,
FYD4529,
FYD4530,
FYD4531,
FYD4532,
FYD4533,
FYD4534,
FYD4535,
FYD4536,
FYD4537,
FYD4538,
FYD4539,
FYD4540,
FYD4541,
FYD4542,
FYD4543,
FYD4544,
FYD4545,
FYD4546,
FYD4547,
FYD4548,
FYD4549,
FYD4550,
FYD4551,
FYD4552,
FYD4553,
FYD4554,
FYD4555,
FYD4556,
FYD4557,
FYD4558,
FYD4559,
FYD4560,
FYD4561,
FYD4562,
FYD4563,
FYD4564,
FYD4565,
FYD4566,
FYD4567,
FYD4568,
FYD4569,
FYD4570,
FYD4571,
FYD4572,
FYD4573,
FYD4574,
FYD4575,
FYD4576,
FYD4577,
FYD4578,
FYD4579,
FYD4580,
FYD4581,
FYD4582,
FYD4583,
FYD4584,
FYD4585,
FYD4586,
FYD4587,
FYD4588,
FYD4589,
FYD4590,
FYD4591,
FYD4592,
FYD4593,
FYD4594,
FYD4595,
FYD4596,
FYD4597,
FYD4598,
FYD4599,
FYD4600,
FYD4601,
FYD4602,
FYD4603,
FYD4604,
FYD4605,
FYD4606,
FYD4607,
FYD4608,
FYD4609,
FYD4610,
FYD4611,
FYD4612,
FYD4613,
FYD4614,
FYD4615,
FYD4616,
FYD4617,
FYD4618,
FYD4619,
FYD4620,
FYD4621,
FYD4622,
FYD4623,
FYD4624,
FYD4625,
FYD4626,
FYD4627,
FYD4628,
FYD4629,
FYD4630,
FYD4631,
FYD4632,
FYD4633,
FYD4634,
FYD4635,
FYD4636,
FYD4637,
FYD4638,
FYD4639,
FYD4640,
FYD4641,
FYD4642,
FYD4643,
FYD4644,
FYD4645,
FYD4646,
FYD4647,
FYD4648,
FYD4649,
FYD4650,
FYD4651,
FYD4652,
FYD4653,
FYD4654,
FYD4655,
FYD4656,
FYD4657,
FYD4658,
FYD4659,
FYD4660,
FYD4661,
FYD4662,
FYD4663,
FYD4664,
FYD4665,
FYD4666,
FYD4667,
FYD4668,
FYD4669,
FYD4670,
FYD4671,
FYD4672,
FYD4673,
FYD4674,
FYD4675,
FYD4676,
FYD4677,
FYD4678,
FYD4679,
FYD4680,
FYD4681,
FYD4682,
FYD4683,
FYD4684,
FYD4685,
FYD4686,
FYD4687,
FYD4688,
FYD4689,
FYD4690,
FYD4691,
FYD4692,
FYD4693,
FYD4694,
FYD4695,
FYD4696,
FYD4697,
FYD4698,
FYD4699,
FYD4700,
FYD4701,
FYD4702,
FYD4703,
FYD4704,
FYD4705,
FYD4706,
FYD4707,
FYD4708,
FYD4709,
FYD4710,
FYD4711,
FYD4712,
FYD4713,
FYD4714,
FYD4715,
FYD4716,
FYD4717,
FYD4718,
FYD4719,
FYD4720,
FYD4721,
FYD4722,
FYD4723,
FYD4724,
FYD4725,
FYD4726,
FYD4727,
FYD4728,
FYD4729,
FYD4730,
FYD4731,
FYD4732,
FYD4733,
FYD4734,
FYD4735,
FYD4736,
FYD4737,
FYD4738,
FYD4739,
FYD4740,
FYD4741,
FYD4742,
FYD4743,
FYD4744,
FYD4745,
FYD4746,
FYD4747,
FYD4748,
FYD4749,
FYD4750,
FYD4751,
FYD4752,
FYD4753,
FYD4754,
FYD4755,
FYD4756,
FYD4757,
FYD4758,
FYD4759,
FYD4760,
FYD4761,
FYD4762,
FYD4763,
FYD4764,
FYD4765,
FYD4766,
FYD4767,
FYD4768,
FYD4769,
FYD4770,
FYD4771,
FYD4772,
FYD4773,
FYD4774,
FYD4775,
FYD4776,
FYD4777,
FYD4778,
FYD4779,
FYD4780,
FYD4781,
FYD4782,
FYD4783,
FYD4784,
FYD4785,
FYD4786,
FYD4787,
FYD4788,
FYD4789,
FYD4790,
FYD4791,
FYD4792,
FYD4793,
FYD4794,
FYD4795,
FYD4796,
FYD4797,
FYD4798,
FYD4799,
FYD4800,
FYD4801,
FYD4802,
FYD4803,
FYD4804,
FYD4805,
FYD4806,
FYD4807,
FYD4808,
FYD4809,
FYD4810,
FYD4811,
FYD4812,
FYD4813,
FYD4814,
FYD4815,
FYD4816,
FYD4817,
FYD4818,
FYD4819,
FYD4820,
FYD4821,
FYD4822,
FYD4823,
FYD4824,
FYD4825,
FYD4975,
FYD4976,
FYD4977,
FYD4978,
FYD4979,
FYD4980,
FYD4981,
FYD4982,
FYD4983,
FYD4984,
FYD4985,
FYD4986,
FYD4987,
FYD4988,
FYD4989,
FYD4990,
FYD4991,
FYD4992,
FYD4993,
FYD4994,
FYD4995,
FYD4996,
FYD4997,
FYD4998,
FYD4999,
FYD5000,
FYD5001,
FYD5002,
FYD5003,
FYD5004,
FYD5005,
FYD5006,
FYD5007,
FYD5008,
FYD5009,
FYD5010,
FYD5011,
FYD5012,
FYD5013,
FYD5014,
FYD5015,
FYD5016,
FYD5017,
FYD5018,
FYD5019,
FYD5020,
FYD5021,
FYD5022,
FYD5023,
FYD5024,
FYD5025,
FYD5026,
FYD5027,
FYD5028,
FYD5029,
FYD5030,
FYD5031,
FYD5032,
FYD5033,
FYD5034,
FYD5035,
FYD5036,
FYD5037,
FYD5038,
FYD5039,
FYD5040,
FYD5041,
FYD5042,
FYD5043,
FYD5044,
FYD5045,
FYD5046,
FYD5047,
FYD5048,
FYD5049,
FYD5050,
FZG4650,
FZG4651,
FZG4652,
FZG4653,
FZG4654,
FZG4655,
FZG4656,
FZG4657,
FZG4658,
FZG4659,
FZG4660,
FZG4661,
FZG4662,
FZG4663,
FZG4664,
FZG4665,
FZG4666,
FZG4667,
FZG4668,
FZG4669,
FZG4670,
FZG4671,
FZG4672,
FZG4673,
FZG4674,
FZG4675,
FZG4676,
FZG4677,
FZG4678,
FZG4679,
FZG4680,
FZG4681,
FZG4682,
FZG4683,
FZG4684,
FZG4685,
FZG4686,
FZG4687,
FZG4688,
FZG4689,
FZG4690,
FZG4691,
FZG4692,
FZG4693,
FZG4694,
FZG4695,
FZG4696,
FZG4697,
FZG4698,
FZG4699,
FZG4700,
FZG4701,
FZG4702,
FZG4703,
FZG4704,
FZG4705,
FZG4706,
FZG4707,
FZG4708,
FZG4709,
FZG4710,
FZG4711,
FZG4712,
FZG4713,
FZG4714,
FZG4715,
FZG4716,
FZG4717,
FZG4718,
FZG4719,
FZG4720,
FZG4721,
FZG4722,
FZG4723,
FZG4724,
FZG4725,
FZG4726,
FZG4727,
FZG4728,
FZG4729,
FZG4730,
FZG4731,
FZG4732,
FZG4733,
FZG4734,
FZG4735,
FZG4736,
FZG4737,
FZG4738,
FZG4739,
FZG4740,
FZG4741,
FZG4742,
FZG4743,
FZG4744,
FZG4745,
FZG4746,
FZG4747,
FZG4748,
FZG4749,
FZG4750,
FZG4751,
FZG4752,
FZG4753,
FZG4754,
FZG4755,
FZG4756,
FZG4757,
FZG4758,
FZG4759,
FZG4760,
FZG4761,
FZG4762,
FZG4763,
FZG4764,
FZG4765,
FZG4766,
FZG4767,
FZG4768,
FZG4769,
FZG4770,
FZG4771,
FZG4772,
FZG4773,
FZG4774,
FZG4775,
FZG4776,
FZG4777,
FZG4778,
FZG4779,
FZG4780,
FZG4781,
FZG4782,
FZG4783,
FZG4784,
FZG4785,
FZG4786,
FZG4787,
FZG4788,
FZG4789,
FZG4790,
FZG4791,
FZG4792,
FZG4793,
FZG4794,
FZG4795,
FZG4796,
FZG4797,
FZG4798,
FZG4799,
FZG4800,
FZG4801,
FZG4802,
FZG4803,
FZG4804,
FZG4805,
FZG4806,
FZG4807,
FZG4808,
FZG4809,
FZG4810,
FZG4811,
FZG4812,
FZG4813,
FZG4814,
FZG4815,
FZG4816,
FZG4817,
FZG4818,
FZG4819,
FZG4820,
FZG4821,
FZG4822,
FZG4823,
FZG4824,
FZG4825,
FZG4826,
FZG4827,
FZG4828,
FZG4829,
FZG4830,
FZG4831,
FZG4832,
FZG4833,
FZG4834,
FZG4835,
FZG4836,
FZG4837,
FZG4838,
FZG4839,
FZG4840,
FZG4841,
FZG4842,
FZG4843,
FZG4844,
FZG4845,
FZG4846,
FZG4847,
FZG4848,
FZG4849,
FZG4850,
FZG4851,
FZG4852,
FZG4853,
FZG4854,
FZG4855,
FZG4856,
FZG4857,
FZG4858,
FZG4859,
FZG4860,
FZG4861,
FZG4862,
FZG4863,
FZG4864,
FZG4865,
FZG4866,
FZG4867,
FZG4868,
FZG4869,
FZG4870,
FZG4871,
FZG4872,
FZG4873,
FZG4874,
FZG4875,
FZG4876,
FZG4877,
FZG4878,
FZG4879,
FZG4880,
FZG4881,
FZG4882,
FZG4883,
FZG4884,
FZG4885,
FZG4886,
FZG4887,
FZG4888,
FZG4889,
FZG4890,
FZG4891,
FZG4892,
FZG4893,
FZG4894,
FZG4895,
FZG4896,
FZG4897,
FZG4898,
FZG4899,
FZG4900,
FZG4901,
FZG4902,
FZG4903,
FZG4904,
FZG4905,
FZG4906,
FZG4907,
FZG4908,
FZG4909,
FZG4910,
FZG4911,
FZG4912,
FZG4913,
FZG4914,
FZG4915,
FZG4916,
FZG4917,
FZG4918,
FZG4919,
FZG4920,
FZG4921,
FZG4922,
FZG4923,
FZG4924,
FZG4925,
FZG4926,
FZG4927,
FZG4928,
FZG4929,
FZG4930,
FZG4931,
FZG4932,
FZG4933,
FZG4934,
FZG4935,
FZG4936,
FZG4937,
FZG4938,
FZG4939,
FZG4940,
FZG4941,
FZG4942,
FZG4943,
FZG4944,
FZG4945,
FZG4946,
FZG4947,
FZG4948,
FZG4949,
FZG4950,
FZG4951,
FZG4952,
FZG4953,
FZG4954,
FZG4955,
FZG4956,
FZG4957,
FZG4958,
FZG4959,
FZG4960,
FZG4961,
FZG4962,
FZG4963,
FZG4964,
FZG4965,
FZG4966,
FZG4967,
FZG4968,
FZG4969,
FZG4970,
GAH7940,
GAH7941,
GAH7942,
GAH7943,
GAH7944,
GAH7945,
GAH7946,
GAH7947,
GAH7948,
GAH7949,
GAH7950,
GAH7951,
GAH7952,
GAH7953,
GAH7954,
GAH7955,
GAH7956,
GAH7957,
GAH7958,
GAH7959,
GAH7960,
GAH7961,
GAH7962,
GAH7963,
GAH7964,
GAH7965,
GAH7966,
GAH7967,
GAH7968,
GAH7969,
GAH7970,
GAH7971,
GAH7972,
GAH7973,
GAH7974,
GAH7975,
GAH7976,
GAH7977,
GAH7978,
GAH7979,
GAH7980,
GAH7981,
GAH7982,
GAH7983,
GAH7984,
GAH7985,
GAH7986,
GAH7987,
GAH7988,
GAH7989,
GAH7990,
GAH7991,
GAH7992,
GAH7993,
GAH7994,
GAH7995,
GAH7996,
GAH7997,
GAH7998,
GAH7999,
GAH8000,
GAH8001,
GAH8002,
GAH8003,
GAH8004,
GAH8005,
GAH8006,
GAH8007,
GAH8008,
GAH8009,
GAH8010,
GAH8011,
GAH8012,
GAH8013,
GAH8014,
GAH8015,
GAH8016,
GAH8017,
GAH8018,
GAH8019,
GAH8020,
GAH8021,
GAH8022,
GAH8023,
GAH8024,
GAH8025,
GAH8026,
GAH8027,
GAH8028,
GAH8029,
GAH8030,
GAH8031,
GAH8032,
GAH8033,
GAH8034,
GAH8035,
GAH8036,
GAH8037,
GAH8038,
GAH8039,
GAH8040,
GAH8041,
GAH8042,
GAH8043,
GAH8044,
GAH8045,
GAH8046,
GAH8047,
GAH8048,
GAH8049,
GAH8050,
GAH8051,
GAH8052,
GAH8053,
GAH8054,
GAH8055,
GAH8056,
GAH8057,
GAH8058,
GAH8059,
GAH8060,
GAH8061,
GAH8062,
GAH8063,
GAH8064,
GAH8065,
GAH8066,
GAH8067,
GAH8068,
GAH8069,
GAH8070,
GAH8071,
GAH8072,
GAH8073,
GAH8074,
GAH8075,
GAH8076,
GAH8077,
GAH8078,
GAH8079,
GAH8080,
GAH8081,
GAH8082,
GAH8083,
GAH8084,
GAH8085,
GAH8086,
GAH8087,
GAH8088,
GAH8089,
GAH8090,
GAH8091,
GAH8092,
GAH8093,
GAH8094,
GAH8095,
GAH8096,
GAH8097,
GAH8098,
GAH8099,
GAH8100,
GAH8101,
GAH8102,
GAH8103,
GAH8104,
GAH8105,
GAH8106,
GAH8107,
GAH8108,
GAH8109,
GAH8110,
GAH8111,
GAH8112,
GAH8113,
GAH8114,
GAH8115,
GAH8116,
GAH8117,
GAH8118,
GAH8119,
GAH8120,
GAH8121,
GAH8122,
GAH8123,
GAH8124,
GAH8125,
GAH8126,
GAH8127,
GAH8128,
GAH8129,
GAH8130,
GAH8131,
GAH8132,
GAH8133,
GAH8134,
GAH8135,
GAH8136,
GAH8137,
GAH8138,
GAH8139,
HZZ7680,
HZZ7681,
HZZ7682,
HZZ7683,
HZZ7684,
HZZ7685,
HZZ7686,
HZZ7687,
HZZ7688,
HZZ7689,
HZZ7690,
HZZ7691,
HZZ7692,
HZZ7693,
HZZ7694,
HZZ7695,
HZZ7696,
HZZ7697,
HZZ7698,
HZZ7699,
6SNU690,
6SNU691,
6SNU692,
6SNU693,
6SNU694,
6SNU695,
6SNU696,
6SNU697,
6SNU698,
6SNU699,
6SNU700,
6SNU701,
6SNU702,
6SNU703,
6SNU704,
6SNU705,
6SNU706,
6SNU707,
6SNU708,
6SNU709,
6SNU710,
6SNU711,
6SNU712,
6SNU713,
6SNU714,
6SNU715,
6SNU716,
6SNU717,
6SNU718,
6SNU719,
6SNU720,
6SNU721,
6SNU722,
6SNU723,
6SNU724,
6SNU725,
6TEE314,
6TEE315,
6TEE316,
6TEE317,
6TEE318,
6TEE319,
6TEE320,
6TEE321,
6TEE322,
6TEE323,
6TEE324,
6TEE325,
6TEE326,
6TEE327,
6TEE328,
6TEE329,
6TEE330,
6TEE331,
6TEE332,
6TEE333,
6TEE334

Let’s bump Gangnam Style to 1 billion views

Egeste — Wed, 19 Dec 2012 04:24:36 +0000

This is a quick and dirty hack I threw together to loop Gangnam Style. Simply embed the code from the gist anywhere in your document body to get instant oppa. An elegant solution would implement youtube’s player api, but who has time for that?

Backbone Pattern: Multi-state views

Egeste — Wed, 24 Oct 2012 17:41:29 +0000

Views that have more than one state can be complex, and if not written correctly can lead to huge unmanageable blocks of logic attempting to determine exactly what state a view is in. If you don’t know what I mean by a “multi-state view”, consider the following requirements:

Create a page with a visual header bar that has 2 options: list view, and tree view
List view is selected by default
When the user selects the list view option, the content underneath the header displays a list view of all items, and the header updates to indicate that the list view is selected
When the user selects the tree view option, the content underneath the header displays a tree view of all items, and the header updates to indicate that the tree view is selected
When the user selects an item from the list or tree view, the content underneath the header displays details about the selected item, and the header updates to indicate that no view is selected

Right away, we’re talking about a pretty complex set of requirements. How can we make sure that we’re always showing the right thing in both the content area and in the header view? What if there are other views on the page that care about the state of the content view? First let’s take a look at one possible approach.

Note: we’re scoping these sub views within a closure. See: Backbone Pattern: Closure-scoped sub views

(function() {
  var HeaderView = Backbone.View.extend({
    id: 'header',
    render: function() {/* ... */},
    setView: function(view) {
      this.$('.option.list').toggleClass('selected', view === 'list')
      this.$('.option.tree').toggleClass('selected', view === 'tree')
    }
  })
 
  var RowView = Backbone.View.extend({
    render: function() {/* render a row */}
  })
 
  var ListView = Backbone.View.extend({
    render: function() {/* render a bunch of rows */}
  })
 
  var TreeView = Backbone.View.extend({
    render: function() {/* render a bunch of rows differently */}
  })
 
  var ItemView = Backbone.View.extend({
    render: function() {/* ... */}
  })
 
  exports.PageView = Backbone.View.extend({
    events: {
      'click #header.list': '_listView',
      'click #header.tree': '_treeView',
      'click .row': '_itemView'
    },
    initialize: function() {
      this.createSubViews()
    },
    createSubViews: function() {
      this.header = new HeaderView
      this.list = new ListView
      this.tree = new TreeView
      this.item = new ItemView
    },
    render: function() {
      this._listView()
      return this
    },
    _listView: function() {
      this.list.render().$el.show()
      this.tree.$el.hide()
      this.item.$el.hide()
      this.header.setView('list')
    },
    _treeView: function() {
      this.list.$el.hide()
      this.tree.$el.render().show()
      this.item.$el.hide()
      this.header.setView('tree')
    },
    _itemView: function(event) {
      var model = $(event.target).data('model')
      this.list.$el.hide()
      this.tree.$el.hide()
      this.item.model = model
      this.item.$el.render().show()
      this.header.setView()
    }
  })
})();

Phew! That’s a lot of difficult to maintain, repetitious, anti-pattern code. Let’s break down what exactly is wrong with this example.

The events hash for the page view is attaching events to elements that belong to subviews. This is a classic backbone code smell.
The page view is reaching into the sub views and modifying their elements.
The page view is reaching into the sub views and modifying its internal state.

What do all these issues have in common? They all put the page view in a position of ultimate responsibility. It’s not the job of the page view to manage the internal state of every sub-view attached to it, and the repetition of code is a side effect. Additionally, this code is unnecessarily complex, making it prone to bugs, and more difficult to debug. I just wrote it, and I’m not even sure if it would work… Let’s try something else.

Note: We’re chaining update functions. See: Backbone Pattern: Chain-able update functions

(function() {
  // Create a new instance of an extended backbone model with some defaults
  var viewState = new (Backbone.Model.extend({
    defaults: {
      state: 'list',
      model: undefined
    }
  }))
 
  // Create a header view that presents and modifies the state attribute of
  // the viewState model
  var HeaderView = Backbone.View.extend({
    events: {
      'click .list': '_list',
      'click .tree': '_tree'
    },
    initialize: function() {
      viewState.on('change:state', this.updateOptions, this)
    },
    render: function() {
      this.$el.html(/* ... */)
      return this.updateOptions()
    },
    updateOptions: function() {
      var state = viewState.get('state')
      this.$('.list').toggleClass('selected', state === 'list')
      this.$('.tree').toggleClass('selected', state === 'tree')
    },
    _list: function() {
      viewState.set('state', 'list')
    },
    _tree: function() {
      viewState.set('state', 'tree')
    }
  })
 
  // Create a view to present a row for an item and passes its model to
  // viewState if clicked
  var RowView = Backbone.View.extend({
    events: { 'click': '_detail' },
    render: function() {/* render a row */},
    _detail: function() {
      viewState.set({
        state: 'detail',
        model: this.model
      })
    }
  })
 
  var DetailView = Backbone.View.extend({
    render: function() {/* render detail for a row */}
  })
 
  var ListView = Backbone.View.extend({
    render: function() {/* render a bunch of rows */}
  })
 
  var TreeView = Backbone.View.extend({
    render: function() {/* render a bunch of rows differently */}
  })
 
  exports.PageView = Backbone.View.extend({
    initialize: function() {
      // Add event listeners to specific attributes of the viewState
      viewState.on('change:state', this.updateState, this)
      this.createSubViews()
    },
    createSubViews: function() {
      this.header = new HeaderView
      this.list = new ListView
      this.tree = new TreeView
    },
    render: function() {
      this.$el.html(/* ... */)
      // Attach the header to its anchor and render it
      this.header.setElement(this.$('.header')).render()
      // Attach the list and tree views to their anchor
      this.list.setElement(this.$('.content'))
      this.tree.setElement(this.$('.content'))
      // Chain the updateState function
      return this.updateState()
    },
    updateState: function() {
      // Render the subviews based on state attribute of the viewState model
      // When the sub-view gets rendered, it replaces its contents with new
      // elements. Theoretically, we can attach an infinite number of views to
      // a single element in this way, allowing us to have an unlimited number
      // of possible view states
      var state = viewState.get('state')
      state === 'list' && this.list.render()
      state === 'tree' && this.tree.render()
      if (state === 'detail') {
        new DetailView({
          model: viewState.get('model'),
          el: this.$('.content')
        }).render()
      }
      return this
    }
  })
})();

What this has accomplished is actually significant:

We now have a model that represents the state of the view in addition to the model it’s displaying (if we’re looking at a detail view).
There is proper delegation of responsibility (no view is modifying the internal state or dom of another view).
While it may not look like it because this is an example, we’ve actually reduced both the amount of code and the code complexity.
We’ve opened up our code to extensibility by making it trivial to add new view states, or remove existing ones.

This pattern if perfect for any view where you’re presenting multiple sub views in the same space on the screen, such as paginated and tabbed views. Please feel free to comment with questions, comments, errata, etc.

Backbone Pattern: Chain-able update functions

Egeste — Wed, 24 Oct 2012 05:55:53 +0000

Frequently, when you’re writing a complex view in Backbone.js, you need to update some aspect of the view due to a model change. However, this can get hairy when you have complex dom with javascript components, and simply re-rendering the view can create unusual or undesirable behavior in the view. Example:

var SomeView = Backbone.View.extend({
  initialize: function() {
    this.model.on('change', this.render, this)
  },
  render: function() {
    this.$el.html(/* ... */)
    this.$('input.foo')
      .val(this.model.get('foo'))
      .datepicker(/* ... */)
    this.$('.bar').text(this.model.get('bar'))
    return this
  }
})

In this example we have a text input with the css class “foo”. This input is acting as an anchor for a date picker component. Assume that the date picker has a callback that changes the model’s foo attribute when a date is selected. In the event that the user focuses on this input field, the date picker component will display, allowing the user to select a date, and therefor alter the state of the model. When this occurs, the view will re-render, replacing the entire view’s dom structure, including the foo input field. Depending on the implementation details of date picker component, it may end up on the screen forever awaiting some event from the original foo input field. Even if this is not the case and the component doesn’t end up in some anomalous state, you’re still doing more work than is necessary by re-rendering the entire view and initializing new components.

How do you render a view to display all the information in its model, and only update specific elements as the model’s attributes change?

The pattern I discovered was to create a series of chain-able update functions for the affected model attributes.
Example:

var SomeView = Backbone.View.extend({
  initialize: function() {
    this.model
      .on('change:foo', this.updateFoo, this)
      .on('change:bar', this.updateBar, this)
  },
  render: function() {
    this.$el.html(/* ... */)
    this.$('input.foo').datepicker(/* ... */)
    return this
      .updateFoo()
      .updateBar()
  },
  updateFoo: function() {
    this.$('input.foo').val(this.model.get('foo'))
    return this
  },
  updateBar: function() {
    this.$('.bar').text(this.model.get('bar'))
    return this
  }
})

In the event that a model attribute changes that has implications for some other portion of the view, you can chain the updates within each other. For example, if foo changing means that something in bar’s update function should execute, you could write this:

var SomeView = Backbone.View.extend({
  initialize: function() {
    this.model
      .on('change:foo', this.updateFoo, this)
      .on('change:bar', this.updateBar, this)
  },
  render: function() {
    this.$el.html(/* ... */)
    this.$('input.foo').datepicker(/* ... */)
    return this.updateFoo()
  },
  updateFoo: function() {
    this.$('input.foo').val(this.model.get('foo'))
    return this.updateBar()
  },
  updateBar: function() {
    this.$('.bar').text(this.model.get('bar'))
    return this
  }
})

Successfully using this pattern means:

You should only ever have to render a view once
You should only ever have to initialize view components once
Your view is always up to date with the model’s state
The only dom that gets touched is the dom relevant to specific model attributes
You will end up with lighter, smaller, more maintainable code by not needing to handle a ton of edge cases in your render function

Please feel free to comment with questions, comments, errata, etc.

Backbone Pattern: Closure-scoped sub views

Egeste — Sat, 20 Oct 2012 19:23:06 +0000

This pattern is really about keeping your namespaced objects free from unnecessary clutter. The concept is simple: if a sub-view is never used anywhere else, it serves no purpose being accessible from the global scope. Keeping the subview locally scoped within a closure keeps your globally accessible namespaced objects from bloating out of control. Consider the following scenario:

window.views = {}
window.views.Home = Backbone.View.extend({/* ... */})
window.views.HomeContent = Backbone.View.extend({/* ... */})
window.views.SearchField = Backbone.View.extend(/* ... */)
window.views.About = Backbone.View.extend({/* ... */})

We have an object in the global scope named views. Views is where we put all of our backbone views for various things, mostly complete page views and a handful of view components, etc. So let’s take a look at what the Home view might look like:

window.views.Home = Backbone.View.extend({
  initialize: function() {
    this.createSubViews()
  },
  createSubViews: function() {
    this.contentView = new window.views.HomeContent
    this.searchField = new window.views.SearchField
  },
  render: function() {
    this.$el.html(/* ... */)
    this.searchField.setElement(this.$('.search')).render()
    this.contentView.setElement(this.$('.content')).render()
    return this
  }
})

This is all well and good and will work just fine, but if you look at the list of views you’ll notice that the HomeContent view is only really relevant to the Home view. While it’s possible that the About view may want to have a search field it’s not at all likely that the About view is going to render the homepage content. The HomeContent view is superfluous in the top-level views namespace and collecting these subviews here over time will lead to massive bloat in this object. To solve this, simply scope sub-views into a closure with the parent view.

(function(views) {
  var Content = Backbone.View.extend(/* ... */) // this is locally scoped
  views.Home = Backbone.View.extend(/* ... */) // this is exported to window.views
})(window.views)

Locally scoping the views in this way serves two purposes. First, it keeps these non-reusable out of the top level object, and second it keeps code relevant to the parent view in the same file and easy to access/find. Using this strategy you should find that your code for these sub views is easier to maintain and more approachable by other developers. Please feel free to comment with questions, comments, errata, etc.

Migrating your turntable.fm playlist to plug.dj

Egeste — Sat, 08 Sep 2012 03:33:03 +0000

I discovered a service somewhat similar to turntable.fm called plug.dj and was delighted to discover that they offer the ability to import playlist files generated by (the now retired) ttTools. In my opinion, that kind of cross-service data freedom embodies the same hacker-ethos that inspired ttTools to begin with. So with that in mind, I wanted to make the export functionality available outside of ttTools and provide a step-by-step guide for those who wish to transfer their turntable.fm playlist over to plug.dj.

Export Playlist

Step By Step: How to root the Motorola I1

Egeste — Tue, 30 Aug 2011 14:36:23 +0000

One of my friends came to me and asked if I would help her root her Motorola I1. Always up to help friends liberate their devices, I told her I would, then set out on my google quest to find all the resources this process would require. As is usually the case with unpopular, niche, or older devices like the Motorola I1, there was a lot of non-working scripts and a hefty handful of misguidance. This article is intended to replace other articles on the subject. Hopefully, you found this article first and didn’t have to waste too much of your time messing around with the others. This article is accurate as of the date it was written. I can’t make any guarantees that the reptilian overlords at Motorola haven’t added some kind of horrible phone-bricking code to prevent this method.

Caution: You must know how to use the command line to do this. I provide no guarantees and cannot be held liable for any damage that may occur to your phone by following this guide. This is for informational purposes only.

Step 1. Install the android sdk
I won’t go into this in detail. There are maintained & updated instructions at http://developer.android.com/sdk/installing.html#Installing

Step 2. Enable USB debugging on your phone
An excerpt from: http://developer.android.com/guide/developing/device.html

Turn on “USB Debugging” on your device.
On the device, go to Settings > Applications > Development and enable USB debugging.

Once this is complete, plug your phone into your computer via your USB cable.

Step 3. Get the files
The files are available in .zip and .tgz archives here. You don’t need both. The tgz is there for convenience for those who prefer it. Once you have the archive, unzip it somewhere that’s easy to get to from a command line.

Step 4. Edit the install file
I was hoping to automate this step so you didnt have to do it manually, but unfortunately stock android (at least 1.5) does not have the gnu-utils necessary to do this – so you’ll have to do it by hand… Thankfully, it’s not a terribly difficult process.
In your local terminal (on your computer, not on the device), run the following command:

adb shell mount

You will see a bunch of output that looks something like this:

rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock10 /phx/cp yaffs2 rw 0 0
/dev/block/mtdblock18 /phx/cpb yaffs2 rw 0 0
/dev/block/mtdblock17 /phx/bp squashfs ro 0 0
/dev/block/mtdblock15 /phx/csd squashfs ro 0 0
/dev/block/mtdblock14 /phx/ue squashfs ro 0 0
/dev/block/mtdblock11 /phx/logger yaffs2 rw 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock12 /data/preload yaffs2 ro 0 0

I have highlighted the line you are looking for in this example. You want to find the line that shows the device that is mounted to /system. In this example, /dev/block/mtdblock7 is mounted to /system. Yours may be different, hence why we check to see what it is first. Once you have this value, open install.sh in your favorite editor (on Windows, I like Notepad++), there are instructions as to where to paste this value. Then save the file and close it.

Step 5. Push the files to the phone
In your local terminal, cd to the directory where you unzipped the files, then run the following commands.

adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /sdcard/busybox
adb push su /sdcard/su
adb push rage /data/local/tmp/rage
adb push install.sh /data/local/tmp/install.sh
adb shell chmod 775 /data/local/tmp
adb shell chmod 755 /data/local/tmp/*

Step 6. Install ConnectBot
Pretty straightforward. Install ConnectBot from the android market. This method may work with other terminal apps, but I have not tested them. I had no luck getting this method to work over ADB.

Step 7. Execute rage
Open ConnectBot and connect to your phone, then issue the following command:

/data/local/tmp/rage

Step 8. WAIT
This has its own step because it’s really important. You have to wait. Be patient. I know, it’s hard, you’re excited, but don’t get all button happy. you’ll mess up the process. The process is complete when you see

[*] Forked %d childs.

(Where %d is replaced by the number of threads forked.)

Once you see this message, disconnect from ConnectBot.

Step 9. Check for root and install root utilities
Open ConnectBot and reconnect to your phone. Where before you saw the $ character indicating you were in userland, you should now see a # indicating that you are root. If you see the # character, congrats! You’re almost done and you may proceed. If you still see the $ character, something messed up and you need to backtrace your steps and figure out where you went wrong. If you are now root, issue the following command:

/data/local/tmp/install.sh

If all went well, this script should have executed with no output and no errors. If everything looks good, go ahead and sync/reboot your phone.

sync
reboot

Step 10. Test your install
At this point, if all went well, your Motorola I1 should be rooted, rebooted and have all the utilities necessary to escalate to root on the command line or run applications that require root permissions. To be sure that it worked correctly let’s test it.

To test on your phone with ConnectBot, start ConnectBot, connect to your phone and issue the command:

su

To test from your computer, you can simply run:

adb shell su

If you’re a security-minded individual or a researcher and are interested in the details of how the root escalation works, there is a great article about it here.

Restore AddressBook Contacts From iPhone/iPod Touch After Reformat

Egeste — Fri, 10 Sep 2010 23:15:10 +0000

So you reformatted your mac and didn’t back up your AddressBook contacts? Whoops. That’s ok though, if you have a jailbroken iPhone you can restore your AddressBook contacts with a little bit of hackery. So lets get started!

1. SSH into your iphone, and get r00t.

TheGame:~ egeste$ ssh root@192.168.1.122
root@192.168.1.122's password:
iPhone:~ root:

2. Go into the mobile user’s home dir and create a backup folder

iPhone:~ root: cd /var/mobile
iPhone:/var/mobile root: mkdir Backup

3. Copy the AddressBook databases into your backup folder

iPhone:/var/mobile root: cp Library/AddressBook/* Backup/

4. Open up iTunes and plug in your iPhone/iPod Touch (if it’s not already). In iTunes, click on your device under Devices, then click on the tab for Info. Check the box to sync your contacts, then click sync. iTunes will ask you if you want to do this because blah blah blah whatever, just do it.

5. Once the sync is complete you will notice that all the contacts are gone from your phone. DON’T FREAK OUT. return to your SSH session and copy the database files back to their original location like so:

iPhone:/var/mobile root: cp Backup/* Library/AddressBook/

6. If you check your phone contacts again you should see that all of your contacts are back. Now all you need to do is sync your phone again. BLAMMO! iTunes should have imported all the contacts from your iPhone into AddressBook. You may have to do some merging and whatnot.

I suppose this would work for Outlook contacts as well, but I haven’t tested it.

Anyway, that’s all for now.
-Egeste

Apache, mod_rewrite, and you

Egeste — Sun, 18 Apr 2010 18:28:54 +0000

mod_rewrite is an awesome module for apache that allows you to rewrite urls. Describes itself right? Like all other apache modules, simply loading the module won’t do jack. You have to configure your apache server, telling it how you want to use mod_rewrite and where you want to use it.

Install mod_rewrite
If you already have apache installed, chances are that you already have the mod_rewrite module. If not, install it.

Debain only

egeste:/etc/apache2# a2enmod rewrite

Load the module in your apache config
Like all other daemons, apache relies on configuration files to tell it how to behave. Common configuration changes for apache would be to load/unload modules, change error or access log locations, etc. If your version apache loads modules in the configuration file, uncomment or add the following line to your config.

LoadModule /path/to/mod_rewrite.so

If your version of apache loads modules from the mods-enabled folder, create a symbolic link to the mod_rewrite config file in mods-enabled. This is what it would look like for me.

egeste:~# cd /etc/apache2/mods-enabled
egeste:/etc/apache2/mods-enabled# ln -s ../mods-available/rewrite.load

Enable .htaccess override in your web application root directory
Enabling .htaccess to override some settings in the root dir of your application allows you to change the way apache will behave in that directory without the need to restart the apache daemon. I like to add this setting to my vhost config. This is what mine looks like (some info redacted).

egeste:/etc/apache2# cat sites-available/egeste.net.conf

 ServerAdmin webmaster@localhost
 DocumentRoot /path/to/site/root
 ServerName www.egeste.net
 ServerAlias egeste.net


 Options FollowSymLinks
 AllowOverride All
 Order deny,allow
 Allow from all

At this point go ahead and give your apache server a restart.

egeste:/etc/apache2# /etc/init.d/apache2 restart

Cool, if all went well, you should have mod_rewrite installed, loaded and configured to allow .htaccess overrides in your site root. The only steps that remain are to define a ruleset in .htaccess and write your web application to handle the requests. I won’t go into detail on mod-rewrite rules and regex, but here’s my wordpress .htaccess file.


RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Happy coding =)

-Egeste

WordPress get_pages() meta_key woes

Egeste — Sun, 18 Apr 2010 18:11:27 +0000

Every once in a while you run into a problem that makes you scratch your head… and eventually maybe smash it against your desk a few times. This was definitely one of those.

get_pages() is a method that returns an array of $post objects (which is very well documented here). There are multiple arguments you can pass to get_pages() for the purpose of filtering the results you get back (these args are well documented here). For example, if you only want to retrieve sub-pages of the current page, you could say:

$pages = get_pages("child_of=".$post->ID);

One of the args you can specify is the meta_key arg, which will only return pages that contain the meta_key you specify. (See: Custom Fields) This is where I ran into some trouble.

It turns out that get_pages has an argument called hierarchical, which according to the codex does the following:

hierarchical

(boolean) Display sub-Pages in an indented manner below their parent or list the Pages inline. The default is true (display sub-Pages indented below the parent list item). Valid values:

1 (true) – default

0 (false)

What’s not intuitive about this argument is that it will filter subpages, (that is, not top-level pages) when using the meta_key arg. Here’s an example:

Data Set

Homepage
About
- Foo
- Bar (This item has a meta_key named banner_title)

Code

count(get_pages("meta_key=banner_title"));

Output: 0
The output indicates that 0 results were returned, despite the fact that we have a page with a meta_key named banner_title. So lets try something different.

Code

count(get_pages("meta_key=banner_title&hierarchical=0"));

Output: 1
Ah, now we’re getting the results we want.

TL;DR – you have to use the hierarchical=0 arg to list all pages that contain your meta_key, otherwise you will only get top-level pages.

-Egeste