I’m thinking of bringing back filters (this time not as a feature flag, just baked in): New filters: Hide Feed, Hide Bots, Hide News, Media Only, No Replies, Local Only — toggle to trim noise & surface the Twts you care about.

@javivf@adn.org.es Sorry. 😂 Meet me on IRC at irc.mills.io in #edgeguard 👌 I’m @james@yarn.mills.io there 😅

@bender@twtxt.net Haha fine 🤣

@javivf@adn.org.es Hit me up on IRC or something and we’ll get started 👌

Farrrk me Google search is and these days. Will they please “fuck off” with this Gemini AI garbage at the top that takes forever and is distracting as shit™ 💩 Fark me 🤦‍♂️ #Google #Search #Sucks #AI #Gemini

@movq@www.uninformativ.de Yeah I actually use sift a lot these days for most “searching” – at least code and text searching. For finding files by name I still use find | grep.

@kat@yarn.girlonthemoon.xyz It’s also perfectly safe to nuke your cache as well. i.e: rm data/cache* and it’s all good, things will just get rebuilt 👌

@kat@yarn.girlonthemoon.xyz I totally recommend zs 🤣 It powers all my sites! 😅 https://twtxt.dev https://yarn.socia/ https://prologic.dev etc 😎

@kat@yarn.girlonthemoon.xyz Hmmm Please if this happens again, help me reproduce it. Any clues in the logs? Hmm? 🧐 My own pod has been running flawlessly for weeks now 😅

@movq@www.uninformativ.de Same here, you do get used to things over time and build a sort-of “muscle memory”. But you’re right, maybe they have terrible interfaces and usage options? 🤔

@bender@twtxt.net I like to self-host 🤣

@bender@twtxt.net Yeah I know 😢 Don’t have Disney+, hell I don’t have many streaming services at all really 🤣

Hmmm Star Wars Andor I think it was 🤔

@bender@twtxt.net Ahh I see. That reminds me, I was going to start watching something someone recommended here hmmm 🧐

@bender@twtxt.net Huh? 🤔

Anyone want to help me alpha/beta test the new WAF I’m building? It’s a Caddy module. 🤔

@kat@yarn.girlonthemoon.xyz Ahh but you’re like one of a very few that actually own domains and do interesting things 😅

@bender@twtxt.net How do you explain mine then? Unless it was registered before me, then let go of and I re-registered it later? 🤔

@bender@twtxt.net I’m not sure this is accurate, if you lookup mine:

$ whois shortcircuit.net.au 2>&1 | grep -i creat
created:      1986-03-05

I think this has to be the registrar’s creation date no? 🤔

Yeah I can’t figure out when I registered shortcircuit.net.au 😭

According to a very old email one of my more personal family domains was registered in 2013 making it 12 years old, so I was closed 🤣 my public facing one is much much older 🤣

@anth@a.9srv.net I actually don’t have a clue how old my public-facing domain is 🤣 I have another more personal one that’s probably around ~15 years, but I’m not even sure how to check tbh 😅

@lyse@lyse.isobeef.org I agree with this sentiment 🙌

And yes I’m taking some inspiration from Anubis here 😅

One thing about my design here is that it would no longer incorporate “regex”-based rules like OWASP, mostly because my experience thus far has taught me that these rules are kind of overly sensitive, produce false positives and I’m not sure they are really very effective. For example, why is the point of performing SQL injection detection at the Edge using a WAF if you already handle SQL properly in the first place? (seriously does anyone still construct SQL queries by hand with effectively printf?!)

Also spent the morning continuing to think about a new design for EdgeGuard’s WAF. I’m basically going to build an entirely new pluggable WAF that will be designed to only consider Rate Limiting, IP/ASN-based filtering, JavaScript challenge handling, Basic behavioral analysis and Anomaly detection.

The only part of this design I’m not 100% sure about is the Javascript-based challenge handling? 🤔 I’m also considering making this into a “proof of work” requirement too, but I also don’t want to falsely block folks that a) turn Javascript™ off or b) Use a browser like links, elinks or lynx for example.

Hmmm 🧐

Running monthly backups…

@kat@yarn.girlonthemoon.xyz Ahh I see ! 😅

Love all the funky colors though 😎

@kat@yarn.girlonthemoon.xyz You’ll have to forgive me 🙏 My vision impairment is getting in the way of seeing this “prompt box” thingy 🤣

Or is it Textadus (hmm not sure I can even spell it 😱) now? 🤔

@sorenpeter@darch.dk Hah 😅 Just like how we ‘all just talk about Twtxt right? 🤣

@kat@yarn.girlonthemoon.xyz This sounds cool! 😎 Can you show me? 🤔

@kat@yarn.girlonthemoon.xyz Look into using something like pyrra for creating and managing SLO(s) with Prometheus 👌 I use this myself actually, plus I also use HetrixTools for external monitoring with SLO-style measures via status.mills.io 👌

@bender@twtxt.net Me too! She’s awesome 🙌

Move beyond basic threshold alerts! Define clear Service Level Objectives (SLOs) and measure Service Level Indicators (SLIs) to track real user impact. Use Prometheus to alert when your SLOs are at risk, ensuring you focus on what truly matters to your users. #Monitoring #SRE #Prometheus

@kat@yarn.girlonthemoon.xyz I’d recommend alerting off of Prometheus 👌

@xuu@txt.sour.is Cool! I’ll have to give it a watch 👌

Really hoping Elizabeth Watson Brown wins and hold her seat here in Ryan 🙏

@kat@yarn.girlonthemoon.xyz Any idea why?

@bender@twtxt.net I think this would be a good idea as @movq@www.uninformativ.de and @andros@twtxt.andros.dev have done ✅ I may even join the experiments if I have any spare time to hack a custom yrand branch and run it up on say something like a yarnexp.mills.io or something 🤔

@bender@twtxt.net This ☝️

@sorenpeter@darch.dk No because as the spec statd originally, and we didn’t change that syntax at all:

Mentions are embedded within the text in either @ or @ format

So the lextwt parser we use will simply call this an invalid mention, which it does.

@sorenpeter@darch.dk Unfortunately it does break all clients, because the original spec stated:

Mentions are embedded within the text in either @ or @ format

@movq@www.uninformativ.de Just like Friday’s right? 😅

@andros@twtxt.andros.dev Yup! 👌

@kat@yarn.girlonthemoon.xyz Make sure you’re up-todate with main 🤣 I’m fixing little things here and there. Also please report bugs 🐞

Hopefully I haven’t missed or messed anything upu 😅

* 101f3eb0 - (HEAD -> main) Fix a bunch of UX to do with following/unfollowing, bookmarking and unbookmarking (3 seconds ago) <James Mills>

Testing UI/UX is hard™ 😉

On a public holiday here (Labor Day, ironic really considering the labor party here in Australia has won their 2nd term this election haha 🤣)

Going to try and few up a few more UX bugs today with yarnd.

@kat@yarn.girlonthemoon.xyz Have you rebuild from main recently? 🤔

@lyse@lyse.isobeef.org Yeah to avoid cutting off bits at the end making hashes end in either q or a 🤣

@kat@yarn.girlonthemoon.xyz No no, it’s just barks at the slightest thing going on around the neighborhod 😃 like it just goes a bit nuts often 🤣 it was a rescue dog, two years old, and it wasn’t treated very well, a street dog. I think it’s just basically afraid of every human in the world 😢

@andros@twtxt.andros.dev Programming is art. You become good at art by practising your art. You learn artistic patterns by being inspired by and reading others art works. The most importance however is that you practise your art.

@javivf@adn.org.es Yes and still in review .

@lyse@lyse.isobeef.org You are of course right! 🤣 There are some low level components that can and should be unit tested for sure! 👌

How do you stop a dog from barking? 🧐

@kat@yarn.girlonthemoon.xyz It is 😅

@bmallred@staystrong.run You mean ActivityPub + Twtxt? 🤔

@kat@yarn.girlonthemoon.xyz Ysy!!! 🙌🙌🙌

@bmallred@staystrong.run It really is 🤣

@bender@twtxt.net Bahahah 🤣😂 mate, me and one of my SRE colleagues actually came up with the terminology ourselves! 😛

@lyse@lyse.isobeef.org Heh I have to wear gloves now when swining an axe or it hurts my hands 🤣

@kat@yarn.girlonthemoon.xyz / @xuu@txt.sour.is Recommend you git checkout main && git pull, rebuild and redeploy: make build, and however you deploy. 🙏 Lots of fixes (no more stalling) and optimizations to the feed fetcher, smoother cpu usage, better internal metrics.

I’m not even being facetious here either. I’d llove to see you “unit tests” this:

@lyse@lyse.isobeef.org Well you are being slightly rude 🤪 Sure you could write unit tests for this, but in practise testing emergent properties and behaviors of a system is actually a lot harder than you might realize. But I’m happy to always be proven wrong 😑

@kat@yarn.girlonthemoon.xyz Yeah right now I’m trying to see if I can “spread the CPU usage of fetching N feeds across M duration” so basically “smooth” out the spikes in CPU usage.

@kat@yarn.girlonthemoon.xyz I’ve almost fixed this btw 🤗 Just testing it thoroughly and polihsing the code. In case you’re curious, I do this style of development called “Observability Driven Development” (ODD) whereby I make observations of the system via metrics and internal observations and adjust the system’s overall behavior to the desired outcome 😅

Hey @kat@yarn.girlonthemoon.xyz If you see this, I’m aware of a bug. I’m trying to figure it out and fix it. bare with me 🤗 It is what’s causing things to “stall” and to have to “restart”. Sorry 😞

@@twtxt.net The fact that it has an SDK and process management is quite amazing g! 🤯

@movq@www.uninformativ.de No problems 🤗

@bender@twtxt.net Haha 🤣

@kat@yarn.girlonthemoon.xyz Please git pull and rebuild 😂 Off of main. I merged the catcher branch already!

@kat@yarn.girlonthemoon.xyz @xuu@txt.sour.is Recommend you git checkout main && git pull && make build. Few bug fixes 😄

@bender@twtxt.net You’re kind of right though 😄 It makes it more engaging IMO 😅

“Monosyllabic replies” refers to responses that consist of a single syllable. These types of replies are typically brief and concise, often used in situations where a simple, direct answer is given. Examples include words like “Yes,” “No,” “Okay,” or “Sure.”

😂 Can I imply you’re not interested in things like “LIke”, “Report”, etc?! 😂

@bender@twtxt.net I knew you wouldn’t be interested in a Twtxt+ActivityPub 😂 Now I have to go figure out what “monosyllabic replies” means 🤣

@movq@www.uninformativ.de Shall I add this to the spec I’m writing? ✍️

After yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?

The reason I think this can work so well and I’m in full support of it is that it’s the least disruptive way to resolve the issue of:

where did this hash come from?

@movq@www.uninformativ.de I think we can make this work 👌 As long as it’s just a client hint.

@kat@yarn.girlonthemoon.xyz Should be fine 🙌

Otherwise assume normal behavior. Pretty easy to implement I think.

@movq@www.uninformativ.de If we’re focusing on solving the “missing roots” problems. I would start to think about “client recommendations”. The first recommendation would be:

1. Replying to a Twt that has no initial Subject must itself have a Subject of the form (hash; url).
   

This way it’s a hint to fetching clients that follow B, but not A (in the case of no mentions) that the Subject/Root might (very likely) is in the feed url.

@bender@twtxt.net Fuck I meant “bugs” 🐞 Geez 🙄

@kat@yarn.girlonthemoon.xyz Unless you’ve found buds in this branch it should be fine 😆 Um running yhe dame!

@movq@www.uninformativ.de Lwt me think on this.

@kat@yarn.girlonthemoon.xyz Nope it’s totally fine 🤗

@kat@yarn.girlonthemoon.xyz No new peers shoyls show up automatically.

@sorenpeter@darch.dk You’re welcome 🤗 We’ll run into each other again. I’m sure! 🤞

@kat@yarn.girlonthemoon.xyz Well some! 🙌

@thecanine@twtxt.net Yeah this is where I think all the hype really falls down. It’s all just a really really expensive search engine and auto-complete 🤦‍♂️ That’s it!

@kat@yarn.girlonthemoon.xyz MinIO is a good choice for a self-hosted Object Storage (compatible with S3 APIs) 👌

@kat@yarn.girlonthemoon.xyz Don’t be nervous, I make sure I test the shit™ out of things before anyone else does 🤣

Hello @Yarn.social@yarn.social 👋 (testing something)

@thecanine@twtxt.net Sorry, but you were expecting what now?! 🤣

I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We’ve thrown this “argument” around in support of some of the proposals, and I just don’t buy it (sorry). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.

@eapl.me@eapl.me I honestly believe you are overreacting here a little bit 🤣 I completely emphasize with you, it can be pretty tough to feel part of a community at times and run a project with a kind of “democracy” or “vote by committee”. But one thing that life has taught me about open source projects and especially decentralised ecosystems is that this doesn’t really work.

It isn’t that I’ve not considered all the other options on the table (which can still be), it’s just that I’ve made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and don’t consider all the possible things that could go wrong.

@bender@twtxt.net ROFL 🤣

@bender@twtxt.net How does it work? 🤔