pfrazee

Using Dat with a github.io domain

My personl site is hosted at hashbase.io (link) so that you can access it via dat and https. My canonical dat url is dat://pfrazee.hashbase.io.

Before I used hashbase I used Github Pages, and today it dawned on me that I can have dat://pfrazee.github.io work too. It's pretty simple if you know the dat dns spec.

All I had to do was add /.well-known/dat to my site (click to view). I put the raw dat URL of my site in that file, along with a TTL.

elclanrs

Install

npm install funcoffee

Require

require('funcoffee').expose global

alexchung

# -*- coding: utf-8 -*-
import sys
import os
import base64
import bcrypt
from Crypto import Random
from Crypto.Cipher import AES
from Crypto.Hash import SHA256

class Blockout:

una

<!-- @una made this -->

<ul class="color-list">
    <li class="color-box brick-red"></li>
    <li class="color-box strawberry"></li>
    <li class="color-box deep-orange"></li>
    <li class="color-box tangerine"></li>
    <li class="color-box gold"></li>
    <li class="color-box sunshine"></li>
    <li class="color-box grass-green"></li>

scottkellum

// ----
// Sass (v3.3.0.rc.1)
// Compass (v0.13.alpha.7)
// ----

=e($name)
  @at-root #{&}__#{$name}
    @content
=m($name)
  @at-root #{&}--#{$name}

clifff

PaulKinlan

(function() { 
  var CSSCriticalPath = function(w, d, opts) {
    var opt = opts || {};
    var css = {};
    var pushCSS = function(r) {
      if(!!css[r.selectorText] === false) css[r.selectorText] = {};
      var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
      for(var i = 0; i < styles.length; i++) {
        if(!!styles[i] === false) continue;
        var pair = styles[i].split(": ");

svallory

require 'colorize'

module Liftr
    module Importers
        class ImportOnce < ::Sass::Importers::FilesystemFilesystem

            attr_accessor :root, :debug_level, :staleness_check, :imported, :original_filename

            # Creates a new filesystem importer that imports files relative to a given path.
            #

joyrexus

St Ives

class Slider
  constructor: (@i, @range) -> 
    @ui = '<span class="slider">' + @i + '</span>'

slider = (i, range) -> new Slider i, range

There are #{sacks} sacks
Every sack had #{cats.ui} cats

blackfalcon

by Dale Sande

CSS has had a long and sordid past. A developer never sets out with the goal of making a complete and total mess of things. Their intention is not to build something that is practically illegible, impractical to maintain and is limited in scale. But somehow, this is where many inevitably end up. Luckily, all is not lost. With some simple strategies, organizational methods and out-of-the box tools, we can really help get that junk-drawer inline.

For many of us getting started with Sass, at one time or another have created a junk-drawer of files. For most, this was a rookie mistake, but for others, this is a continuing issue with our architecture and file management techniques. Sass doesn't come with any real rules for file management so developers are pretty much left to their own devices.

Large CSS files and increased complexity

CSS started out with very simple intentions, but as [tableless web design][1.1] began to really take a foothold, o