bramus

🚚 The bookmarklet has moved to https://github.com/bramus/mastodon-profile-redirect/

cljoly

.PHONY: hooks

hooks:
    git config --local core.hooksPath $(shell pwd)/.githooks

oatmealine

A metatable can be defined like

local t = setmetatable({}, {
  __tostring = function() return 'custom tostring behavior!' end
})

Here are the metamethods that you can define, and their behavior

Operators

uncomfyhalomacro

Sway output mirror and screencast

Mirror

wf-recorder

With wf-recorder it is possible to record one output. When ffmpeg is compiled with sdl support, then it is possible to use "sdl" as the muxer and replay the recorded video instead of writing it to a file.

iagoleal

local fmt = string.format

-- Iterator that splits a string o a given delimiter
local function split(str, delim)
  delim = delim or "%s"
  return string.gmatch(str, fmt('[^%s]+', delim))
end

-- Find the proper directory separator depending
-- on lua installation or OS.

umbernhard

Building a Secure Arch Linux Device

Locking down a linux machine is getting easier by the day. Recent advancements in systemd-boot have enabled a host of features to help users ensure that their machines have not been tampered with. This guide provides a walkthrough of how to turn on many of these features during installation, as well as reasoning for why certain features help improve security.

The steps laid out below draw on a wide variety of existing resources, and in places I'll point to them rather than attempt to regurgitate full explanations of the various security components. The most significant one, which I highly encourage everyone to read, is Rod Smith's site about secure boot, which is the most comprehensive and cogent explanation of UEFI, boot managers and boot loaders, and secure boot. Another incredibly useful resources is Safeboot, which encapsulates many of the setup steps below in a Debian application.

Phate6660

body, textarea, input, button {
    font-size: 11px;
}

a {
    color: green;
}

p>a {
    color: green !important;

TaylanTatli

:root {
  --font-family: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial, "Noto Sans", sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";
  --body-color: rgba(255, 255, 255, 0.7);
  --body-background: #282c34;
  --header-link-color: #9b9494;
  --header-active-link-color: #d19a66;
  --input-border: 1px solid #2c384e;
  --input-background: #2c384e;
  --input-placeholder-color: #888;
  --input-focus-border-color: #d19a66;

mjlbach

Foreword

The open source community depends on the efforts of a small group of volunteers relative to the number of users. In order to make the most of contributors' time, here is some advice for asking “good questions”. This is largely paraphrased from this article by Eric Steven Raymond and Rick Moen, with edits for brevity and tone. If you have the time (and tolerance), I strongly recommend reading that article over this one. Let's start with the procedure.

The procedure

1. Try to find an answer by searching the archives of the issue-tracker, IRC, matrix-room, discord, forum or mailing list you plan to post to.
2. Try to find an answer by searching the Web.
3. Try to find an answer by reading the manual.
4. Try to find an answer by reading a FAQ.
5. Try to find an answer by inspection or experimentation.

rsms

[Unit]
Description = Foo HTTP server
Requires    = foo.socket
After       = multi-user.target

[Service]
User             = www-data
Group            = www-data
WorkingDirectory = /var/foo
ExecStart        = /var/foo/bin/foo-server