
Trilium now has an official homepage:
Edit: I'm not the owner or a Trilium's dev.
#Tag
Trilium now has an official homepage:
Edit: I'm not the owner or a Trilium's dev.
Trilium now has an official homepage:
Edit: I'm not the owner or a Trilium's dev.
I just sponsored @joplinapp Go sponsor your open source dependencies!
https://github.com/sponsors/laurent22?sp=GPrimola
#FOSS #NoteTaking #JoplinNotes #GoEuropean #AlternativeTo #Apple #BuyFromEU #Notes #OpenSource #MineIsYours
I just sponsored @joplinapp Go sponsor your open source dependencies!
https://github.com/sponsors/laurent22?sp=GPrimola
#FOSS #NoteTaking #JoplinNotes #GoEuropean #AlternativeTo #Apple #BuyFromEU #Notes #OpenSource #MineIsYours
relatedly: in Brazil I had a Samsung washing machine that, when it was done washing, would beep with actually pleasant tones. first of all the beeps, while still clearly electronic, were not simply triangles or squares, but a crystaly timbre that reminded me of windchimes. and it wouldn't just beep the same note a few times, but play a happy little tune that made it feel like the machine was proud of a job well done.
ever since having that machine I still resent the harsh, dissonant loud beeps of my current washing machine, my microwave, my fax maschine, my tria laser 4x, and basically ever single machine that beeps. I often wonder what they do to designers that all machines have to be so aurally primitive. it seems to me that just having 1) clicky physical buttons, sturdy and reliable plus 2) pleasant auditory feedback would instantly make a machine enormously more enjoyable to use, at minimal cost, and in a market that seems oversaturated by models that would be a clear differential?
but what do I know, maybe nobody else cares about how the beeps of the machines sound
relatedly: this is the script I use when I want to make my computer beep a few times to tell me a task is completed or something:
#!/bin/bash
# usage: soxbeep [N] [duration]
# where N = number of beeps (default 1)
# and duration = duration in seconds (default 0.33)
# try e.g. soxbeep.sh 7
n=1
duration=0.33
wavetype=tri
if [ "$1" ]; then
n="$1"
fi
if [ "$2" ]; then
duration=$2
fi
if [ "$3" ]; then
wavetype=$3
fi
# penta M
notes=( A3 C4 D4 E4 G4 A4 C5 D5 E5 G5 )
function getnote() {
echo "${notes[$RANDOM % ${#notes[@]} ]}"
}
command=''
for blah in $(seq $n); do
note="$(getnote)"
command="$command synth $duration $wavetype $note :"
done
# remove last ':'
command="${command:0:-1}"
play -q -n $command 2>&-
I have used variations of this basic idea since 2001, when my NetBSD webserver (an old 486 in my dorm room) would beep to us every minute whenever the ADSL modem randomly stopped responding. NetBSD is cool because you can just pipe to /dev/speaker, in Linux you'll need sox(1) installed.
I've been playing around with streamlining documentation by pulling JSDoc comments straight into an #11ty website. I'll try and write it up once I get it to somewhere I'm a bit happier with.
For example, this page is partially generated based on the comments directly in the JavaScript code
https://gruber.r0b.io/postgres/
https://github.com/robb-j/gruber/blob/main/postgres/postgres-migrator.ts
It's pretty cool, and hopefully makes the documentation so much closer to edit when the code itself changes, Though I think there needs to be more curatability in it.
I've been playing around with streamlining documentation by pulling JSDoc comments straight into an #11ty website. I'll try and write it up once I get it to somewhere I'm a bit happier with.
For example, this page is partially generated based on the comments directly in the JavaScript code
https://gruber.r0b.io/postgres/
https://github.com/robb-j/gruber/blob/main/postgres/postgres-migrator.ts
It's pretty cool, and hopefully makes the documentation so much closer to edit when the code itself changes, Though I think there needs to be more curatability in it.
"If you wanna know how I write 2-3 books per year, blame the #cognitiveprosthesis of #blogging, which forces me to apply rigor to the #notes I take, and rewards me with a searchable database of everything I've ever found important, while stimulating a constant mnemonic rejuggling of all those thoughts that crystallizes into an endless stream of novel synthetic insights and road-tested ways to express them."
The @pluralistic strategy you'll want to learn.
https://pluralistic.net/2025/07/28/twiddlehazard/
"If you wanna know how I write 2-3 books per year, blame the #cognitiveprosthesis of #blogging, which forces me to apply rigor to the #notes I take, and rewards me with a searchable database of everything I've ever found important, while stimulating a constant mnemonic rejuggling of all those thoughts that crystallizes into an endless stream of novel synthetic insights and road-tested ways to express them."
The @pluralistic strategy you'll want to learn.
https://pluralistic.net/2025/07/28/twiddlehazard/
A space for Bonfire maintainers and contributors to communicate