-- Leo's gemini proxy

-- Connecting to warp.geminispace.club:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini;lang=en

A Gemini Users Shared Database for Places and Restaurants


A couple of day ago I wrote on the mailing about creating a kind of self-managed database that we can consult on Gemini before to ending up eventually on the WWW.


How ever that gentleman of Yumh, the author of GMID the server that runs this capsule, suggested that a demonstration it would convey better my idea.


> "The main idea is to share our knowledge and experiences about our favorite places and restaurant in order to have all these information available on Gemini"


The main idea is to share our knowledge and experiences about our favorite places and restaurants in order to have all these information available on Gemini, in the wake of Gemini first; to make this possible I believe we should use a recognizable pattern that Gemini's search engines and aggregators can recognize in order to get these information quickly and ordered.


A Machine Readable Structure


I am not a Informatics Scientist hence this is not really my best skill, anyway I think we could start adding a folder called "places" in our root, like:


My Capsule
├── place
│   ├── index.gmi
│   ├── en-florida-south_florida-places.gmi
│   └── it-italia-roma-places.gmi
│
└── index.gmi

The index page I think is useful in case you have several places to share, although not strictly necessary.


The URL pattern


The URL pattern should be something that makes sense for a machine as well as for a human being, so far I came out with this idea:


[language]-[country]-[city or locality]-places.gmi

In this case you can imply that if an URL start with "EN" will surely provides content in English or in case it began with IT the content provided would be in Italian; if [country] or [city] must be written in a international language like English or should reflect the own [language] is something that I am not still sure about.


The entries


Also for this aspect people with better knowledge than me can come out with something more refined. Said that, one shortcoming is the difficult to organize the content in alphabetically without a script. Because of that I suggest to use a chronological organization instead, for instance a review made five years ago might not reflect anymore the real condition of a certain place.


I thought for a while about a possible organization and this would be one of my best solution:


[## DATE]
[### NAME'S PLACE]
[TYPE OF FACILITY]
[ADDRESS, WHERE, LOCATION]
[RATING]
[DESCRIPTION]
[EXTRA 1]
[EXTRA 2]
[WWW]

Where in place of [EXTRA 1] and [EXTRA 2] someone might add a telephone number or a GPS coordinates or a link to OpenStreeMap for instance.


A volunteer privacy leak


> "Sharing is Caring"


While "sharing is caring" adhering to this project means that we are voluntarily leaking personal information, and I totally understand if someone would prefer to avoid spill these out, for instance I am using an alter ego... ^^"


A capsule to own all the capsules


A capsule where people can add their favorite places through a TSL certificate is certainly cool, however a decentralized approach, which is essentially the one described here, is more resilient and easy to maintain (I guess). By the other hand current Gemini search engine or aggregator should be instructed to read "special" page like the "places" ones. Both methods may coexist together but this is beyond my understanding.


Wrapping This Up


Thanks for reading till the end, this is a real example with a real location:


EN-FLORIDA-SOUTH_FLORIDA-PLACES.gmi



freezr AT disroot DOT org


↩ go back

-- Response ended

-- Page fetched on Tue May 21 12:08:34 2024