@falsifian@www.falsifian.org Hahaha, thatās sick, I love it! :-D I envy you a bit. On the other hand, I have to admit Iām glad that I donāt have to chisel down giant blocks of ice from the house.
@lyse@lyse.isobeef.org I am a big fan of āobviousā math facts that turn out to be wrong. If you want to understand how reusing space actually works, you are mostly stuck reading complexity theory papers right now. Ian wrote a good survey: https://iuuk.mff.cuni.cz/~iwmertz/papers/m23.reusing_space.pdf . Itās written for complexity theorists, but some of will make sense to programmers comfortable with math. Alternatively, I wrote an essay a few years ago explaining one technique, with (math-loving) programmers as the intended audience: https://www.falsifian.org/blog/2021/06/04/catalytic/ .
@falsifian@www.falsifian.org Mate, what an amazing video, holy cow! :-D We only get complete jokes of icicles compared to what you had there ealier today. Itās a giant wall. For how many days did that grow on your roof?
@lyse@lyse.isobeef.org Still melting!
@falsifian@www.falsifian.org Oh, thatās neat! Interesting how āobviouslyā isnāt all that obvious at all, even to the contrary. I reckon I have to read up on that subject on the weekend. :-)
I like how Ianās and your photo complement each other, winter and summer join forces for something special. :-)
@falsifian@www.falsifian.org Wooooaaaahhh! That is BY FAR the biggest icicle Iāve ever seen. Really cool! :-) How long did it take to melt in your sink? The video download is still dripping in, looking forward to that.
twtxt
, the microblogging for hackers and friends...
@eapl.me@eapl.me I couldnāt care less about ActivityPub, but twtxt is the thing for hackers by design. Thatās the appealing part for me, personally. I actually do enjoy that not everybody and their dogs are here. :-)
@thecanine@twtxt.net I agree!
@movq@www.uninformativ.de @prologic@twtxt.net I donāt know, I donāt see this happening all that often. Very rarely. The problem I encounter much more often is that tech folks are blindly adopting every new hype without thinking the slightest bit what the consequences might be.
But maybe that also means Iām one of these ātold you soā guys. Not sure.
Today is an important day. We have a new extension: Direct message šŖšØļøšš„³ā¤ļø
https://twtxt.dev/exts/direct-message.html
#twtxt
@sorenpeter@darch.dk Sorry, I realized that shortly after posting. Hereās another attempt to post the images:
@eapl_en@eapl.me Good idea
4, but I like the idea of @eapl_en@eapl.me
What would you like the new twtxt logo to be?
Comments: https://git.mills.io/yarnsocial/twtxt.dev/issues/9#issuecomment-18960
@prologic@twtxt.net All the URL are missing the protocol part (https://
) and my markdown parser does not know how to handle but I see yarnd does it just fine.
@falsifian@www.falsifian.org
it look like your markdown image tags are missing the protocol part (https://
) so they donāt render at least on my server: https://darch.dk/timeline/conv/3vtnszq
@prologic@twtxt.net Have you tried Googleās robots.txt report? https://support.google.com/webmasters/answer/6062598?hl=en . I would expect Google to be pretty good about this sort of thing. If you have the energy to dig into it and, for example, post on support.google.com, Iād be curious to hear what you find out.
Something interesting to think about for twtxt
, the microblogging for hackers and friendsā¦
The biggest challenge of ActivityPub is that itās too technical to easily explain to regular people. Nobody is interested in a jargon-laden diatribe about servers and federation. When simple questions have overly complex answers, people tend to switch off.
https://activitypub.ghost.org/your-thoughts-on-onboarding/
@bender@twtxt.net @prologic@twtxt.net the markdown list in #jr6ywrq is a ālooseā list, e.g. https://github.com/erusev/parsedown/issues/474#issuecomment-280874843
My markdown parser (parsedown PHP) renders the list with p
-tags also.
@andros@twtxt.andros.dev Thank you :-)
@andros@twtxt.andros.dev screenshots plz :=!
Yesterday I was doing a lot of research on how #hyperdrive and the #holepunch project work. Would it be possible to use it to make #twtxt an easier gateway for new users? Could we stop using web servers?
My conclusion: We would end up being a #nostr. On the one hand it would become more complex to use, it would force the user to have software installed, and on the other hand the community would need a central proxy to make the routes accessible via HTTP. In other words, itās not a good idea.
However, itās an AMAZING technology. I want to start playing with it.
@prologic@twtxt.net š¤£š¤£š¤£ thanks! I didnāt even notice š
@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.
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.
@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. :-)
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.
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
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
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
@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 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.
@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.
@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")
@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
@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.isDid you want to mine Chia? Or Twtxt Coin? š
@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 ;-)
@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.
@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.
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
@<url>
. Submitting this writes @<domain url>
instead of @<nick url>
in the feed.
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.
@<url>
. Submitting this writes @<domain url>
instead of @<nick url>
in the feed.
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!
@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.
@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. :-)
@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.
@movq@www.uninformativ.de That is a good one! It took me 15 minutes to get it. š¤