Yeah I can’t figure out when I registered short circuit.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 😅
printf
?!)
@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?
Z
for UTC +00:00
- is that allowed in your specs?
Regarding url =
I would suggest to only allow one and the maybe add url_old =
or url_alt =
!?
I'm still not a fan of a DM feature, even thou it helps that i have now been split out into a separate feed file. Instead if would suggest a contact =
field for where people can put an email or other id/link for an established chat protocol like signal or matrix.
@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.
@<nick url timestamp>
) and having location based treading this way, might not break older clients, since they might just igonore the last value within the brackets.
@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! 👌
main
recently? 🤔
@kat@yarn.girlonthemoon.xyz Make sure you’re up-todate with main
🤣 I’m fixing little things here and there. Also please report bugs 🐞
yarnd
.
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™ 😉
yarnd
.
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.
tt2
from @lyse and Twtxtory from @javivf?
@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 😞