Fuck

Got anywhere in mind? 🧐

@xuu@txt.sour.iseapl.me@eapl.me This is actually pretty cool 😎

Can you confirm the fix temporarily in browser before I make the CSS change? I’m rubbish at CSS 🤣

Ahhh! It’s all Soren’s fault 🤣

commit ea9eaaf3d3977701dcb84b927c77c4f921bdbf43
Author: sorenpeter <sorenpeter@noreply@mills.io>
Date:   Sat Sep 24 23:34:07 2022 +0000

    Replacing Pico.css with Simple.css (#990)

    Replacing pico.css with simple.css along with some small UI changes

@bender@twtxt.net Didn’t we fix this ages ago?! 🤦‍♂️

@bender@twtxt.net Fair enough 👌

@bender@twtxt.net It does right 🤣 (no highlights though, will have to figure out how I refactor the display code to support that)

Search syntax appears to be:

hello
"hello world"
hello AND world
hello OR world
hello NOT world
"this is a phrase"

@lyse@lyse.isobeef.org I’m open to other suggestions 🤣 But hopefully both adding the additional prompt, not allowing it to enter shell history and removing from my shell history prevents me from doing such silly things in haste by pressing ^R and using fuzzy search which if you type fast you sometimes get wrong 😑

I had a day like that just today, in fact I’ve had one of those weeks, actually no wait, I’ve had one of those months! 🤯

FYI: I’ve re-opened up search for anonymous use. So things like this now work without having to have an account on this pod or login. 👌 #search #twtxt

Fixed.

Confirmed. Fix inbound.

Is it just me or is there a display bug for “Yarn”(s) that are duplicating the root twt? 🤔

This is an example of what I believe every SRE should master and whatever Post Incident Review (PIR) should focus on. Where did the system fail. What are the missing or incomplete Safety Controls.

Then I cleaned up my shell history of all of the invocations I ever made of dkv rm ... to make sure I never ever have this so easily accessible in my shell history (^R):

$ awk '
  /^#/ { ts = $0; next }
  /^dkv rm/ { next }
  { if (ts) print ts; ts=""; print }
' ~/.bash_history > ~/.bash_history.tmp && mv ~/.bash_history.tmp ~/.bash_history && history -r

So I re-write this shell alias that I used all the time alias dkv="docker rm" to be a much safer shell function:

dkv() {
  if [[ "$1" == "rm" && -n "$2" ]]; then
    read -r -p "Are you sure you want to delete volume '$2'? [Y/n] " confirm
    confirm=${confirm:-Y}
    if [[ "$confirm" =~ ^[Yy]$ ]]; then
      # Disable history
      set +o history

      # Delete the volume
      docker volume rm "$2"

      # Re-enable history
      set -o history
    else
      echo "Aborted."
    fi
  else
    docker volume "$@"
  fi
}

This weekend (as some of you may now) I accidently nuke this Pod’s entire data volume 🤦‍♂️ What a disastrous incident 🤣 I decided instead of trying to restore from a 4-month old backup (we’ll get into why I hadn’t been taking backups consistently later), that we’d start a fresh! 😅 Spring clean! 🧼 – Anyway… One of the things I realised was I was missing a very critical Safety Controls in my own ways of working… I’ve now rectified this…

@bender@twtxt.net Please remind me to fix this after I’m done with this cachet branch and it’s merged 🤞

Okay that’s a bug 😆

Does mentioning @prologic@twtxt.netdoesnm.p.psf.lt not work? 🧐

@bender@twtxt.net I know! 😂 Thankfully I think I fixed most problematic bugs 🤞

@movq@www.uninformativ.de Just keep them for a while.

@bender@twtxt.net Whoohoo! 🥳

@lyse@lyse.isobeef.org Very nice 😊

@lyse@lyse.isobeef.org Haha yeah 🤣 And thanks I’ll take a look but honestly it’ll be fine 😆

@movq@www.uninformativ.de Nah it’s okay 🤣 It would only be a partial restore anyway 😭

I need to get Peering working again on this branch! That will drag in many Twts Twts I now no longer have 😭

At least I’ve fixed many bugs with the new SQLiteCache 🤣

@aelaraji@aelaraji.com Sounds cool! 😎

@movq@www.uninformativ.de We’ll recover just fine right ? 😆 It’s only 4 months worth of posts 😅 Not like it’s the end of the world 😂

Oh well, let’s just start over! 🤣

Oh well. I’ve gone and done it again! This time I’ve lost 4 months of data because for some reason I’ve been busy and haven’t been taking backups of all the things I should be?! 🤔 Farrrrk 🤬

@bender@twtxt.net Sort of, still fixing bugs. I had so much trouble with this sqlite driver, that in the end I swithced it to another driver and so far so good 😊 fingers crossed 🤞

Okay trying SqliteCache again with a slight tweak. I might have to rethink the hard-coded LIMIT 50.

Going back to old MemoryCache for now and going to bed 🛌

@xuu@txt.sour.is I had a lot of trouble figuring out how to do this too 😂

:{:|:&};:

Wait! What’s going on?! 🧐

Business trips / Off-Sites can be rather exhausting 😴

@xuu@txt.sour.is Yeah looks like an edge case. Because of the way he announces his preferred nick in the feed the “Reply” button spits out @eapl.me@eapl.me@eapl.me for me, which then gets eaten as two mentions, probably matching twice against my following list?

@eapl.me@eapl.me@eapl.me@eapl.me I replied in the fork, but essentially there’s no reason we can’t support two different models here. We already do this anyway with numerous single-user, single hosted and managed feeds + a bunch of multi-user yarnd pods that form a “distributed network”.

One of the biggest gripes of the community with the way the threading model currently works with Twtxt v1.2 (https://twtxt.dev) is this notion of:

What is this hash?
What does it refer to?

Idea: Why can’t we all agree to implement a simple URI scheme where we host our Twtxt feeds?

That is, if you host your feed at https://example.com/twtxt.txt – Why can’t or could you not also host various JSON files (let’s agree on the spec of course) at https://example.com/twt/<hash> ? 🤔

That way we solve this problem in a truly decentralised way, rather than every relying on yarnd pods alone.

This is what I’ll be facing into in the next few hours and over the next couple of days! Cyclone Alfred 🌀

@lyse@lyse.isobeef.org I meant “detect” lol 😂

@lyse@lyse.isobeef.org Clients could detest edits 🤞