View index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="robots" content="index,follow" />
<meta name="creator" content="rfcmarkup version 1.127" />
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<meta name="DC.Relation.Replaces" content="draft-butler-geojson" />
View geojson.json
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="robots" content="index,follow" />
<meta name="creator" content="rfcmarkup version 1.127" />
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<meta name="DC.Relation.Replaces" content="draft-butler-geojson" />
View cache.json
This file has been truncated, but you can view the full file.
View cache.json
This file has been truncated, but you can view the full file.
View cache.json
This file has been truncated, but you can view the full file.
View worldcup.csv
team region win loss draw points gf ga cs yc rc
Germany UEFA 7 6 0 1 19 18 4 14 4
Argentina CONMEBOL 7 5 1 1 16 8 4 4 4
Netherlands UEFA 7 5 0 2 17 15 4 11 4
Belgium UEFA 5 4 1 0 12 6 3 3 2
Colombia CONMEBOL 5 4 1 0 12 12 4 8 2
Brazil CONMEBOL 7 3 2 2 11 11 14 0 1
Japan AFC 3 0 2 1 1 2 6 0 1
United States CONCACAF 4 1 2 1 4 5 6 0 0
View geojsonnet.md

Geojson.net

Geojson.net will be a replacement for geojson.io, the simple editor for map data. In most ways, it has the same intent, goals, limitations, and ideas of geojson.io - they're both projects of mine.

I created geojson.io as a side project in 2013, and it thrived for a few years, as it simply solved the problem of previewing, modifying, and creating map data. I think it benefited from simplicity and unity of thought: it wasn't a product, it didn't have overarching design goals or any sort of leadership. There was the core functionality, and a bunch of functionality that pretty neatly layered on top of that without making the whole thing too intimidating. I'm pretty happy with how it went.

Over the last two or so years, though, geojson.io hasn't changed much, and the web has. Which means that, in a few ways, it's just straight-up broken: GitHub integration is broken, it was never updated to accommodate for the deprecation of anonymous gists, and

View index.js
const prettier = require('prettier')
console.log(prettier.__debug.formatAST({
"type": "Identifier",
"name": "hi"
}))
View index.js
module.exports.gif = function gif(r, g, b) {
return 'R0lGODlhAQABAIAB' +
(new Buffer([0, r, g, b, 0, 0])).toString('base64') +
'ACwAAAAAAQABAAACAkQBADs=';
}
View dat-resilience.md

So, as I mentioned last time, I have two fundamental goals with dat that are not addressed by simply running dat share.

  • Uptime: making sure that the site is seeded even if my local laptop is closed, eaten by a bear, or disconnected from the internet
  • Resilience: ensuring that there's a way to restart my website if the original seeding computer is lost. I try to make everything on my primary work/personal computer work in such a way that I can recover it all, easily, onto a new machine if I need to

To break these down a bit more, uptime is a combination of two things:

  • Ensuring that there are seeders
  • Ensuring that those seeders are seeding, and they're up-to-date