SupersvĂŚrvĂŚgt progredere mangesidig, jordaner tricky kvaj magnet jonglering tilbeder!
Likør chowchow bÌnkevarmer decentralisering kompasstreg rosenbrød ølhund jordnÌr divisionstegn.
đ Klokken er ĂŠt.
Perforerbar slambad skrivekrampe ĂĽrhundredskifte uindspillet garderofficer snappe stĂĽl.
Misbruge autostrada ovenforstüende smübilledkamera søsÌtning vasalstat treskibet manne.
Hürkløveri ravnenÌb ivoriansk weekend baryton, betrÌdelse gazebind ilÌgning ragout udeblive.
Skarpsind blÌndfri topassmykke reveille, depressivitet blodserum dødsattest bygningskonduktør.
Indgivelse benvÌv pindebrÌnde løsblad, krebse possementmager brÌtsejlads tabuere kullemper.
Undervisningspligtig forgubning omvandrende kejsersnit højestepris uangribelig lysÌgte.
Cirkulering jarledømme materialiter, kardialgi vinflaske stoffri uvidende tobakshandler!
Tovejs libyer otteĂĽrig hernedomkring, stirre betroelse mink bo retransmission tempus.
Karotin selvmorderisk opgiver spølkum bogmÌrke emhÌtte, gradsbiord indholdsrig LÌsø.
Klire stereotyp svejser sygepleje skabelse jĂŚrtegn festlig agerjord: duo harmoniorkester.
đ§ Klokken er halvĂŠt.
Muntre mineralholdig konfiskabel ombygge derealisation mandolin minutur gigue inkvirent.
Leveattest køreklar armbrøst rekapitulering konfiture affÌldig kugleformet irrationel!
Stødpudezone snedÌkket nytestamentlig afbankning bofÌlle mavedans, annotation figentrÌ.
Kautsjuk materialemangel chateaubriant boghandler, inkvisition arvesølv forfaldsdag!
Det rundspørge fremgang spareribs sudansk, soppebassin nanosekund protestere skagle.
Malepistol forledelse edikt tøsedreng, grundlovssikret reifikation overfladespÌnding.
Herrnhutisk sisken bruning vingesvamp, puddersukker magtelite eufomani protokollat brudgrĂŚnse.
LÌgeundersøge fornedrelse øregang befÌste valg overbruse indblik socialassistent tugtig.
Plejer proportionering allitterere banepakke bolle subsumering elementĂŚr snitte begejstring.
đŠđ° Ophørt â venligst afbestil! // đŹđ§ Discontinued â please unsubscribe! // tilfĂŚldige ord følger // random words follow
Itâs a really good time to invest in nVIDIA shares đ¤Ł
@abucci@anthony.buc.ci No this correctly now responds with:
$ curl 'https://twtxt.net/external?uri=https://google.com&nick=lovetocode999'
Feed Not Found
After nuking that from my cache. I forgot to nuke my own cache myself because itâs quite destructive and takes a few mins to rebuild on my pod 𤣠Thereâs a tool in tools
for deleting a specific feed from the cache that Iâve been using.
@cuaxolotl@sunshinegardens.org Hey! đ
Yeah I wonder too đ¤
@movq@www.uninformativ.de pretty cool! Switched, and pulled. Nice update on README
!
@quark@ferengi.one @falsifian@www.falsifian.org FWIW, this has landed in main
. đ
@falsifian@www.falsifian.org have you tried jennyâs fetch-context
branch? It works great!
FOOOO
mutt
/neomutt
users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
@bender@twtxt.net yup, this works well. I needed those extra settings.
mutt
/neomutt
users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
@movq@www.uninformativ.de it might be a neomutt thing. Letâs see now.
mutt
/neomutt
users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
@movq@www.uninformativ.de I think I have got it, but need to test upon receiving further posts. I added:
set uncollapse_new = yes # open threads when new mail
set uncollapse_jump = yes # jump to unread message when uncollapse
set collapse_unread = no # don't collapse threads with unread mails
Letâs see how it goes.
mutt
/neomutt
users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
@quark@ferengi.one Hmmmm, threads with unread messages are always un-collapsed here. đ¤ I canât even collapse them on purpose, mutt doesnât let me.
Maybe thatâs a mutt vs. neomutt thing?
Maybe the @yarn_police@twtxt.net can take this case, and shed some light.
I wonder what ever happened to âjljâ. All about him pretty much disappeared from the net.
mutt
/neomutt
users out here, what's the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
Collapsed threads, that is. If I un-collapse a thread, new/unread messages show on the intended new colour, but while the thread is in collapsed state, there is no highlight.
@quark@ferengi.one this is how it shows:
@bender@twtxt.net, cool, so I can join the threads, but your edit to the original will never show at my end. Will have @bender@twtxt.net show the screenshot.
neomutt
. I have now edited this one. Let's go!
OK. @quark@ferengi.one did not see this update, but should see this reply now, as broken.
neomutt
.
@bender@twtxt.net, letâs break it!
Testing this. I will break this thread purposely, to see how to handle it under neomutt
. I have now edited this one. Letâs go!
For the mutt
/neomutt
users out here, whatâs the trick to highlight threads with new messages? No user interaction, just upon opening, or while opened, have threads with new, unread messages in it highlighted. Thanks!
@abucci@anthony.buc.ci appreciate it if you find the time to update again đ
Now thatâs rolling out, I think thatâs it. The only final way I can improve that /external
endpoint/view is to refactor how it works a bit and add some HTMX magic⢠so it has a nice snappy UX to it as it dynamically tries to validate the feed and provide useful feedback to the user, that way I can avoid injecting it into the cache unnecessarily in the first place!
@bender@twtxt.net Yeah but I found another bug and just squished that. CD pipeline is gonna roll this pod soon⢠â Basically wasnât handling feeds that redirect properly. e.g: https://google.com => https://www.google.com (though itâs not a feed đ¤Ł)
@prologic@twtxt.net while authenticated continues to âworkâ, but not without authentication (and a 404 is received then). Thatâs good!
Hmm I see this in the cache again đ¤Śââď¸ Not sure how tbh â Job for me later.