> Being drunk is not an excuse
Hmmm
> Being drunk is not an excuse
Hmmm
> Being drunk is not an excuse
Hmmm
$ yarnd --help 2>&1 | grep interval
--fetch-interval string cache fetch interval (how often to update feeds) in cron syntax (https://pkg.go.dev/github.com/robfig/cron) (default "@every 5m")
However, Pods actually also utilise WebSub between each other to subscribe to each other's feeds. So fetches _can_ be near real-time without having to have an aggressive fetch interval.
We should have promoted the WebSub feature in the recent v0.15.x release but I forgot to π
Add
websub to your "Operational Features" in the Web UI or --enable-feature websub until we do:
$ yarnd --help 2>&1 | grep feature
--enable-feature feature enable the named feature
Also, thanks for your PR! π
$ yarnd --help 2>&1 | grep interval
--fetch-interval string cache fetch interval (how often to update feeds) in cron syntax (https://pkg.go.dev/github.com/robfig/cron) (default "@every 5m")
However, Pods actually also utilise WebSub between each other to subscribe to each other's feeds. So fetches _can_ be near real-time without having to have an aggressive fetch interval.
We should have promoted the WebSub feature in the recent v0.15.x release but I forgot to π
Add
websub to your "Operational Features" in the Web UI or --enable-feature websub until we do:
$ yarnd --help 2>&1 | grep feature
--enable-feature feature enable the named feature
Also, thanks for your PR! π
- We build a
/api/v1/admin/delete API endpoint which takes {"hash": <hash>} as JSON input.- We build a
yarnc admin delete <hash> sub-command (start a new sub-command group)Which would delete a Twt by hash from the Pod's archive and blacklist it (as it could come back from other pods via the Converge logic).
This _would_ require manual operations to be performed by one or more cooperating / participating Pod operators in the network. And I _think_ this would have to end up being a "culture" we build upon where we agree when incidents that require this happen, that we get together in some way to cooperatively agree on a Twt deletion.
A similar set of tools would have to be built for the Twtxt Search engine too, although I would probably do this by hand for now as it does not peer with pods and therefore has no way to bring back Twts from the dead from a convergence logic that
yarnd has.
- We build a
/api/v1/admin/delete API endpoint which takes {"hash": <hash>} as JSON input.- We build a
yarnc admin delete <hash> sub-command (start a new sub-command group)Which would delete a Twt by hash from the Pod's archive and blacklist it (as it could come back from other pods via the Converge logic).
This _would_ require manual operations to be performed by one or more cooperating / participating Pod operators in the network. And I _think_ this would have to end up being a "culture" we build upon where we agree when incidents that require this happen, that we get together in some way to cooperatively agree on a Twt deletion.
A similar set of tools would have to be built for the Twtxt Search engine too, although I would probably do this by hand for now as it does not peer with pods and therefore has no way to bring back Twts from the dead from a convergence logic that
yarnd has.
Therefore I have gone and deleted that Twt out of your feed (by hand). As I have no way to contact you (as you provide very little information on your Profile or any way to contact you) I've had to take this action without your prior consent.
Please understand that our goals for Yarn.social is to build and maintain a positive culture for as long as we possibly can. Thanks! π
Therefore I have gone and deleted that Twt out of your feed (by hand). As I have no way to contact you (as you provide very little information on your Profile or any way to contact you) I've had to take this action without your prior consent.
Please understand that our goals for Yarn.social is to build and maintain a positive culture for as long as we possibly can. Thanks! π
include plugin for zs:
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\n" "$(basename "$0")"
exit 0
fi
if [ -f "$1" ]; then
cat "$1"
else
echo "error: file not found $1"
fi
Sorry π
include plugin for zs:
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\n" "$(basename "$0")"
exit 0
fi
if [ -f "$1" ]; then
cat "$1"
else
echo "error: file not found $1"
fi
Sorry π
include plugin for zs:
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\\n" "$(basename "$0")"
exit 0
fi
if [ -f "$1" ]; then
cat "$1"
else
echo "error: file not found $1"
fi
Sorry π
$ cat .zs/include.sh
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\n" "$(basename "$0")"
exit 0
fi
fn="${ZS_OUTDIR}/$1"
if [ -f "${ZS_OUTDIR}/$1" ]; then
cat "${ZS_OUTDIR}/$1"
else
echo "error: file not found ${ZS_OUTDIR}/$1"
fi
Usage:
{{ include.sh twtxt.txt }} (as used by the Yarn.social site and to include a full-example feed in the "Manually" section (Thanks to @autiomaa for this feedback! πββοΈ) #Yarn.social #zs #static-site #static-site-generator
$ cat .zs/include.sh
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\n" "$(basename "$0")"
exit 0
fi
fn="${ZS_OUTDIR}/$1"
if [ -f "${ZS_OUTDIR}/$1" ]; then
cat "${ZS_OUTDIR}/$1"
else
echo "error: file not found ${ZS_OUTDIR}/$1"
fi
Usage:
{{ include.sh twtxt.txt }} (as used by the Yarn.social site and to include a full-example feed in the "Manually" section (Thanks to @autiomaa for this feedback! πββοΈ) #Yarn.social #zs #static-site #static-site-generator
$ cat .zs/include.sh
#!/bin/sh
if [ ! $# = 1 ]; then
printf "Usage: %s <file>\\n" "$(basename "$0")"
exit 0
fi
fn="${ZS_OUTDIR}/$1"
if [ -f "${ZS_OUTDIR}/$1" ]; then
cat "${ZS_OUTDIR}/$1"
else
echo "error: file not found ${ZS_OUTDIR}/$1"
fi
Usage:
{{ include.sh twtxt.txt }} (as used by the Yarn.social site and to include a full-example feed in the "Manually" section (Thanks to @autiomaa for this feedback! πββοΈ) #Yarn.social #zs #static-site #static-site-generator
I'm a lazy sysadmin -- In fact I stopped doing this "sysadmi " shit yeats ago π
I'm a lazy sysadmin -- In fact I stopped doing this "sysadmin " shit years ago π
I'm a lazy sysadmin -- In fact I stopped doing this "sysadmin " shit years ago π
Host header (_virtual hosts_) π
Host header (_virtual hosts_) π
yarnd v0.15.1? I still can't repro here... π’
yarnd v0.15.1? I still can't repro here... π’
Quite a few artists that demo their stuff on Youtube seem to use a combination of these two devices:
- [AKAI - MPK mini MK3 - Google Search](https://www.google.com/search?q=AKAI - MPK mini MK3)
- [Novation - Launchpad Mini MK3 - Google Search](https://www.google.com/search?q=Novation - Launchpad Mini MK3)
And only a couple of hundred bucks for the gear it doesn't sound too expensive to even try π€ #Music #MIDI #LiveLoop
Quite a few artists that demo their stuff on Youtube seem to use a combination of these two devices:
- [AKAI - MPK mini MK3 - Google Search](https://www.google.com/search?q=AKAI - MPK mini MK3)
- [Novation - Launchpad Mini MK3 - Google Search](https://www.google.com/search?q=Novation - Launchpad Mini MK3)
And only a couple of hundred bucks for the gear it doesn't sound too expensive to even try π€ #Music #MIDI #LiveLoop