@aelaraji@aelaraji.com Perfect! :-D

@movq@www.uninformativ.de it’s a shame we have to ruin such great technology that only depends a lot of this with crappy bullshit nonsense like advertising we’ve been into responses 🤦‍♂️

@prologic@twtxt.net This was to be expected and I’m glad that it’s finally happening. I seriously hope that AI/LLM output gets swamped with advertisements or unwanted code, so people see what they have gotten themselves into, especially the “vibe coders”.

@david@daiwei.me You might have ended up loading the page in an unfortunate moment while I was reworking it. 😅 The CHANGES file is there, in the browser:

Advertise in ChatGPT | Hacker News Seriously?! 😳 wut da actual fuq?! 😱

@aelaraji@aelaraji.com Perfect! 👌

@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? 😅

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

I finally built a prototype of a marking gauge with a cutter wheel out of some scraps.

https://lyse.isobeef.org/tmp/streichmassprototyp-mit-messerrad/

It had been a long time in coming, I bought some replacement cutting wheels three years ago for exactly that purpose. I also found out that I need more M3 countersink bolts for future marking gauges that I want to make (maybe two or three more). Luckily, I had exactly one. I thought I got way more than that, but M3 is very, very scarce in my collection. My M3 bolt was barely long enough to attach the cutting wheel to the bar. But it’s okay for the prototype.

I was pleasantly surprised that I managed to drill the 2.5mm diameter hole almost perfectly in center in the 8mm diameter aluminium round bar. Center finder, drill press and vise with a vertical prism for the win!

I knew upfront that the M5 steel bolt to lock the bar in place definitely needs to be replaced with a brass or aluminium one (maybe with a knurled head). Otherwise, it cuts into the aluminium bar and leaves ugly marks. These burrs might even scratch the workpiece. But, of course, I don’t have any brass on hand either. Alternatively, I swap out the aluminium bar for a steel or even stainless steel one. Stainless might be tricky to precisely drill and tap, though.

I already learned a few things by making this prototype. The final wooden fence can be even a bit bigger. This round thing behind is also too short, I’d like it to be a tad longer and thicker. The final one will be made from hardwood, not spruce. Other than that, it’s great and already more practical than my store-bought marking gauge with its round fence. This only causes the tool to roll around on the workbench. Or even roll off. Stupid design.

@david@daiwei.me Is this better? 🤔 Pretty hard to keep this concise but also not miss anything. 🤔 https://movq.de/git/jenny/

@prologic@twtxt.net Even without the gamification and AI, I don’t host anything on GitHub. Just the fact that it’s owned by Microsoft spells trouble, in my opinion.

I still have an account, for occasionally contributing to a few specific projects, since a lot of developers wouldn’t know what to do with a patchset, and since many users of GitHub/Lab and Codeberg use send-only email aliases, so git send-email probably wouldn’t work.

@david@daiwei.me Oh, that is a good idea. This could be included here, yeah. 🤔

Hmm …

My project pages have this “Downloads” section and I offer tarballs for each release:

https://movq.de/git/jenny/#downloads

I added this many years ago because an OpenBSD dev asked for it (but the project in question didn’t end up in their ports after all).

What are your thoughts on this? Is it necessary to offer tarballs?

I noticed that some distributions have already moved away from using tarballs and instead always clone from Git. 🤔

@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 🙌

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.

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

@lyse@lyse.isobeef.org

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-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.

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 Interesting, given that Vim Classic is specifically an AI-free fork of Vim.

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

@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. 😃

Why is there no English version of this interesting ZIP code article!? https://de.wikipedia.org/wiki/H0H_0H0 (Canadians know that this is Santa’s postal code.) https://www.canadapost-postescanada.ca/cpc/en/our-company/write-letter-to-santa.page

@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? 🤔

@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? 😅

After many months of hard™ work, I’ve finally been able to get Mu (µ) lang to a point where the duplication of machine code / assembly between the ARM64/AMD64 and Mach-O and ELF formats are not all eliminated. This now means that writing a new backend target os/arch for Mu is now relatively simple to do, or far less duplicated work/effort.