@dce@hashnix.club I don’t use Gemini, but I follow you on the good, old, HTTP(S)! :-)

Here’s an interesting thought/angle on this topic:

gemini://gemini.conman.org/boston/2025/08/21.1

A further check showed that all the network blocks are owned by one organization—Tencent [4]. I’m seriously thinking that the CCP (Chinese Communist Party) encourage this with maybe the hope of externalizing the cost of the Great Firewall [5] to the rest of the world.

Really, it won’t be long until I give the world the finger and move everything behind Gopher or Gemini. It’ll be a while until the bots find me there.

When I chose the MIT license for all of my software, I thought:

“Should I use GPL, which I don’t really understand? Is that worth it? Yeah, there is a theoretical possibility that some company might use my code in their proprietary product … and then what? Should I sue them to enforce the GPL? I’m not going to do that anyway, so I’ll just use the MIT license.”

And now we have those LLM scrapers and now it’s suddenly a reality that these companies (ab)use my code. I can see it in my logs. I didn’t expect that back then.

GPL wouldn’t help, either, of course. (Regardless, I now think that GPL would have been the better choice anyway.)

I’m honestly considering taking my code and website offline. Maybe make it accessible through some obscure protocol like Gopher or Gemini, but no more HTTP.

(Yes, Anubis might help. Temporarily.)

I’m just tired.

Farrrk me Google search is and these days. Will they please “fuck off” with this Gemini AI garbage at the top that takes forever and is distracting as shit™ 💩 Fark me 🤦‍♂️ #Google #Search #Sucks #AI #Gemini

@prologic@twtxt.net OH SHIT using this for a protocol like gopher is smart! might have to try that for gemini so i don’t have to keep a port open for that

@bender@twtxt.net thinked about Gemini protocol. Why corporations shit this name with cryptocurrency and LLMs?

well, I assume by syntax you mean Gemtext (which I like a lot, my personal blog is built on top of it), so I think it might work for twtxt clients…

I knew of twtxt in Gemini Antenna, so at least the 2017 spec might work on that protocol. I think the main issue with extensions is that they weren’t designed with many URLs and protocols in mind.

Also I have to admit that the Gemini community significantly reduced in the last few years. I don’t know how worth it is to add support for Gemini now.

@eapl.me@eapl.me I agree. The syntax is weird inside Gemini and twtxt is made with the http protocol in mind and Gemini doesn’t work with some extensions.

Timeline and twtxt-php, don’t support Gemini, only HTTP/S, as a design choice (although originally it was intended to work on Gemtext, it was a niche inside a niche, so it was discarded very soon).

At the moment of building the engine there weren’t many Gemini URLs supporting twtxt 1.1 (with twtxt.dev extensions).
Also User-Agent won’t work there, and many Gemini URLs are a mirror of the HTTP one, so I think is not strictly necessary.

my 2c

Are there any clients to read gemini?

well, Gemini clients like Lagrange allow to show inline images when you click on an image link. Text based clients, like Amfora, usually allow to watch the image in another ‘window’.

For example here: gemini://text.eapl.mx/en-making-a-tic-tac-toe-variant and there https://text.eapl.mx/en-making-a-tic-tac-toe-variant

I agree that some topics require images to make it easier to explain.

@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")

messing with gemini again, this time a static site generator called gssg - https://git.sr.ht/~gsthnz/gssg

my capsule is linked in my profile but just in case it’s over at gemini://lazuli.sayitditto.net

@sorenpeter@darch.dk on 4 for gemini if your TLS client certificate contains your nick@host could that work for discovery?

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

4. Do we need more commandments?

Understand, ok seems i should leave gemini untouched

should i delete gemini support from twet? iirc in twtxt v2 it starts prohibited. And all of my fields are https

Found this: https://notabug.org/tinyrabbit/gemini-antenna. Maybe it have some user-agent alternative?

I hear about Gemini Antenna as User Agent alternative but cant find any information

I was not suggesting to that everyone need to setup a working webfinger endpoint, but that we take the format of nick+(sub)domain as base for generating the hashed together with the message date and content.

If we omit the protocol prefix from the way we do things now will that not solve most of the problems? In the case of gemini://gemini.ctrl-c.club/~nristen/twtxt.txt they also have a working twtxt.txt at https://ctrl-c.club/~nristen/twtxt.txt … damn I just notice the gemini. subdomain.

Okay what about defining a prefers protocol as part of the hash schema? so 1: https , 2: http 3: gemini 4: gopher ?

how little data is needed for generating the hashes? Instead of the full URL, can we makedo with just the domain (example.net) so we avoid the conflicts with gemini://, https:// and only http:// (like in my own twtxt.txt) or construct something like like a webfinger id nick@domain (also used by mastodon etc.) from the domain and nick if there, else use domain as nick as well

Google Chrome will have Gemini LLM built into the browser.

I would love to see a world where ones twtxt feed is defined by webfinger. So @xuu@txt.sour.is => https://text.sour.is/user/xuu/twtxt.txt

Then my identity can exist independent of the feed location. And I can host multiple protocol types for my feed. Ie. http/gopher/Gemini/irc DCC/etc

After seeing Google’s Gemini video, will everyone now need to invest in one of this pointing-downwards camera stands for the home?

Another part of this crisis is that I like the idea of what I was doing with gemini, but the main issue here is that hosting from my house when my internet is terminated every month for 10-15 days is a problem. Not just for my sanity, but also for reliability

Almost MIPS-only session today! Actually, I also briefly ran my PowrBook G4 and the Gemini PDA in attempt to fix my Pebble. But mostly the SGI O2 and the Indigo, too!

I grepped access logs and found at least three subscribers! @apex@rawtext.club, @prologic@twtxt.net, and @darch@neotxt.dk, hi there!

My gemini capsule has a gemlog now and I update it usign a script I made…

Look at my fancy new gemini capsule at gemini://tilde.club/~melyanna/

also at gemini://om.gay/twtxt.txt and gopher://oh.mg:70/0/twtxt.txt

@benk@kwiecien.us I am using jenny (we chatted a bit on IRC earlier today). I have been using it for over five months now, I think. It is truly a joy to use, specially because you can use the power of Mutt/NeoMutt to read your twts.

Oopsies, turns out I’ve never included my twtxt file on Gemini

@fastidious@arrakis.netbros.com the things Gemini has going for it are mutual TLS and lack of JavaScript. Which makes for a secure albeit boring experience (much like gopher). The fake markdown is a bit of a drag.

A render mode for Gemini probably wouldnt be too hard. There are markdown to Gemini libs out there.

With Web3 the whole trust a 3rd party browser ext + high fees + env impact for compute and storage are serious no gos for me.. I have heard one too many horror stories about clicking the wrong link and some script draining your metamask wallet.

What if due to climate crisis effects and disasters our digital future will depend on low-energy hardware and protocols like Gemini?

compudanzas.net is now available in gemini: sharing (self-hosted) space with caracolito.mooo.com :) | https://compudanzas.net/gemini.html

@prologic@twtxt.net deedum for android.

Kristall for OS X

Elaho for iOS

more here

though I can only vouch for the first two.

Just a note that I have a little gemini capsule at gemini://tanelorn.city/~melyanna/

Can I interest you in the latest edition of Tales From The Dork Web when it’s about Gopher, Gemini and The Smol Internet? https://thedorkweb.substack.com/p/gopher-gemini-and-the-smol-internet

Now also to be found on Gemini at gemini://gem.johanbove.info - the future looks light and bright!.

Started playing with the gemini protocol on ctrl-c.club

I re-read my script that updates my gemini log automatically

Making a bash gemlog script to maintain my gemini log

I just installed asuka to try out the gemini protocol (https://gemini.circumlunar.space/)

You can now find me on Gemini at gemini://tanelorn.city/~melyanna

Ready to explore the gemini protocol as it looks awesome so far

Gemini "The Autonomous Robot" - YouTube https://www.youtube.com/watch?v=A44biuHj7UY