@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:
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.
@lyse@lyse.isobeef.org on emacs i use elpher
@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.
@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.
@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")
robots.txt
file. only noticed it because the OpenAI bot was hitting me with a lot of nonsensical requests. here is the list from last month:
@bmallred@staystrong.run i really need to sit down and add some rate limiting to be honest.
robots.txt
file. only noticed it because the OpenAI bot was hitting me with a lot of nonsensical requests. here is the list from last month:
@lyse@lyse.isobeef.org yeah, i have the following as well:
User-agent: *
Disallow: /
now i some middleware that looks at the header, and if they are polite enough to include “bot” in the user agent, they politely get a 404 response.
@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
robots.txt
file. only noticed it because the OpenAI bot was hitting me with a lot of nonsensical requests. here is the list from last month:
@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
@prologic@twtxt.net @xuu@txt.sour.is@movq@www.uninformativ.de Oh man this made my morning!
Did you want to mine Chia? Or Twtxt Coin? 😂
@lyse@lyse.isobeef.org That is how it feels for sure
@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 So they say. :-D
@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.
Look at the size of this coffee!!! 😱