@prologic@twtxt.net It seems like the typical problem of an unneutered cat 😂

@prologic@twtxt.net That boycott didn’t last very long, eh!?

Yeah, sounds like another hype train arriving at the station.

@doesnm@doesnm.p.psf.lt I’ll let you know once it reaches a point where it might be barely usable by someone else than myself. There are long ways to go, though. Right now, you don’t wanna even look at it. :-)

Thinking about trying tt. If it really usable i will abandon twtxtdon (service to read twtxt feeds from mastodon client), which currently has only authorization implemented

It would appear that Google’s web crawlers are ignoring the robots.txt that I have on https://git.mills.io/robots.txt with content:

User-agent: *
Disallow: /

Evidence attached (see screenshots): – I think its the the Small Web community band together and file a class action suit(s) against Microsoft.com Google.com and any other assholes out there (OpenAI?) that violate our rights and ignore requests to be “polite” on the web. Thoughts? 💭

I’m continuing my tt rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I don’t wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.

The very first dialog I added is viewing the raw message text. Unlike in @arne@uplegger.eu’s TwtxtReader, I’m not able to include the original timestamp, though. I don’t have it in its original form in the database. :-/

Next up is a URL view.

@movq@www.uninformativ.de That’s what I immediately thought as well. :-D @eapl.me@eapl.me Unfortunately, no fancy buttons. What does your model do?

Added support for uploading images to to #Timeline

Image

@prologic@twtxt.net Of course you don’t notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinley’s message from 2023-01-09T22:42:37Z. It has “[Scheduled][Scheduled][Scheduled]“… in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I’ve explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.

@eapl.me@eapl.me I like this idea. Another option would be to show a limited number of posts, with an option to see the omitted ones by user. Either way, I wonder how well that works with threading.

@movq@www.uninformativ.de Ja, völlig behämmert. Schade, vertane Chance für einen „Doch“-Knopf.

@prologic@twtxt.net Tolerant yes, but in the right places. This is just encouraging people to not properly care. The extreme end is HTML where parsers basically accept any input. I’m not a fan of that. Whatever.

@prologic@twtxt.net The issue is that all bracketed text in the entire feed has been duplicated again two days ago. The bug is not fixed. Or it’s a new one.

@movq@www.uninformativ.de I can relate to that. :-/

Thanks @prologic@twtxt.net @eapl_en@eapl.me @lyse@lyse.isobeef.org ! I take note

@aelaraji@aelaraji.com You can update the package 😀

@andros@twtxt.andros.dev it seems your GtS has issues:

Warning! It looks like trusted-proxies is not set correctly in this instance’s configuration. This may cause rate-limiting issues and, by extension, federation issues.

If you are the instance admin, you should fix this by adding 10.66.66.1/32 to your trusted-proxies.

@andros@twtxt.andros.dev I suggest to not touch it and work on a different project instead. :-D

No, in all seriousness, that’s a tough one. Try to figure out the requirements and write tests to cover them. In my experience, if there is no good documention, tests might also be lacking. It goes without saying that you have to understand the code segments first before you can begin to refactor them. Commit even earlier and more often than usual, this will help you bisecting potentially introduced bugs later on. Basically baby steps.

But it also depends on the amount of refactoring required. Maybe just scrap it entirely and start from scratch. This might not be feasible due to e.g. the overall project size, though.

@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). ;-)

Exactly, @bender@twtxt.net, just like yours and prologic’s, too. :-( Subsequent Brackets Considered Harmful™.

@eapl.me@eapl.me Read flags are so simple, yet powerful in my opinion. I really don’t understand why this is not a thing in most twtxt clients. It’s completely natural in e-mail programs and feed readers, but it hasn’t made the jump over to this domain.

@mckinley@twtxt.net Yeah, all this JS and HTMX garbage messes up a lot of things which used to work better in the earlier days.

@prologic@twtxt.net @xuu@txt.sour.is There:

Image

Just search for ][ in https://twtxt.net/user/mckinley/twtxt.txt and you’ll see.

@movq@www.uninformativ.de @prologic@twtxt.net @bmallred@staystrong.run @andros@twtxt.andros.dev Thank you all! I don’t have emacs installed, so I’ll try lagrange and see. According to my shell history, I must have played around with amfora ages ago.

@xuu@txt.sour.is People should just fix their feeds. :-)

@aelaraji@aelaraji.com Sorry I’m late! I still have to work on the mention system, I don’t get some of the messages. I’ll look into your case and get back to you shortly 😄
If it’s a problem that ruins your experience, don’t hesitate to create an issue.

@xuu@txt.sour.is Thank you! A common mistake is to see Emacs as a text editor but it’s a Lisp interpreter with a text editor (among other software), so the limit is your imagination 😋. I’m glad you like it! 🙌

i made a little twtxt feed fixer for when a feed uses other whitespace instead of tabs.

https://git.mills.io/yarnsocial/go-lextwt/pulls/32

@lyse@lyse.isobeef.org Where? 🧐

@prologic@twtxt.net the code block is the cause of https://txt.sour.is/twt/zn2kg7q

and the second? i get POST errors when i try to submit the webform.

@lyse@lyse.isobeef.org c

@andros@twtxt.andros.dev lol nice! emacs is wild. text and graphics all inline.

@andros@twtxt.andros.dev Broke on me for having alt-urls I think 🥲

twtxt---profile-layout: Wrong type argument: char-or-string-p, ("https://aelaraji.com/twtxt.txt" "gemini://box.aelaraji.com/twtxt.txt" "gopher://box.aelaraji.com/0/twtxt.txt")

@movq@www.uninformativ.de Yeah, maybe. What browsers are you using again for these two?

@mckinley@twtxt.net And there is the bracketed text duplication bug again… Actually with lots of twts. Did you edit a twt? Do you remember? /cc @prologic@twtxt.net

@mckinley@twtxt.net b

@bmallred@staystrong.run Surprisingly, my

User-agent: *
Disallow: /

seems to work. Or maybe those bastards change their user agent and claim to be someone nice. In any case, I just added a bunch of

location = /robots.txt {
    add_header Content-Type text/plain;
    return 200 "User-agent: *\nDisallow: /\n";
}

in my nginx config. No need for any bot to visit, crawl and index most of my sites.

@movq@www.uninformativ.de Photographic memory, eh?

@movq@www.uninformativ.de I also thought that I have a new Linux friend the other day. But it was just a fake KDE look from Redmond. :-(

Totally agree @jost@jost.sdfeu.org @prologic@twtxt.net

I have uploaded a new version of #twtxtel 🥳. It’s now possible to view profiles, either your own or others. #twtxt #emacs

Video

Did you want to mine Chia? Or Twtxt Coin? 😂

@jost@jost.sdfeu.org Happens to everybody. 😂 Well, except for a few people. I have this colleague at work who remembers everything. It’s scary. 😅

@jost@jost.sdfeu.org Yeah, this AI crap is a big reason not to blog.

@andros@twtxt.andros.dev The article is a good reminder of the true blogging mindset. But let’s try to think beyond. 2 ideas: (1) writing “forces clarity, structures your thoughts, sharpens your perspective”. But it also generates thoughts in the sense of Heinrich von Kleist (1805). (2) You’re writing for “the future you, one right person, one day” but you are also writing for the AI. The idea of AI as an audience.

@movq@www.uninformativ.de It happens to the best of us :-) On a more serious note: I’m relieved to hear that I’m not the only one who is completely perplexed by his own projects when returning back to them after a short hiatus.

@movq@www.uninformativ.de So they say. :-D

@prologic@twtxt.net Ha,ha :-) I do not maintain anything! In the context of that post I was just an ordinary citizen. So the ‘we’ refers twice to “we, the citizens of the Baltic States”. (Classical case of social media ‘talk at cross purposes’. Now I understand, why they do this Introduction-thing over on mastodon ;-)

@xuu@txt.sour.is Why? To both issues:

@prologic@twtxt.net we need to remove: https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/ast.go#L776-L784

apparently i can’t make the edit via gitea.. i am guessing its hitting one of your firewall rules.

@xuu@txt.sour.is da fuq?!

@andros@twtxt.andros.dev Awesome! I’ve seen the demo earlier on mastodon, things are getting better and better with each update 👌 Good luck!

I’m realizing that my performance bottleneck is @prologic@twtxt.net ! It is actually calculating the hash to make the replicas, and specifically users with very long feeds 😂 . I’m seriously thinking about enabling replies via configuration.

I have infinite scroll now! I can finally focus on replies and mentions 😋

Video

Look at the size of this coffee!!! 😱

Well, that’s another bug: The search https://twtxt.net/search?q=%22LOOOOL%2C+great+programming+tutorial+music%22 yields the wrong hash. It should have been poyndha instead.

@prologic@twtxt.net hmm this isnt right..

@thecanine@twtxt.net Lol… I just don’t change my default profile pictures. (Well, only when my teammates ask me to.)

@doesnm@doesnm.p.psf.lt Haha, that’s great! :-D

hmm interesting work here.. ill give it a look.. @lyse@lyse.isobeef.org do you know if it is even storing the url into the AST object? afair the code to parse tags url should be the same as the mention url.

@thecanine@twtxt.net Some precious cloud space. Probably the Atlassian one.

How does one end up with an avatar of that weird size to begin with? :-D

@falsifian@www.falsifian.org Do you want me to reconfigure my nginx to look at the User-Agent in order to serve you a different file for the time being? ;-) Good luck with your paper!

@movq@www.uninformativ.de Open-plan offices are just a giant mistake. I’ve never seen a single working one where people can actually concentrate. Except when I was the first one around in the morning.

@prologic@twtxt.net @bender@twtxt.net Looks like something for /dev/null.

@movq@www.uninformativ.de Schön mal noch eine Querreferenz zu haben. Danke!
Beide O-Maten haben ähnlich Ergebnisse für mich. Das bestätig mich in meiner bereits getroffenen Wahlentscheidung für den 23. Februar.

@arne@uplegger.eu Der Real-O-Mat ging neulich auch rum: https://real-o-mat.de/ (Ändert bei mir im Ergebnis nix, die Antworten/Begründungen sind aber interessant(er).)

While I now have a somewhat working fix for it in yarnd (https://git.mills.io/yarnsocial/yarn/pulls/1232), I also have the feeling that I should fix literal formatting in lextwt as well. This also uncovered more bugs I believe: https://git.mills.io/yarnsocial/go-lextwt/pulls/28

But then there is also the question why the textarea is populated with @<url> in the first place rather than @<nick url> or yarnd’s own @nick@domain/@nick syntax. It indeed has to do something with whether I follow the mentioned feed or not.

Anyway, something to investigate for future Lyse or maybe @prologic@twtxt.net and/or @xuu@txt.sour.is. G’night!

@movq@www.uninformativ.de This time it works! (For the first time). Using mutt, yes, and the config is yours. I’ll contact you later, when I have more data. Some time needed to experiment. Thanks!

@jost@jost.sdfeu.org Hmm, not really, no. Could you share your mutt config? (Are you using mutt?) Feel free to send me an email, if doing this over twtxt doesn’t work (yet). You can find the address on https://www.uninformativ.de/contact.html ✌️

@bender@twtxt.net @prologic@twtxt.net I can reproduce this locally, too. But it doesn’t matter if I follow the feed or not. With JS enabled, hitting “Reply” opens a textarea with @<url>. Submitting this writes @<domain url> instead of @<nick url> in the feed.

However, when I have JS disabled, “Reply” jumps to the top of the page, but the the textarea is at the bottom. So, after scrolling down, the textarea is not filled with anything. Which is expected I reckon. Entering @nick@domain or just @nick resolves to the correct @<nick url> in the feed.

@prologic@twtxt.net @movq@www.uninformativ.de I sadly agree.

@movq@www.uninformativ.de Whether in the office or at home, I get nothing done. ;-) Well, while this is almost true, I actually tried to respond to the other thread I started myself, but starting the editor it switched immediately to this one. Any idea why this happens?

@movq@www.uninformativ.de So true! Either I’m hanging around with my direct teammates socializing in person in a meeting room or some other workmates are making so much noise in the open-plan office that I cannot concentrate at all. In any case, completely unproductive. :-D Luckily, I very rarely have to go to the office.

@bender@twtxt.net Bwhahahahaaaahaaaahaaaaahaaaaaaa! :-D Oh man, my cheeks are hurting and eyes are watering. :-D I love it!

@falsifian@www.falsifian.org Yes! The first part about the history was my favorite. Not that the second one about finding life on Mars wasn’t interesting, no, not at all! But maybe it’s just that Earth is a bit more relatable. :-) I’m sure they will dig up something eventually.

@twtxt.net@twtxt.net right. I don’t follow you. I will restart following you once Yarn has fixed this problem. :-P

@bender@twtxt.net Every base is base 10.

@lyse@lyse.isobeef.org Thanks for sharing. I really enjoyed it. The beginning part about the history of life on Earth was fun to watch having just read Dawkin’s old book The Selfish Geene, and now I want to read more about archaea. The end of the talk about what might be going on on Mars made me a bit hopeful someone will find some good evidence.

@movq@www.uninformativ.de The light pollution map reports red for my town. That’s fairly accurate, I’d say. The view from home is not all that great. Yeah, I can see Ursa Major and a bunch of other stars. Maybe even some satellites. But there’s definitely a sky glow at the horizon.

When I leave town, I can see a bit more. However, it doesn’t compare to the alps or even some rural parts in Australia. The latter was by far the craziest I’ve ever seen in my life. Looked like a space telescope photo in person. Soooooooooooooo many stars and the band of the milky way was easily visible to the naked eye. Up until then, I didn’t even know this was remotely possible down on earth. Absolutely stunning. :-)

@twtxt.net@twtxt.net Octal 31 = Decimal 25

@johanbove@johanbove.info Ours also inlcudes the streaming portal https://www.filmfriend.de
It’s nice to watch some arthaus and off main stream movies.

@sorenpeter@darch.dk It depends on your requirements. If you just want to put your code somewhere for yourself, simply push it over SSH on a server and call it good. That’s what I do with lots of repos. If you want an additional web UI for read access for the public, cgit comes to mind (a mate uses that). Prologic runs Gitea, which offers heaps more functionality like merge requests.

@jost@jost.sdfeu.org Hello jost!

@prologic@twtxt.net Go just moved back to second place. :-)

@movq@www.uninformativ.de Nice! I would have missed the plane if you hadn’t pointed it out. :-) Venus is very visible these days. When a mate and I went on a night walk during clear sky this week, the night sky looked really great, it was easy to spot the second planet. We got lucky, ISS just passed above our heads, too. Most of the week, it was cloudy, though.

@movq@www.uninformativ.de Hahaha, that’s a good one! :-D I came across this one before, but couldn’t remember the answer.

@prologic@twtxt.net I’m gonna give you a hint: Octal, decimal. 😅

@movq@www.uninformativ.de That is a good one! It took me 15 minutes to get it. 🤓

@prologic@twtxt.net In the EU there are Laws, Rules and Regulations for many things. I’m not an expert, but your case may sound like it could match to the EU Digital Services Act.

[…] for example, the obligation to establish points of contact for authorities and citizens […]

@lyse@lyse.isobeef.org Es ist immer noch so ähnlich. Da kommen so viele verschiedene Ebenen innerhalb und außerhalb der TYPO3-Umgebung zusammen, dass man sich wundert.

Und die TYPO3-Core-Entwickler nehmen gefühlt jeden fancy Shice mit, den sie gerade finden. Das reißt dann immer wieder Prozesse ein oder es muss ein gigantischer Aufwand betrieben werden, damit “grundlegende” Funktionen wieder hergestellt werden.
In den Kommentaren ist dann immer nur zu lesen “Tja, Pech. Gibt’s nicht mehr. Sei froh, dass wir ‘ne undokumentierte Schnittstelle dazu im Code versteckt haben. Bau’s dir selbst.”
Und der OpenSource-Gedanke ist bei einigen Erweiterungen (die als Quasi-Standard gelten) auch nur noch zu erahnen. Da müssen teilweise Abos abgeschlossen werden, damit einige Funktionen genutzt werden können.

Es wird auf jeden Fall nie langweilig.

@andros@twtxt.andros.dev Wazzaaaaa… https://www.youtube.com/watch?v=NsJLhRGPv-M

That’s my alt-feed by the way! 😉

@lyse@lyse.isobeef.org The one in question is more like the javascript version for unwrapping errors when accessing methods.

 const value = some?.deeply?.nested?.object?.value

but for handling errors returned by methods. So if you wanted to chain a bunch of function calls together and if any error return immediately. It would be something like this:

b:= SomeAPIWithErrorsInAllCalls()
b.DoThing1() ?
b.DoThing2() ?

// Though its not in the threads I assume one could do like this to chain.
b.Chain1()?.Chain2()?.End()?

I am however infavor of having a sort of ternary ? in go.

PS. @prologic@twtxt.net for some reason this is eating my response without throwing an error :( I assume it has something to do with the CSRF. Can i not have multiple tabs open with yarn?

@lyse@lyse.isobeef.org would it work wit cats instead? there has been a whole flock of them in the neighborhood the last couple of days, one female and a gazillion males taking turns 😅 … at least they’d be good for something other than their non-stop after midnight opera 😂

@prologic@twtxt.net Which one? I don’t mind the ternary operator at all. In fact, I often find myself missing it in Go. I don’t find the two alternatives particularly elegant:

foo := "eggs"
if bar {
    foo = "spam"
}

Or:

var foo string
if bar {
    foo = "spam"
} else {
    foo = "eggs"
}

To my eye, this just would look a lot nicer:

foo := bar ? "spam" : "eggs"

Or at least as the Pythons do it:

foo = "spam" if bar else "eggs"

The ternary operator especially shines with relatively short expressions.

@arne@uplegger.eu Ohjemine, TYPO3! O_o Lass mich schreiend davonlaufen!

Mit dieser absoluten Katastrophensoftware vor dem Herrn haben wir mal ein Studienprojekt gemacht. Die hat alle Vorurteile komplett übererfüllt. Angefangen von Fehlerseiten, die statt 4xx oder dergleichen immer mit HTTP 200 ausgeliefert wurden oder auch, dass das generierte HTML leider einfach ungültig war. Über die Implementierung von Löschen durch einen Deleted-Schalter in der Datenbank, das Speichern von Passwörtern im Klartext bis hin zu völlig umständlichen Bedienungskonzepten. Alles hat immer brutal viele Schritte gebraucht. Das Zeilennummernrumgeeier im TYPO-Script erinnerte eher an Basic. Uns kam es auch so vor, als ob man damit nicht ernsthaft was sinnvolles machen könnte.

Zu allem Überfluss hatte irgendwer noch ein ganz hundsmiserables Buch ausgegraben, das als Vorbereitung dienen sollte. Ich kann mich zum Glück weder an den Titel noch den Autor erinnern, aber ich weiß noch, wie das komplett inkonsistent geschrieben war. Anfangs gabs mehrere Seiten zu Unicode und UTF-8 wurde angepriesen, aber alle Beispiele haben dann auf ISO-8859-1 gesetzt. Gezeigter Beispielcode war häufig unterste Schublade. Selten hab ich so merkwürdige Erklärungen gelesen: „Wenn Sie die Sicherheitswarnhinweise stören, kommentieren Sie doch bitte im Quelltext die die()-Funktion in $ZEILE aus.“ Oder ein anderer Klassiker: „Ausgeschrieben würde der Code wohl folgendes tun…“. War sich der Autor also nicht ganz sicher, ob sein Codeschnipsel vllt. doch in Wahrheit was ganz anderes tut.

Seit diesem gigantischen Trauma (das hat mich wirklich sehr nachhaltig geprägt, wie man Dinge nicht machen sollte) hab ich erfolgreich einen Bogen um das TYPO3-Universum gemacht.

Ich kann nur hoffen, dass es zwischenzeitlich ein wenig besser geworden ist. Aber Deinem Kurzbericht zufolge scheint da ja immer noch der Wurm drin zu sein. Mein Beileid! :-(

@skinshafi@thunix.net ❓📞🚫👻🔫

@arne@uplegger.eu Manchmal HASSE ich TYPO3! 💩

@doesnm.p.psf.lt@doesnm.p.psf.lt Huh? 🤔 I’m curious to what other features you’d want from a messaging app! Also, you can easily send in a couple of feature requests, the dev is pretty receptive 👌