@movq@www.uninformativ.de Oh nothing much 🤣 Just a bunch of folks running really old versions of yarnd
that were susceptible to abuse on the open web 🤣
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
Hopefully you should see traffic die off a bit too as the /external
endpoint is no longer externally abusable (get it) without being an authenticated user – which became problematic 🤦♂️ – The web is so fucking hostile 🤬
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci Hopefully it shouldn’t 🤞
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci Fuck that script 🤣 you’re good! Just follow the Build from Source docs 😅
Thinking we need to adapt the UI a little bit to something like this
@bender@twtxt.net I can see the same errors again hmmm 🧐 @stigatle@yarn.stigatle.no Did you run out of disk again? 😅
I had a play with LiveKit Agents Playground: KITT and I have to say it’s pretty impressive. Not the ChatGPT part of course, but the speech recognition and text to speech synthesis.
KITT is an AI voice assistant powered by LiveKit Agents, Deepgram, Eleven Labs, and ChatGPT. It is running on LiveKit Playground.
It’s too bad it relies on three cloud services, none of which can be run locally (with the exception of Ollama that you could replace the OpenAI component with).
@lyse@lyse.isobeef.org Man gotta love that sunset !!! So nice 😊
You should have the fancy new SPA-like UI too 😅 (just checked!)
@stigatle@yarn.stigatle.no No worries at all! 👌
@stigatle@yarn.stigatle.no Note that “Building From Source” is covered in the docs
You are reminding me that I should cut a release soon™ so there are binaires you can just “download” and use for the platform of choice 😅
@stigatle@yarn.stigatle.no So make deps
would have installed some tools in either $GOPATH/bin
or $GOBIN
. See which with go env
. Chuck that in your $PATH
and you’re good to run make server
. Normally this would be something like:
GOBIN=$HOME/go/bin
GOPATH=$HOME/go
export GOPATH GOBIN
...
@stigatle@yarn.stigatle.no Run make deps
. I use a non-standard (written in Go) minify tool
@stigatle@yarn.stigatle.no Take a backup of the data dir in case I screwed something up 🙏
@stigatle@yarn.stigatle.no Sweet 👌
@stigatle@yarn.stigatle.no I think pods have become exploited over time so I’ve had to tighten up some feature like the external handler 😢
@stigatle@yarn.stigatle.no Ahh! Please update to the latest main 🙏
@stigatle@yarn.stigatle.no Works now! 🥳
@stigatle@yarn.stigatle.no It looks like your some kind of problem with the reverse proxy in front of yarnd
? 🤔I ’m seeing this error: incomplete chunked encoding
error(s)
I don’t know anything about this though, tbh I’ve never seen this before myself 🤔”
@stigatle@yarn.stigatle.no I’m doing okay 👌 Busy with work as you can imagine, and still tinkering of course whenever I can spare a moment or two! 😅
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
For example this one that got fixed this year:
commit 4304ec7ea3c5df95e0ed82bfa292c9330e342f61
Author: James Mills <james@mills.io>
Date: Mon Jan 24 00:10:33 2022 +0000
Fix bug in DownloadImage() leaking termporary files for external avatar downloads (#746)
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
I also think you may be running a version that had a bug and lacked cleanup of those temp files
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
At work right now so will have more concrete details in a few hours from now
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci I will have a look but I suspect it has something to do with the open nature of the external endpoint. I closed this loophole recently due to other reasons myself.
@stigatle@yarn.stigatle.no Nice to see you still around (even if occasionally) 😅
Same hwre
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci Please update!
@abucci@anthony.buc.ci can you update to the latest revision in the main branch?
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci What revision are you running?
watch -n 60 rm -rf /tmp/yarn-avatar-*
in a tmux
because all of a sudden, without warning, yarnd
started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554
into /tmp
, which filled up the entire disk and started crashing other services.
@abucci@anthony.buc.ci Wer that’s a bug!
Are we over Crowdstrike yet? 🤔🤣 Have We forgotten about it? 😅
@bender@twtxt.net This is sadly all too true 🤣
@hacker-news-newest@feeds.twtxt.net this reminds me I need to seriously consider exploring the idea of replacing my Plex set up with Jellyfin
@lyse@lyse.isobeef.org so in other words, their own entire sections of global industries that are using this rubbish crowd, strike antivirus/endpoint detection, piece of crap that are infection effectively in violation of the terms of conditions of the service? 🤔
That’s some good sleuth thing that @lyse@lyse.isobeef.org 🙇♂️
@bender@twtxt.net sometimes having the open honest and transparent conversation and discussion is more valuable than anything to be individually gained. 😅 it helps us learn!
@movq@www.uninformativ.de Who says it’s bad stuff or negativity? These are lessons to be learned and things to gain experiences from right?
@movq@www.uninformativ.de Yeah pretty much ooops 🤦♂️
@movq@www.uninformativ.de Haha 🤣 I might have liked a few, hell even agreed with you on some 🤣
Some bad code just broke a billion Windows machines - YouTube – This is a really good accurate and comical take on what happened with this whole Crowdstrike global fuck up.
@bender@twtxt.net i’m thinking it’s probably worth to try and implement both features as use for configurable preferences just so that we can see what it’s like. 🤣 The default, of course would be the regular pagination that exists now.
@lyse@lyse.isobeef.org Heh 😀 This is why we’ve always implemented features that have differing opinions as either user options, configuration or feature gated 🤣
@lyse@lyse.isobeef.org So you neither like “Click to Load” nor “Infinite Scroll” eh? I mean I sort of get it, infinite scroll is kind of annoying as you never really know wtf is going on. Click to Load misses out on “how many pages”, “what page you’re on”, etc. But is it really that bad? 🤔
Hmmm according to this you are right! I wonder what kind of crypto they use?
@bender@twtxt.net Messages (formally known as iMessages) has always lacked e2e encryption though and often falls back to using SMS which is worse for security and privacy. – OTOH this might be all changing for the better with Google lounging for a new standard? 🤔 (Although I do have to wonder: “What’s in it for Google?”)
DuckDuckGo’s mobile view does this for example
@bender@twtxt.net Pretty much. One post per feed.
@lyse@lyse.isobeef.org My god ! 🤦♂️
@lyse@lyse.isobeef.org What about “Click to Load”?