@prologic@twtxt.net Sorry I havenât seen your question before! and to answer your question, no, it wasnât hard at all. itâs a simple go build âŠetc. as instructed + scp twtd to remote + made a systemd service for it to (re)start automatically under a dedicated twtd user for lols. + poked at the Caddyfile to reverse-proxy a couple of paths and called it a day.
Too much info?
@david@daiwei.me @lyse@lyse.isobeef.org How about Augmented Ignorance ? it packs a better punch, doesnât it? đ
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
@movq@www.uninformativ.de Yes good I think we are too! đ
@david@daiwei.me Go down to âReleasesâ, thereâs a link to the CHANGES: https://movq.de/git/jenny/CHANGES.html
@lyse@lyse.isobeef.org Yeah, the feed names are legacy and I didnât want to set up redirect rules. (I canât really tell if anybody actually uses them âŠ)
Extracting the info from the CHANGES file would be nice. Maybe Iâll add that. :-)
@aelaraji@aelaraji.com @david@daiwei.me Hahaha, neither did I came across this before. :-D
@movq@www.uninformativ.de Similar to my Go IDE at work. GoLand hangs so often in this giant code base. :-D (But it could also be one or the other snake oil thatâs forcefully installed and fucks with me every day.)
@david@daiwei.me Hahaha! The thing is, it doesnât taste as good in summer as in winter for some unknown reason. Two or three decades ago I asked my grandma to bake some of her amazing gingerbread in summer. But she always refused, claiming that this only really works in winter. Of course, I didnât believe that. Finally, after years of begging and pleading, she finally made a tray. And to my surprise, she was right. It wasnât bad, no, no, not at all. It was really yummy. But the gingerbread in winter was just better. :-/
Maybe I should give it a shot myself. Perhaps she slightly changed the recipe on purpose. So that I will never break the tradition of seasonal food again. :-P It worked, at least I never asked her to bake gingerbread in summer again. :-D
Pretty cool, @thecanine@twtxt.net!
@movq@www.uninformativ.de Good question. Tarballs are probably not needed, but might be convenient for people who donât want to or can use a version control system. Not sure if there are non-techies who use your software. Tarballs for branches are overkill, though, I agree.
Looking at this more closely: As for the feeds, how about filenames âtags.atomâ and âcommits.atomâ? Unless, of course, they were already named like that before.
For the tags feed it would be cool to include the actual changelog entries to be more useful if somebody takes this approach to get notified of new versions. But that would mean you have to duplicate the changelog entry into the annotated tag. And then you canât fix changelog typos in the feed anymore. Alternatively, the feed generation would need to extract the section from the the CHANGES file. That has the benefit of automatically providing changelogs for past versions in the feed.
@david@daiwei.me Is this better? đ€ Pretty hard to keep this concise but also not miss anything. đ€ https://movq.de/git/jenny/
@david@daiwei.me Oh, that is a good idea. This could be included here, yeah. đ€
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
@prologic@twtxt.net Oh, yes, just for clarity: This wasnât a âpro GitHubâ argument. đ I wonât go back there (or to another âforgeâ).
I think weâre totally on the same page: Decentralized Git hosting is good, but we havenât solved the âcollaborationâ part yet. Or rather: We have to modernize it. The tools are already there, but (many) people donât want to use them and think theyâre clunky.
@david@daiwei.me Have you never seen or heard me say AI is basically Artificial Incompetence? đ€Ł
@GabesArcade@raw.githubusercontent.com those are getting harder and harder to come by these says. Everything is smart this, smart that and Artificial Ignorance powered now.
@david@daiwei.me It would appear so đ
@thoshi@yarn.thoshis.net I wouldnât bother if I were you đ Theyâre both fairly outdated protocols and very much an âsiloâ IMO. THey donât make very good places to host your Twtxt feed either.
@thoshi@yarn.thoshis.net Welcome to the Yarn.social / Twtxt ecosystem đ
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
And @lyse@lyse.isobeef.org is right. Not being on Github is a good thing IMO. Even when I was there with all my many projects, I basically got the same amount of âattentionâ as I do now. The only real way to gain more âattentionâ is to artificially play the âgameâ. You know. The stupid âStargazerâ one, and whatever you can to get into the âTop 10 Xâ charts. â But ultimately that doesnât buy you âqualityâ contributors or users or whatever. So itâs all pointless.
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
@movq@www.uninformativ.de So I see it slightly differently⊠Over the years I have recieved great contributions from the likes of yourself and @lyse@lyse.isobeef.org and the many forms of @bender@twtxt.net and his friends đ Hell even others along the way that have come and gone. Likewise I also think you have recieved many contributions to Jenny over the yeras in much the same way, perhaps not in patches, but user reports, feedback, etc.
So I think what Iâm saying here is this⊠Ever since leaving Github (like you), I find that my desire to continue to build up the community weâve built here and to contribute to grow and cultivate it is important to me. My desire to thwart and eliminate useless traffic like bots and ai even strongers.
I want to find a good balance.
@thecanine@twtxt.net Always love your work ! đ
Deleted some old no longer used pixelart from my galley and added this as an alternative version, of the sprite one.

@movq@www.uninformativ.de Sigh. :-(
@movq@www.uninformativ.de Oh, thatâs actually quite a bit. I didnât expect that. You definitely have useful things. :-)
Exactly, I now also send links to my fork. :-D
@dce@hashnix.club Yeah, but I havenât looked into this specific issue. I am very much anti-AI, but this particular thing might be human error. I donât know.
@lyse@lyse.isobeef.org Oh, Iâm sure theyâll keep hammering dead URLs for many years to come. These crawlers are 100% brain dead. And they donât even need to be smarter, because they still grab valuable stuff left and right.
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
How many tickets and merge requests did you get before moving to your own server?
Hm, these were probably some of the more active projects:
- https://github.com/vain/lariza/issues?q=is%3Aissue%20state%3Aclosed
- https://github.com/vain/pdfPres/issues?q=is%3Aissue%20state%3Aclosed
- https://github.com/vain/xiate/issues?q=is%3Aissue%20state%3Aclosed
So itâs not a ton of stuff and there are many âissuesâ I opened myself, but itâs certainly more than these days.
Havenât used
git send-emaileven once. I definitely have to look into that soon. Wanted to do that for several years. I typically upload the patch to my server and send a link via IRC.
git send-email is good for sending patches to a mailing list (because then the individual patches can be discussed easily), but since those are dying out as well, it loses its appeal. If you want to send patches to a single person, just sending the link to your repo is far easier. đ€
@movq@www.uninformativ.de Yeah, Iâm interested in your future bot stats as well. I wouldnât be surprised if they just keep hammering against all those now 404s. But I hope Iâm wrong.
jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
@movq@www.uninformativ.de Finally, your software is just perfect and finished by now, no need to report non-existing bugs or send in code changes. :-) How many tickets and merge requests did you get before moving to your own server?
I have to admit that I use git format-patch so rarely, I always have to pull it up from my shell history. Havenât used git send-email even once. I definitely have to look into that soon. Wanted to do that for several years. I typically upload the patch to my server and send a link via IRC.
Maybe I was just very unlucky, but my experience is that you can perfectly ignore people and their work who only do it for the âfameâ. Itâs almost always been from inferior quality to say the least.
@movq@www.uninformativ.de If only somebody had warned us! Luckily, no TV in this household. :-)
@lyse@lyse.isobeef.org Oh dear, thatâs cute. đ
@lyse@lyse.isobeef.org Thanks. đ Yeah, I already found it slightly annoying myself. Letâs see how the bots respond to the new situation. đ€
@prologic@twtxt.net Hmmm, I have no idea how to solve that problem. đ
Some jenny stuff aside, I received zero bug reports or code contributions since leaving GitHub in 2018.
I thought I had made that super easy, because you can just send me an email â no sign-up process, nothing. But thatâs way too old-school, people donât know how to use git format-patch (let alone git send-email) and they also donât understand that they can just send me a link to their forked Git repo (which can be hosted anywhere). Git is super flexible and powerful, but those features are hardly ever used.
Maybe people even need some kind ârewardâ, or âfameâ. Like those âachievementsâ that you can unlock on GitHub. (Something to put in their CV ⊠?)
@movq@www.uninformativ.de Works good. I fully get and support your reasoning behind that change. Thereâs only one downside. Quickly looking at some code snippets in the browser helps me to quickly judge whether itâs worth to clone a repo or not. Oh well. :-) After all I know that movqware always is.
@movq@www.uninformativ.de Luckily, Iâm not an autist. If you walk next to a busy road or airport, I totally get the annoying noises. Iâd plug my ears, too. But I meant in the woods where there are almost only nature sounds. Maybe they miss the jackhammers etc. :-D
@david@daiwei.me Hell yeah, letâs finally reintroduce the big predators! :-D
@david@daiwei.me OH no ! đ My wife caught COVID some weeks ago, then we got sick again with a cold, it was awful đą
Oh god đ€Ł I mean I had this idea to re-invent âGit hostingâ, but failed. Maybe Iâll try it again. I dunno. The thing is I hardly get âIssuesâ really, only when I ask nicely, of folks I know every well đ€Ł So think at much âsmaller scaleâ we need a different solution, and I think @movq@www.uninformativ.de is on to something, but not to the extend implemented, somewhere in the middle I think? đ€
os/arch for Mu is now relatively simple to do, or far less duplicated work/effort.
@david@daiwei.me Bah you đ€Ł Do you know how hardâą it is to write a compier, a self-hosted compiler that has two runtime engines? đ
@prologic@twtxt.net Which is? đ
@lyse@lyse.isobeef.org A small portion of people might do the headphone thing because of autism or sensory issues, to isolate them from annoying noises. I used to do that myself. đ€
@movq@www.uninformativ.de Hmmm youâve given me an idea đ§
@david@daiwei.me I first thought that this is a real lake, but itâs just a lake of craziness. :-D A town owned by a company (or so it reads to me), thatâs insane.
Let me send you some nice 17°C.
@prologic@twtxt.net Yeah, great documentary. I was reading up on Orcas a few months ago. Zoos are really problematic.
@aelaraji@aelaraji.com Noice đ
@prologic@twtxt.net yes! ~24 hrs ago!
@aelaraji@aelaraji.com oh good was that the in app nudge?
@david@daiwei.me @lyse@lyse.isobeef.org Oh, I wish it was for work. Iâd usually abstain from going if donât get to choose either the location, or the company. But, both? HEeeeeLL No!! đ
@david@daiwei.me We could say the same about the England - France game, right? đ
Does this seem right to you so far @david@daiwei.me ? đ€
2026/07/18 02:55:52 sync-reaper: observe-only pass â 1145 namespaces, 3 anchored, 1089 undatable, 0 idle candidate(s), 0 reaped
So far only 3 users of the Twtxt App have achieved their device settings with a recovery key? đ
Ta, @david@daiwei.me, much appreciated.
@movq@www.uninformativ.de Hahaha, I didnât expect anything like that. But yeah, makes perfect sense. :-D
@lyse@lyse.isobeef.org I was wondering for an embarrassingly long time why my NAS wouldnât boot. (The main power supply switch was turn off.) đ€Ș
@prologic@twtxt.net Haha, no, youâre off the hook this time. :-D Itâs totally my fault.
@movq@www.uninformativ.de Den LÀrm haben sie gut rausgefiltert. Ist mir jedenfalls nicht negativ aufgefallen. Oder es war einfach zu interessant. Tauschen möcht ich aber mit Dir echt nicht. :-(
@movq@www.uninformativ.de Now Iâm curious what happened.
@movq@www.uninformativ.de Bwahahaha, absolut groĂartig! :â-D
@lyse@lyse.isobeef.org Das ertragâ ich wahrscheinlich nur auf Mute. ScheiĂ LĂ€rm. đ€Ł
tt. I run into this bug almost daily for weeks now.
@lyse@lyse.isobeef.org Ahh ok! I was just wondering and curious whether it was a bug that Iâve caused anywhere along the way đ§
@dce@hashnix.club I see, ta!
@movq@www.uninformativ.de @prologic@twtxt.net @itsericwoodward@itsericwoodward.com Let me join the Enterprise Ruined It For Me Club. :-D
@david@daiwei.me Yeah, with the long and thus taller list entries, things are getting off hands. Ah, when focused, you wouldnât differentiate between read or unread.
tt. I run into this bug almost daily for weeks now.
@prologic@twtxt.net A screenshot wonât help in this case, as you donât see anything. :-D It starts off just fine with a conversation tree like that:
Unknown conversation root
ââŽRead reply
ââŽRead subreply
Everything works. After reloading the feeds, a new message becomes part of the conversation, so the conversation e.g. looks:
Unknown conversation root
ââŽRead reply
ââŽRead subreply
ââŽUnread subreply
However, the bug is that the whole conversation is not shown at all. None of the three (or four with the root) messages appear in the message tree view. My recursive SQL determining the messages to display is clearly broken.
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
and @david@daiwei.me your rename shipped đ itâs âGenerate recovery codeâ now (you were right â mints a fresh one each press), + it asks before replacing an existing code so you donât nuke the one you saved đ
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
@david@daiwei.me Good point ! đ
@david@daiwei.me Nice! đ
đŁ ACTION REQUIRED: Hey folks đ For those of you whom are using the Twtxt App either via the Hosted option or on your own twtd instnace or via Github/Gitea or any other publishing backend (doesnât amtter). Please read.
Please open the app and you should be prompted to save your recovery code for your device. This basically is all of your settings, follows, etc in the app itself. This is synced to the Origin everytime you make a change, and also stored on-device. This is what makes it possible to sync your setting across services, move to another device, etc.
Please save a copy of the recovery code somewhere. This is only your only way to recover your settings.
Thank you đ
@david@daiwei.me Ma too đ€Ł
@ponderpoints@twtpub.com Welcome to Yarn.social đ Interesting video, I actually watched it all the way through, riverting stuff really and quite well put together. The idea of âsubjective experienceâ is a rather complicated thing to describe and youâre right, how do we even know we have them? đ€
@david@daiwei.me Holy moly đ±
@balloon-fu-sen@tw.fus.f5.si Huh? đ§ This hasnât changed. What has is the default proxy used depending on your publishing backend.
@david@daiwei.me Itâs truly mind-boggling. All the hand full of episodes Iâve seen so far on this channel are amazing. Totally worth tuning in. I have to catch up a lot. :-)
SpitzenmĂ€Ăige Doku ĂŒber @movq@www.uninformativ.des kleinen Hausflugplatz: https://www.youtube.com/watch?v=F72t2fpiWPo
@david@daiwei.me Danke đ
@david@daiwei.me Cool đ
@david@daiwei.me Please đ
@lyse@lyse.isobeef.org Stimmt, das hatte ich völlig vergessen. Gab da mal diese Zeit, in der âForenbeitrĂ€geâ die Pest waren. đ€ Da ist sie also wieder, die rosarote Nostalgiebrille. đ
@prologic@twtxt.net that are included, part of the first round. LOL.
@bender@twtxt.net I meant the hookers đ€Ł
@prologic@twtxt.net I will pay for the first round. After that you are on your own! I am Bender, not your dad, right? đ
@bender@twtxt.net Whoâs buying? đ€
@prologic@twtxt.net well, thank you my good friend! Now, lets go for blackjack and hookers! đ
Another post, to show @prologic@twtxt.net I am around. I am not dead! Not for 9 days!
@kiwu@twtxt.net ba bá»n nÄm sĂĄu to you, too! đ
@prologic@twtxt.net @itsericwoodward@itsericwoodward.com âEnterpriseâ Java ruins everything, eh? đ I only did that very briefly, luckily.
tt. I run into this bug almost daily for weeks now.
@lyse@lyse.isobeef.org Can you explain this like iâm five? đ€Ł Scgeenshot?
@movq@www.uninformativ.de Ich war nie im Ubuntuusersforum unterwegs. Aber zu Delphizeiten damals im âPlanet Quellcodesâ-Forum aktiv, das es lĂ€ngst nicht mehr gibt. Ich schĂ€tze, die Hochzeiten der Foren sind einfach rum. Heutzutage ist einmal sehr viel mehr Wissen andersweitig zugĂ€nglich und dann sind vermutlich die allermeisten Leute auch einfach auf Soziale-Medien-Plattformen unterwegs. Oder werden die eigenen Projekte auf dem eigenen Blog und dergleichen vorgestellt.
Dann gabâs auch (zumindest gefĂŒhlt) eine Zeit, in der man einfach keine sinnvollen Antworten mehr in Foren bekam. So kam das mir jedenfalls vor. Ist schon eine ganze Weile her, aber ich kann mich noch dunkel erinnern, dass ich bei Forensuchtreffern hĂ€ufig auf Reaktionen Ă la âsuch doch selberâ stieĂ. Oder einfach zuhauf komplett falsche Antworten vorgeschlagen wurden. Ich hab mir dann angewöhnt, ForenbeitrĂ€ge komplett zu ignorieren.
Einige Foren haben auch noch damit angefangen, anonyme Zugriffe zu unterbinden oder zumindest einzuschrĂ€nken. Das half im RĂŒckblick natĂŒrlich auch nicht, dieses Medium attraktiv zu machen.
@aelaraji@aelaraji.com Thatâs totally fine if you work at the beach. :-)
@david@daiwei.me Right now, ttâs theme is baked into the binary. I have to edit the ui/styles.go and recompile. Luckily, this almost takes no time. But my todo list already includes a bullet point to make this customizable via the configuration file. :-)
@david@daiwei.me Ha, I just noticed that I changed Newsboatâs defaults. Right from the factory, new items are just bold, while read ones arenât. No different colors, white on black. Focused items are bold yellow on blue. No matter the read status. I think thatâs why I started to play with the config to differentiate them. Itâs been so long ago that I didnât know anymore I even messed with that.
And yes, youâre right, the red on black is borderline readable. Also, my white on green focus is rather silly. But Iâm sooo used to it, I donât realize how bad the contrast is. To be fair, I donât spend a lot of time in the lists. Aha, there are new articles, Enter to hit the artice view, read it, press n to immediately jump to the next unread article, rince and repeat, finally Iâm back in the article list view.
Default theme, read focused:
Default theme, unread focused:
Lyseâs schlimmbesserung, read focused:
Lyseâs schlimmbesserung, unread focused:
@aelaraji@aelaraji.com Haha đ Oh dear!
@kiwu@twtxt.net hi back at you!
@dce@hashnix.club Ah brilliant đ
To retest: reload the app, reconnect Codeberg/Gitea with the same token, fill in the new Owner field (dce), repo twtxt, and Feed URL https://hashnix.club/~dce/twtxt.txt. Publish to Codeberg, serve from Hashnix â exactly what you wanted đ€ lemme know!
@dce@hashnix.club Fixed! đ„ł That 403 was our bug â connect was checking your token via /api/v1/user (needs read:user), but your tokenâs scoped to just the repo so it canât. Now it validates against the repo itself instead đ
@misskatie@twtpub.com Haha đ€Ł Nice Avatar đ
@david@daiwei.me Bahahaha đ€Ł
@david@daiwei.me Oh yes blame me for you not having fun on the âPlay Stationâ đ Haha đ€Ł
@GabesArcade@gabesarcade.com I may be blocking that provider due to abuse from bots using VPN(s) â What was your last IP?
@lyse@lyse.isobeef.org It reads a lot nicer, yeah. And you can do oink.my_property += 1 as well, for example.
@dce@hashnix.club I should maybe look into it some day.