💾 Archived View for gemi.dev › gemini-mailing-list › 000777.gmi captured on 2023-11-04 at 13:06:14. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Hello! I heard of the wonderful Gemini protocol a while ago, and I've decided to put my blog on Geminispace! gemini://snowymouse.com I may put other resources on here later for some of my other open source projects, but I've decided to just start out with my blog. The server software I'm using is something I've mostly written from scratch in C++, and it presently serves no actual files on the SSD - just my blog posts from a MySQL database (either?converted from markdown or written in native gemtext), a status page, and a contact page. Anyway, my question is... is it better to use a subdomain (i.e. gemini.snowymouse.com) or to continue using the main domain (i.e. snowymouse.com)? I've been lurking on this mailing list for a while, and I've been seeing a lot of new capsules using either, so I wasn't sure! As a side note, I consider the HTTP and gemini blog functionally identical since, besides differences in formatting, they're functionally identical, which is why I defaulted to just using the same hostname. Many thanks, Snowy
Quoth Snowy <snowy at snowymouse.com>: > Anyway, my question is... is it better to use a subdomain (i.e. gemini.snowymouse.com) or to continue using the main domain (i.e. snowymouse.com)? I've been lurking on this mailing list for a while, and I've been seeing a lot of new capsules using either, so I wasn't sure! I would say: if you can, use your main domain. Sharing it would share both your web and gemini presence :) In the end, I doesn?t matter much, go with the most practical solution for you!
On 02-Mar-2021 16:00, Snowy wrote: > As a side note, I consider the HTTP and gemini blog functionally identical since, besides differences in formatting, they're functionally identical, which is why I defaulted to just using the same hostname. Ha ha - be careful with remarks like that equating HTTP and gemini - these sort of statements can be considered as blasphemy round these here parts! :) Just host them however it makes sense to you. Sometimes it makes sense to use a different sub domain if it is different content - more easily moved around perhaps. But if it is all coming out of the same database, that seems less of an issue. ?- Luke
On Tue, Mar 02, 2021 at 05:00:04PM +0100, Snowy <snowy at snowymouse.com> wrote a message of 25 lines which said: > Anyway, my question is... is it better to use a subdomain > (i.e. gemini.snowymouse.com) or to continue using the main domain > (i.e. snowymouse.com)? As said by others: do what you want. The Lupa crawler <gemini://gemini.bortzmeyer.org/software/lupa/> knows 725 working capsules and only 80 of them has a name starting with 'gemini.' or 'gmi.'. But of course there are other subdomains (4 'capsule.'). Choosing the apex of your domain has pros:
Mar 2, 2021, 10:59 by luke at marmaladefoo.com: > Ha ha - be careful with remarks like that equating HTTP and gemini - these sort of statements can be considered as blasphemy round these here parts! :) > Goodness, well, yes, I meant just the blog (the posts), not the protocols! Of course, for some posts, I may need to change things like links, lists, tables, and other things for the gemini version in order to convey the same information effectively. And there is styling on the HTTP/HTML site where no such styling is necessary (or possible) on gemini/gemtext. This requires a little bit of extra care sometimes, but since most of my content is just headings and text, anyway, it's rarely a problem. That said, I do use a HTTPS server (with IP filtering) to modify/submit articles to the blog, particularly a PHP tool called Adminer. I, of course, don't really see myself comfortably making entire posts in under 1024 characters using only one line (though I'm sure writing an editor that has you submit multiple lines wouldn't be impossible, if convoluted). > Just host them however it makes sense to you. Sometimes it makes sense to use a different sub domain if it is different content - more easily moved around perhaps. But if it is all coming out of the same database, that seems less of an issue. > As far as websites go, when I think of switching between two different protcols (for example, HTTP and HTTPS but not necessarily HTTP and SCP), my thought process was receiving the same content but in a different way, which is sort of what I was going for here. Anyway, I'll keep using this! Thank you!
---