chozahell

Brew install specific version / Locally freeze version

# Please define variables
packageName=<packageName>
packageVersion=<packageVersion>

# Create a new tab
brew tap-new local/$packageName

xianlin

#!/usr/sbin/nft -f

flush ruleset

table inet filter {
    # Define allowed IP range
    set allowed_nets {
        type ipv4_addr
        flags interval
        elements = {

evanesoteric

#!/usr/bin/nft -f
# vim:set ts=2 sw=2 et:

flush ruleset


# whitelist { admin, office }
define admin = { 10.10.10.10, 172.16.0.0/16 }

# blacklist

fabiojmendes

# This config is based on the original nftables
# config that ships with fedora/rocky/rhel
# Added podman_allowed so it works with podman

# Sample configuration for nftables service.
# Load this by calling 'nft -f /etc/nftables/main.nft'.

# Note about base chain priorities:
# The priority values used in these sample configs are
# offset by 20 in order to avoid ambiguity when firewalld

timothyham

A Short IPv6 Guide for Home IPv4 Admins

This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.

Let’s begin.

First of all, there are some concepts that one must unlearn from ipv4:

Concept 1

jirawan-chuapradit

package handlers

import (
	"context"
	"io"
	"net/http"

	"github.com/jirawan-chuapradit/tracing-go/service"
	"github.com/rs/zerolog/log"
	"go.opentelemetry.io/contrib/bridges/otelslog"

cyrex562

#!/usr/sbin/nft -f

flush ruleset

table inet filter {
        chain input {
                type filter hook input priority 0; policy drop;
                ct state invalid counter drop comment "early drop of invalid packets"
                ct state {established,related} counter accept comment "accept all connections related to our sessio>
                iifname "tailscale0" accept

macrat

A simple search query parser

Supported syntax:

• and (a b, a AND b)
• or (a OR b)
• not (NOT a)
• grouping ((a))

rain-1

On Llamafile not making sense

The LLamafile project doesn't make sense.

The claim is that it is "bringing LLMs to the people", but you could already run an LLM - which is a large binary file containing lots of floating point numbers - by using llama.cpp.

Llamafile joins a compiled binary program to run LLMs with a weights binary into a single file. This isn't a useful goal. you could simply distribute a zip containing an .exe and a weights file together. Or better still: Decouple the program that runs these chatbots from the chatbot weights.

Imagine if PNG files were also an executable that could pop open a window that displays a PNG on your computer. There is a reason we don't do this: It's not good engineering.

karitham

package http

import (
	"context"
	"log/slog"
)

// RequestAttrGrabber adds an attribute to each row produced by the logger when it can
type RequestAttrGrabber struct {
	Sub         slog.Handler