Bacardi55's Gemini TinyLog

Welcome on my tinylog where I wrote short and uninteresting stuff…

author: @bacardi55

avatar: 🤔

2025-06-27 09:59 +0200

Weird idea: #Selfhosting 5 different #finger servers (all named after a finger, eg: thumb.finger.bacardi55.io, index.finger.bacardi55.io, middle.finger.bacardi55.io, …) with 5 different goals: latest tinylog entry, latest gemlog, latest blog post, and other useless thing…

I know there is absolutely no good reasons to do so except “because I can” and “it would make me laugh"… So we’ll see if I one day find the time and motivation to do so even though I have way more important things on my todolist .

2025-06-26 17:03 +0200

I received my #clockwork #uconsole 2 weeks ago, but because I was sick and then had to travel for work, I haven’t been able to play with it since I got it…

{{< figure src=”/images/micro/uconsole.jpeg” >}}

My short term goals:

• Install debian bookworm
• Encrypt only my home directory (I think full encryption might be to harsh for micro sd card)
• Install emacs, syncthing and git so I can write and publish from it
• Install some retro gaming (best rpg games were made for SNES anyway!)

What I don’t know is what am I going to do with the keyboad layout. Normally I’m an azerty user. And even on my Dogma Raise 2 that has qwerty keycaps, I have it setup to azerty as I don’t care and don’t look. But the layout of the uconsole is so special that changing it might mean I’ll struggle a lot to find some special keys… So I’m still perplex at this stage about that.

2025-05-29 18:08 +0200

https://blog.pomdtr.me/posts/tweety-v1/

While I have nothing against the writer of this post and I don’t care if they decided to use their terminal within their web browser, I do believe this is yet another example of how we broke our use of computer and the web in general…

« Everything should be a web app » is just a very bad idea for so many reasons that I’m too tired to enumerate here. A side effect is seeing so many CLI/TUI application developped in JS/Typescript/NodeJS.

I don’t want to only use a web browser at all, I want more “desktop software” doing their job well, even if they are connected to web services to do their job… My window manager is then here to manage window and workspace the way I like. I have already too many tabs open in my web browser (even though I’m using readeck (read-it-later) and linkding (bookmark manager)) to add all my terminal windows in there too.

Useless rant, but I had to say it anyway :-).

2025-05-29 18:05 +0200

What was supposed to be a « work on GTL afternoon » turned into a « reinstall your NAS afternoon »… I’ll try to work on GTL tomorrow though but the NAS moved to priority #1 yesterday after a broken update (my fault, it was still running debian buster).

2025-05-26 11:25 +0200

Just discovered that an android application for #readeck already exists! I wasn’t aware of that and that might be a game changer for my readeck usage as it does provide offline usage!

https://github.com/jensomato/ReadeckApp

Will try it later today!

2025-05-24 03:04 +0200

https://support.mozilla.org/en-US/kb/future-of-pocket

So mozilla is shutting down pocket… Yet another good move from them /s. I guess they need the money to develop more AI bullshit and focus their R&D money where their own users don’t want it to go…

Anyway, I’ve never used that tool anyway, but I can strongly advice using either #wallabag or #readeck . Both are great tools! Readeck is faster and has a better and more beautiful UI. But Wallabag has a phone app that can import articles for offline read, which I believe readeck really need to get at some point. Too bad I just don’t want to build an android app (for readeck or anything really).

I believe you could achieve the same with readeck and its OPDS endpoint. Something I still need to look at.

2025-05-20 19:08 +0200

That’s the 3rd time today that I had to reach out to someone because they deployed an anti AI service like #anubis or #goaway . I have nothing against these people that just try to protect their service / assets from these shitty bot scrapping the web like they own it (when normal people do it, they get sued though)…

That’s what the AI slop is giving us right now: shitty AI services that most don’t care about (and the one that does should be a lot more careful about their results) and are a pain in the a** for everyone else: people trying to run small services / websites and the one that try to follow them outside of proprietary jails…

I really hate the state the web is now… NO thank you big tech sh*t heads.

2025-05-20 15:11 +0200

Hey, we have checked your website and it looks like SEO isn’t working properly, and it’s also not ready for AI-based ranking. We guarantee TOP3 placement on search results for a very affordable price. You can WhatsApp us: [redacted]

Just received this spam for the 2nd time in a couple of days… What they don’t know is that:

• I don’t care about SEO. This sh*t has been broken for a long time anyway.
• “Not ready for AI-based ranking” is actually a great thing to me :D

Seriouly though, not the first time I get around this, so I guess they found me somewhere so it must not be that hidden anyway xD… But still I wish I wouldn’t receive those email wasting my time (even for a few secondes).

2025-05-20 14:36 +0200

I just love email conversations that I sometimes have with other bloggers or people that read some of my blog posts. Most people reaching out (or people I reach out to) are nice and open. And it often sparks new thoughts and ideas in a very positive manner!

As written in my about page:

I’m happy to receive any messages regarding this site or its content, would it be a short or an extensive message, in French or in English, on any of these channels

So always feel free to reach out!

2025-05-19 16:55 +0200

2025-05-13 20:07 +0200

I really like that I can now write one microblog entry and decide to deploy it on both or either my website (as notes[a]) and/or on my capsule as a tinylog entry[b]! I need to write more about this, but basically it goes like this:

• write in emacs/orgmode the entry using a capture template to preformat the entry (specially the frontmatter)
• Indicate in the frontmatter the channel: “tinylog” and / or “website”
• Optionnaly add a element to indicate it is a response to someone (used only on tinylog entry for now)
• Optionnaly add tags (only used on my website so far)
• Export to markdown using ox-hugo as for blog or gemlog post in the right place
• Git add / commit / push the file
• Sourcehut automated build starts like usual and use a new tool I created called micrologs[c] to create the tinylog.gmi file and the different markdown file for hugo

Seems over engineered like the rest of my deployment workflow, but weirdly I find it easy and fun :).

Missing pieces:

• Micro logging from my phone
• Add “fediverse” (my gotosocial account) as another channel to choose to deploy entries too

2025-05-12 22:37 +0200

I love my new Dygma Raise 2 keyboard[a]!

Mandatory picture: [b]

(This is mainly an entry to test my new micro blogging workflow for my tinylog and on my website)

2025-05-06 01:49 +0200

Wow, another set of patches for GTL, this time from @cthulhu! GTL never got so much love than for the past month! Can’t wait to review all them next week and improve GTL again!

Sorry for making these patches wait, but thanks to all of you lovely people submitting patches <3

2025-05-03 02:14 +0200

Just saw that @zekromaster sent a patch to GTL to update dependencies! Thanks a lot for this!

Like @fab and @sandra ‘s patches, I’ll review them after my vacation mid May, but really appreciate your help!

2025-05-02 01:03 +0200

@skyjake: I don’t know if you read my tinylog, but if you do:

I sent you an email about my access to BBS. Most probably ended in your spam folder but I would appreciate if you could help with retrieving access to my bacardi55 account as I don’t want to create another account with another username :-).

Thanks!

2025-05-02 00:57 +0200

So, what exactly did change?

For reader, nothing :). It is just a new workflow on my side to write micro log entries in the form of small markdown file (like for each gemlog or blog entries) and based on content in the frontmatter headers, my CI/CD will create the tinylog files and also the files for my blog depending on the “channel” I indicate in the frontmatter.

I’ll write a more detailed post about it but I’m doing this to:

• Keep 1 file per post
• Indicates if a micro post should be published on my tinylog, on my website or both (or even on my fediverse account)
• This, with some additional code, will also allow me to write these micro post from my phone

Still over engineered like the rest of my deployment workflow, but I’m having fun doing it so I don’t mind :-).

2025-05-01 01:07 +0200

If you read this, it means the first step of my new micro blogging workflow is done. Still a lot to do but a good first step!

2025-05-01 00:45 +0200

Looking at the “new” drama around the fosstodon instance… I’m:

1. so glad to be running my own instance to avoid all these issues

2. scared of how fragile the whole thing based on how quickly instance owners are inclined to defederate others.

It feels like every instance owner with enough users can just always scare others with defederation like a weapon. Defederation is a great tool for the sake of the fediverse but should be used wisely. Blocking/Muting users is always prefered when the whole instance is not horrible like Gab or Truth social…

A lot could be said about that, but I won’t go there yet… But I think there is something to do here to make the fediverse both more safe for everyone and smarter too.

2025-04-29 21:09 +0200

First tinylog entry writen with my new micro blogging system (not entirely finished).

More info to come :-).

2025-04-28 15:45 +0200

I’m thinking of migrating my source repositories to SourceHut. […] and I must say I really like how simple the CI/CD is compared to GitHub and GitLab.

Agreed, moved to sourcehut some time ago and love it. My deployment workflow is built on their CI and and it is very flexible and simple.

My only issue with sourcehut is the unfriendly UI when it comes to navigates between projects, repository, mailing list and tickets for one or multiple project or per users. The project area is great but you often loose that connection by navigating to other places.

2025-04-28 14:35 +0200

When folk log onto GTL what do they hope to see? I want to write for myself, but I also want to be considerate of others.

I suggest you just write for yourself instead of trying to please an “audience”. People who like what you write will read, other will ignore, as simple as that :).

Also, GTL is a software, not the entire ecosystem that the tinylogs are.

2025-04-25 02:16 +0200

New tinylog added to the aggregator: gemini://zekromaster.net/notes.gmi[a]

2025-04-24 02:08 +0200

what are your thoughts on adding Station and BBS logs to the overall subs list?

The main issue I have with this is who should be added and who shouldn’t? “Everyone” is, I think, not scalable, and I don’t know where to draw the line… There are a few station users already and even for those I’m hesitant to keep them.

I feel like adding tinylogs from these service doesn’t serve the tinylog ecosystem because that makes these tinylogs second class citizen.

I truly believe tinylogs could be the base of a “fediverse for gemini” if done well, hence my idea of an open source multi user selfhostable tinylog service that can still interact with other instance and with individual tinylogs hosted like ours. May take a bit of time to architecture and develop but I think it would be a major step forward for tinylogs being easier to adopt and spread amongst the gemini community.

2025-04-23 16:53 +0200

maybe the aggregated logs from GTL could have a preformatted text line at the bottom of each message to just copy/paste into the top of the reply

I love the idea so much that I already implemented it :).

Good thing I refactor the gemtext output to use a template last week, it made it so easy to actually add this!

2025-04-23 09:18 +0200

Well, I’m clearly not planning on working on a mobile app because I don’t like those. That being said, I’m currently working on something that will allow me to post to my tinylog from my phone (and to part of my website too). It is clearly over engineered and over complicated (like everything related to my deployment workflow - but it is fun - for me at least). As for consumption of other tinylogs from my phone, I simply go to the aggregator with Lagrange. If you want your own subset of tinylogs and not all the one from the aggregator, you could simply host your own aggregator with GTL which has a gemtext output option (this is what the aggregator uses).

All that being said, the easiest may be the long goal project I have for tinylogs with a simple centralized (yet “federated”) tinylog service where you could post from your phone with lagrange and a certificate. But that’s clearly more mid/long term compared to the other thing that I’m working on, but which may be very tight to my own use case.

I’ll write about all this soon.

2025-04-20 20:10 +0200

I’m writing golang code… It should be for GTL, but I may have started a new small-ish (that could grow bigger) project that will be the core of my new microblogging workflow (for gemini tinylogs, but also for my website and the Fediverse). I will work on GTL soon though, I have a few patches to review and then a full new TUI to build from (almost) scratch. And then maybe work on my vision for a centralized decentralized tinylog service (but clearly not short term for this one.

2025-04-18 17:12 +0200

Small updates to the tinylog RFC[a]:

1. Explicitly indicates that the @ is mandatory before the author name.

2. Allow having 2 blank line in an tinylog entry (always had worked in GTL but was forbidden by the RFC before, but it doesn’t make sense).

2025-04-18 16:27 +0200

I noticed that you updated the date format to comply with the new RFC version, which is great!

But FYI, while the new RFC version is not yet 100% validated, the current state indicates that timezone abbreviations (such as CEST) are no longer valid, instead use UTC offset (eg: +0200).

It makes parser’s life not coded in advanced languages a lot more simpler and human readable too (without looking online what the abbreviations means).

2025-04-18 16:25 +0200

I’ve updated GTL to make the output of the tinylog aggregator more flexible (via a template file). The first update to the output was to add a link to the subscriptions used in the aggregator[a]

The link give a file that can be used with GTL to read locally all subscriptions known by the aggregator (which should be most if not all of them).

2025-04-17 13:45 +0200

I think I fixed the aggregator to make it better than before. I didn’t change anything related to the spec yet, just fixed the fault tolerance.

I also updated the list of tinylogs aggregated there. Some may be missing, let me know (but I started from @fab@redterminal.org’s list).

Gemlog with a bit more detailed coming later today.

2025-04-17 00:59 +0200

I’m not sure what’s going on with the tinylog aggregation at bacardi’s place. The tlogs seem to come and go, randomly.

Not sure either, I just moved the capsule to another server and since then there are always some tinylog failing when the aggregator runs… I know GTL (the tool behind the aggregator) is not great with slow responding capsule but it shouldn’t be as bad as it is now. It wasn’t when it was running on the other server, so I need to further analyse that. As I’m reworking the tinylog RFC at the moment, I’ll work on an updated version of GTL once it is finalised. Hopefully, I can improve that part too.

I doubt it’s anything on my side of the connection, as it’s basically retrieving a single “file”. Nothing good lasts forever?

Indeed, it isn’t on your side.

2025-04-17 00:57 +0200

I don’t understand why blank lines are forbidden in a tinylog entry now, except at the end.

Fair point, that’s something that I didn’t change, but you are correct that it is something we could remove. I’ll make a not of that and compile it with other remarks if I receive other ones.

Thanks!

2025-04-15 23:55 +0200

Of course, my first tinylog entry for this tinylog “rebirth” is about… Tinylogs! I’ve finaly updated the RFC, more detailed on the dedicated gemlog[a].

And the diff on codeberg[b].

Discussions welcome via gemlog, tinylog, email or via the codeberg issue[c]