nanos

Mastodon Comments

A simple, dependency-free script to add Mastodon-powered comments to your site. For details see Adding comments to your blog, powered by mastodon

Turn this HTML

<div id="comments"></div>
<script>
 addEventListener('DOMContentLoaded', (event) =&gt; window.loadComments('{mastodon}',document.getElementById('comments')));

luoyjx

import {
  createParser,
  ParsedEvent,
  ReconnectInterval,
} from "eventsource-parser";

export interface OpenAIStreamPayload {
  model: string;
  prompt: string;
  temperature: number;

peterc

put.your.domain.here {

  @local {
    file
    not path /
  }

  log {
    output file /var/log/caddy/mastodon.log
  }

kettanaito

Chromium on Vercel (serverless)

This is an up-to-date guide on running Chromium in Vercel serverless functions in 2022. What you will read below is the result of two days of research, debugging, 100+ failed deployments, and a little bit of stress.

Getting started

Step 1: Install dependencies

Use chrome-aws-lambda that comes with Chromium pre-configured to run in serverless, and puppeteer-core due to the smaller size of Chromium distributive.

joelonsql

🗺🐘 1000+ PostgreSQL EXTENSIONs

This is a list of URLs to PostgreSQL EXTENSION repos, listed in alphabetical order of parent repo, with active forks listed under each parent.

⭐️ >= 10 stars
⭐️⭐️ >= 100 stars
⭐️⭐️⭐️ >= 1000 stars
Numbers of stars might not be up-to-date.

ksassnowski

import {computed, ref} from "vue";
import {
    addMonths, addYears,
    eachDayOfInterval,
    endOfISOWeek,
    getYear,
    getDate,
    isSameMonth,
    startOfISOWeek,
    startOfMonth,

levelsio

<?

	//
	// AUTO KEYWORD-BASED FOLLOWER CURATION BOT (by @levelsio)
	//
	// File: twitterFollowerCuratorBot.php
	//
	// Created: May 2021
	// License: MIT
	//

fideloper

#!/usr/bin/env bash


###
## This mounts a (single) ephemral NVMe drive in an EC2 server.
## It's meant to be run once, within user-data
## For EBS drives (non-ephemeral storage), see: https://gist.github.com/jalaziz/c22c8464cb602bc2b8d0a339b013a9c4
#

getify

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

reinink

select
  first_name,
  last_name
from
  users
left join
  companies on companies.id = users.company_id
where (
    companies.name like 'TERM%' or
    first_name like 'TERM%' or