Support the Gemini protocol (kinda like gopher but new)
No @ruarí, they do not!
It seems to be something to do with with the URL sanitation included in our backend. I guess we have
a whitelistan "allow list" of permitted protocols only.
@Ruarí You are raising some good points. If users write in Markdown, they aren’t aware how it will look in Gemtext and any workarounds could lead to ugly results. Since it would be the user’s decision to publish on Gemini additionally, writing in Gemtext directly makes sense. Then the only thing that is needed is converting the Gemtext to HTML for consumption on the web.
About Gopher, personally I have no use for it and it would complicate things even more.
Speaking of links. Another issue is link conversion between https:// and gemini:// Consider that our user blogs are hosted on subdomains of vivaldi.net. Should all links in a blog be converted from https:// to gemini:// when they end with *.vivaldi.net?
If we do not convert them then someone browsing with a Genimi client looking at the blogs gemlogs will constantly be pushed back to the web, even when one post links to a sibling post on the same site. However, if we do convert all the links then every page on vivaldi.net that isn't converted to Gemini (it might not even be practical to convert everything) will also result in broken links, when browsing from the Gemini side of things.
Well, when using a Gemini client you will have some sort of bookmark or subscription to access a blog hosted by Vivaldi. Any links in such a blog leading back to the web will be marked as outside links by the client itself and the reader will be aware they are redirected. Browsing with the Vivaldi web browser one should see no difference, because all the blogs should be accessible, since Gemtext is being converted to regular HTML in this case.
And no, I don’t think it makes sense converting existing Vivaldi blogs. It should be the choice of the content creator alone to publish on Gemini additionally and they will have to write in Gemtext for this purpose. It’s also reasonable to only publish specific content on Gemini and still content of another type only on the web.
I would lie if I claimed I get all you are talking about . Are we not taking it a little too far by talking about hosting Gemini pages on Vivaldi.net and writing gemtext with Vivaldi? I think just the ability to access existing Gemini space pages and allowing to search for them with Vivaldi would already be cool to just open that realm to a wider audience. Also I believe even the most hardcore Gemini User still needs to access the regular web all the time, and might appreciate a browser that can access both. Not that it wouldn't be cool to od more in step 2...
Are we not taking it a little too far by talking about hosting Gemini pages on Vivaldi.net and writing gemtext with Vivaldi?
Yes, indeed it is now two requests. The original one Vivaldi supporting the Gemini protocol and an additional request to allow the publishing of Gemlogs via the blogging platform we already have in place.
Each could be considered separately. I'll pass on the original idea first but again I am not promising anything and suspect it might go nowhere.
P.S. None of you have found my Gemlog yet then it seems.
None of you have found my Gemlog yet then it seems
If I only had a browser that made it easier to find my way around that space (= no)
@wildente Lagrange is pretty nice for a basic GUI client. Not perfect by any means but it is something. AV-98 is quick nice on the terminal
I am using Lagrange (rarely) , and yes, I just needed a lame excuse (to hide that I actually am not really reading anything much in the Gemini space). I still have trouble finding interesting stuff there (for the same reason). But I very much like the idea and hope it will see some success.
@ruarí Eh, the only thing I found was a comment of your’s on some gopher blog from 2008…
@luetage Sounds plausible. Every few years I go for a little trip around gopherspace, to remind myself how it used to be and see how things are going.
By the way… I just got notice from Ariane, which is the Gemini client I’m using on Android, that they will halt development of the client, remove all 3rd party code from the project, rename it and release a paid version. Ariane wasn’t that great to begin with, but the other Android clients are even worse. At this point you almost have to switch to Termux and start using a command line client. Anyway, as mentioned before, in my opinion it would make sense to try and introduce a Gemini client in Vivaldi for Android first. There isn’t much competition.
@luetage That's a shame.
By the way I searched for your username on gemini://geminispace.info and found nothing. No capsule or gemlog for you (or you have another identity)?
@ruarí Yeah, other handle. But I don’t have much content and the raspberry I’m running it on is down half the time. It’s more of a testing thing at this point. I do plan to get this going though. Maybe I’ll just go the sourcehut route and host the stuff there.
I had thought about using Gopher (or now Gemini) for
bloggingphlogging/gemlogging in the past because of the (engineering) simplicity of those kinds of setups. Both in terms of generating content and should I want to self host. The downside would be the extremely limited audience, due to the unusual protocol.
Historically, I always used to have a personal blog (firstly on my.opera and when that died I later used a paid blog hosting service that pushed Markdown for content creation). Again, using something like Markdown was nice because it meant that you could knock something up fast and easily and didn't feel pressured to spend a lot of time tweaking presentation. This kind of self imposed limitation appeals to me. You even see this to an extent in microblogging services like Twitter. The barrier to "write something" is small because you don't have to do much, just copy down your thoughts.
At some point though I just kind of let the last blog expire as I felt I was not using it enough, so I stopped paying. Since that time the kind of thoughts I might put into a 'blog' have been kind of scattered on various services, much of it Github gists or Twitter threads but sometimes other places, e.g. I have a couple of things you might consider "blog posts" on my Strava account.
The problem with this scatter approach, is that it is very hard to locate something you wrote before because it could be in any number of places and one of the things I liked about a blog is that I could either link to them or sometimes just copy and paste snippets of them when having conversations on similar topics elsewhere online.
Recently (three days back), I put up a tiny bit of content on Gemlog Blue as a test. So far it has been tweaked, reposts of stuff I have said on Twitter, Github and parts of a splintered conversation (with several different people) on Slack but already I see some value. I was able to flesh out and reorganise my thoughts (Twitter threads are too limited sometimes) and now I have those 3 'articles' in one place (plus an intro post). I don't really imagine many people will find and read them because of the 'limited audience' on Gemini but there is still some value. Firstly I started to notice that as much as anything posting them is 'for me', so that I can go back over my thinking, or clarify my thoughts in my head during the process of writing. I guess in much the same way people have kept diaries. Also it still gives me a place I can copy snippets of ideas from and if I really wanted to link someone to an entire posting, I could always give them a link through a Gemini-to-web proxy service (since we are not at a stage where we could expect many people to have a Gemini client installed).
I am not sure that gemlog blue is where I would want to host long term though. It is just a free gemlog hosting service and it could easily disappear in much the same way my.opera did. Again another appeal of Gemini is the simplicity of self hosting but I figured I would start there as a test/trial and just move stuff if and when I decide that this is something I might want to do again going forward.
P.S. I realise now that I have given you more than enough information to find my little test gemlog but that is OK it is not secret and it is probably pretty dull to anyone but me . Also, these are just variants of things I have already posted publicly anyway. Anyway, I am still confused how you did not find me in the first place. I find myself immediately via a name search on gemini://geminispace.info
@ruarí Well, my search term was
unicyclegeek1337and I expected to get a hit. Not my fault But ok, got it now
@luetage unicyclegeek1337 could have been the one other guy I found who has writes a gemlog and likes unicycling.
@ruarí Your capsule is already very nice. The only thing it desperately requires is an atom feed so all your fans can access your content asap. In my opinion Antenna
gemini://warmedal.se/~antenna/is a good way to get recognition. It’s a continuous stream of capsule feeds and I stumble upon some interesting content there every now and then.
And before I forget to mention it, I like the concept of Station. It’s Gemini’s twitter equivalent without the garbage and hate. Worth taking a look ☛
@ruarí I actually did that search but the search results didn't look relevant (too used to the regular web?) I just didn't think of clicking through all (... wow, 3! ...) search results
You wrote quite a lot in a few days. Recycled? (pun intended)
You wrote quite a lot in a few days. Recycled?
It is somewhat recycled but everything was tweaked/updated. In addition I have written a couple more now that entirely new (albeit just as dull).
The only thing it desperately requires is an atom feed so all your fans can access your content asap.
I was almost tempted to self host as it was not obvious how I could setup an atom feed from Gemlog Blue but in the end I decided to move to Flounder (
gemini://ruario.flounder.online/), which was both easier than self hosting and is more powerful.
Again Gemlog blue's limitations meant proper redirects were not something I could see how to setup, so I just redid all the pages so that they point to their Flounder equivalents.