Richard Littauer RichardLitt

Dynamic content in distributed applications

30mins

Description

At the heart of every application is a database. In the decentralized web, the peer-to-peer paradigm doesn't use servers, so how can we develop compelling applications and user experiences? This talk will demonstrate orbit-db, a distributed peer-to-peer database built on IPFS. We'll show how we can create traditional data models, such as a key-value store, in a distributed fashion and create applications without servers. We'll cover the underlying data structures and transport mechanisms provided by IPFS, take a look at CRDTs (Conflict-free Replicated Data Types) and show how they can be leveraged to create different types of databases. Using IPFS and orbit-db, we'll show examples of how to build news feeds, real-time chat and comment systems in distributed applications that can run purely in the browser.

Additional resources

orbit-db

orbit-db is a distributed, peer-to-peer database built on IPFS. By saving all data in IPFS and

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

Vocabulary

hinky, but it still made him a little hinky on those skates carillon, The volume went up but couldn't scour away the deep tones of the carillon, which resonated in his long bones. gallimaufry, n. a confused jumble or medley of things. mid 16th cent.: from archaic French galimafrée ‘unappetizing dish,’ perhaps from Old French galer ‘have fun’ + Picard mafrer ‘eat copious quantities.’ Bud's relationship with the female sex was governed by a gallimaufry of primal impulses, dim suppositions, deranged theories, overhead scraps of conversation, half remembered pieces of bad advice, and fragments of no-doubt exaggerated anecdotes that amounted to rank superstition. calla, like a spray of hundred-meter-long calla lilies. calabash, like the germs of some moon-size calabash. natty, in their best crinolines and natty short-pants suits, natty beige linen suit fabricules, constructed of infinitesimal fabricules that knew how to eject dirt

How To Deprecate A Repository on GitHub

A simple checklist for deprecating a repository. See https://github.com/RichardLitt/knowledge/blob/master/how-to-deprecate-a-repository-on-github.md.

Deprecating a project no one uses

Change the GitHub description. This is often the first thing people see for the repository, and the first line that people will see if looking at the repository in the Organization view. The most important thing to do is to add the word DEPRECATED at the front of the description. This clearly marks it will not be updated. You can also add an emoji to it. ⛔️ DEPRECATED <former description> makes it pop out a bit more.
Add GitHub topics: deprecated, obselete, and archived are all good ones.
Edit the title of the README. Remove the current title, and instead write # DEPRECATED.

	var logLsCmd = &cmds.Command{
	Helptext: cmds.HelpText{
	Tagline: "List the logging subsystems.",
	ShortDescription: `
	'ipfs log ls' is a utility command used to list the logging
	subsystems of a running daemon.
	`,
	},
	Run: func(req cmds.Request, res cmds.Response) {
	output := strings.Join(logging.GetSubsystems(), "\n")

	#!bin/sh

	FILE="log/$(date +%Y-%m-%d).md"
	echo "# $(date +%Y-%m-%d)\n" >> $FILE
	cat "daily_routines.md" >> $FILE
	echo "\n" >> $FILE
	cat "todo.md" \| head -5 >> $FILE

	## TODO
	# - [ ] Send anything from yesterday's ## Tomorrow section into the new day


	function license {
	echo "## License

	[MIT](LICENSE)"
	}

	function contribute {
	echo "
	## Contribute

	$ frankenstein libp2p/go-libp2p

	Found: master for libp2p/go-libp2p — libp2p implementation in Go — 513⭐️ — last updated 1 day ago
	🏃 Processing links for libp2p/go-libp2p ...
	🔎 Checking 14 links
	⚪ https://travis-ci.org/ipfs/go-libp2p.svg?branch=master
	✅ https://godoc.org/github.com/ipfs/go-libp2p?status.svg
	✅ https://raw.githubusercontent.com/diasdavid/specs/libp2p-spec/protocol/network/figs/logo.png
	✅ https://github.com/libp2p/specs
	✅ https://img.shields.io/badge/freenode-%23ipfs-blue.svg?style=flat-square

	[alias]
	co = checkout
	ca = !git add -A && git commit -v