#Wisp

Tom Forrestertforrester
2026-02-18

Easily one of my favourite discoveries from last year. This record is hazy alt/grungegaze perfection.

open.spotify.com/track/59ledUS

mariolistens 🎧mariolistens@neko.cat
2026-02-16

I am now listening to Your face by Wisp #Wisp
last.fm/music/Wisp/_/Your+face

2026-02-14

"Time-Traveling Valentine's Gift" for @mtaht:

github.com/TWShiyuLiou1997/sch

🇹🇼:靈魂永駐,精神長存
🇺🇸:May his soul find eternal peace, and his spirit live on forever in our #routers.

h/t Shiyu Liou ❤️

#bufferbloat #latency #sch_CAKE #OpenSource #RFC8290 #jitter #ISP #BandwidthIsALIE #FQ_CoDel #schCAKE #LowLatency #Linux #OpenWrt #Kernel #FQCoDel #Starlink #broadband #WiFi #WISP #FISP #FWA #FTTX #DaveTaht #FLOSS #Taiwan #InternetServiceProvider #InternetService #FTTH

2026-02-12

I’m uneasy about chaining / threading / piping operators, be it #Haskell’s $, #Wisp colon, #Clojure arrows, or my own #CommonLisp #/ operator from <https://codeberg/aartaka/lin-edi-table>.

These seem to restrict the code in what it can do. With dirty imperative or functional code, you can insert new forms literally everywhere. But with these operators you have to come up with strategies to compose things properly.

Which is not a problem with Clojure, because at least built-ins are designed with threading in mind. But it’s much harder in brown field langs like CL.

This post was brought to you by refactoring a complex seven-stage threading in Clojure.

Herbert "Bracket" Wolversonherberticus@fosstodon.org
2026-02-04

We've been having fun working on the next @LibreQoS release. We're testing real-time Quality of Outcome tracking, a heatmap-based summary, and a modernized UI. It's using less CPU, less RAM and is really snappy! #LibreQoS #QoE #WISP #QualityOfOutcome #bufferbloat #latency

The new LibreQoS user interface, showing heatmaps and a modernized user interface.
2026-01-16

Takeaways from a second serious session of #Lisp programming in #ed(1):

• I still need Emacs for indentation and because I only set up #Git auth in #Magit.

• Overall, the code is working nicely with line-readtable syntax

• But I’m afraid of the possibility of extending this code, because my nice line-local nesting operators will break when split across lines.

• My programming style immediately shifted to writing small functions that compose (somewhat (like (that on args))) like in Lamber and #Wisp

This post is written in aed(1)

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst