@lyse@lyse.isobeef.org Oooooh, never seen that before. 😲 Either white-balance doing funny stuff or unusual “filtering” through those clouds. 🤔

Honestly for these types of services, there probably isn’t much point, as the layer4 module in Caddy doesn’t do inspection/filtering anyway I think? 🤔

I’m also thinking of adding eye-off icon next to every Twt that, when clicked, hides that feed (tooltip: “Hide this feed”). This would work with the filters as a “temporary additive filter” to restrict/control the current view.

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.

Fin de semana: ¡A jugar!
#catsoftwtxt

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 🧐

En estos momentos, no sé si un dios le está pidiendo que libere su pueblo felino o está mirando una paloma
#catsoftwtxt

¿Me rascas detrás de la orejita?
#catsoftwtxt

Sol y caja, ¿qué más se puede pedir?
#catsoftwtxt

No hay luz pero no me importa. En la vida hay que focalizarse en cazar las plumas al final del palo. El resto es secundario.
#catsoftwtxt

Mi oscuro secreto en las videoconferencias
#catsoftwtxt

@bender@twtxt.net Exactly. I suspect it was because of sqlitebrowser also accessing the database in parallel to debug the original issue.

So far, I have not found the exact reason why some replies don’t show up. When I do not filter for unread messages and show all, though, I actually see them. So, there’s that.

Posando para el pasaporte
#catsoftwtxt

💩
#catsoftwtxt

• Hace mucho solecito para dormir. -
  #catsoftwtxt

@bender@twtxt.net I was a bit confused at first what that is: Apparently, it’s the source code of Altair BASIC: https://gizmonaut.net/soapflakes/EXE-199711.html

(Of course they have a user agent filter. 😂 Can’t download that PDF with wget.)

Baldo en el universo Ghibli
#catsoftwtxt

• Inspección terminada: no hay ratitas 🐭, se puede sentar. -
  #catsoftwtxt

“it is very easy to filter or ignore it” This is the interesting part for legacy clients, hehe

Joking aside, let’s see how it works in the wild!

@eapl.me@eapl.me I think the benefits do not outweigh the disadvantages. Clients would have to read and merge the information from 2 txt and a new metadata would have to be added with the address of this file.
Also, it is very easy to filter or ignore it.

-¡Un humano!-
#catsoftwtxt

Siesta felina
#catsoftwtxt

Junta de vecinos: organizando los turnos para maullar por la noche.
#catsoftwtxt

• Da igual lo que digan: siempre serás un black panther. -
  #catsoftwtxt

@andros@twtxt.andros.dev I’m all for elegant solutions. I prefer when the computer helps me to really achieve my goal and solve it completely, not where I still have to manually filter a list by hand. Anyway. :-)

@eapl.me@eapl.me Yeah, you need some kind of storage for that. But chances are that there’s already a cache in place. Ideally, the client remembers etags or last modified timestamps in order to reduce unnecessary network traffic when fetching feeds over HTTP(S).

A newsreader without read flags would be totally useless to me. But I also do not subscribe to fire hose feeds, so maybe that’s a different story with these. I don’t know.

To me, filtering read messages out and only showing new messages is the obvious solution. No need for notifications in my opinion.

There are different approaches with read flags. Personally, I like to explicitly mark messages read or unread. This way, I can think about something and easily come back later to reply. Of course, marking messages read could also happen automatically. All decent mail clients I’ve used in my life offered even more advanced features, like delayed automatic marking.

All I can say is that I’m super happy with that for years. It works absolutely great for me. The only downside is that I see heaps of new, despite years old messages when a bug causes a feed to be incorrectly updated (https://twtxt.net/twt/tnsuifa). ;-)

FreeBSD and hi-fi audio setup: bit-perfect, equalizer, real-time
A complete guide to configuring FreeBSD as an audiophile audio server: setting up system and audio subsystem parameters, real-time operation, bit-perfect signal processing, and the best methods for enabling and parameterising the system graphic equalizer (equalizer) and high-quality audio equalization with FFmpeg filters. Linux users will also find useful information, especially in the context of configuri … ⌘ Read more

• Tenemos que hablar sobre las raciones “recomendadas”. -
  #catsoftwtxt

#catsoftwtxt

• ¡Que frío! Me tiemblan hasta los bigotes.-
  #catsoftwtxt

• ¿A qué juego ahora? -
  #catsoftwtxt

I received a tad over four hundred e-mails during my three and a half weeks vacation. That’s actually really good, I expected way more. It just would have been nice if some bot e-mail addresses hadn’t changed and hence slipped through my sorting filter rules in the first place.

Retocada en blanco y negro. Ahora es más adorable
#catsoftwtxt

Montando en elefante
#catsoftwtxt

• Silla ocupada.-
  #catsoftwtxt

¿Me das mimos?
#catsoftwtxt

@prologic@twtxt.net No I’m not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter@darch.dk already did with the nick = domain case. (unless I’m missing the point)

No te quito el ojo
#catsoftwtxt

#catsoftwtxt

• ¡Feliz navidad! -
  #catsoftwtxt

Gato bola 2: ahora la cosa se pone negra
#catsoftwtxt

-¡Muy buenos días a todos los felinos! Son las 5 am y arrancamos con otra edición de recordar el desayuno a nuestros dueños.-
#catsoftwtxt

Yes it work: 2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

-¡Se ha caído la pelota al suelo! Yo te salvaré.-
#catsoftwtxt

#catsoftwtxt

#catsoftwtxt

#catsoftwtxt

• Hoy tengo muchas ofertas. Es el black cat friday -
  #catsoftwtxt

Su juguete favorito
#catsoftwtxt

Been curious to see if can filter out my access.log file and output a list of my twtxt followers just in case I’ve missed someone … I came up with this awk -F '\"' '/twtxt/ {print $(NF-1)}' /var/log/user.log | grep -v 'twtxt\.net' | sort -u | awk '{print $(NF-1) $NF}' | awk '/^\(/' spaghetti monster of a command and I’m wondering if there’s a more elegant way for achieving the same thing.