💾 Archived View for gemi.dev › gemini-mailing-list › 000998.gmi captured on 2023-11-04 at 13:15:26. Gemini links have been rewritten to link to archived content
View Raw
More Information
➡️ Next capture (2023-12-28)
-=-=-=-=-=-=-
More Awesome Gemini
- 📧 Messages: 3
- 🗣️ Authors: 2
- 📅 First Message: 2021-08-31 17:52
- 📅 Last Message: 2021-08-31 20:43
Jonathan McHugh <indieterminacy (a) libre.brussels>
- 📅 Sent: 2021-08-31 17:52
- 📧 Message 1 of 3
Hello all,
In lieu of the upcoming talk I recently mentioned:
=> https://lists.orbitalfox.eu/archives/gemini/2021/007043.html
I feel that the heterogenous ecosystem of tools may benefit from tighter
documenting. Or at least integrating
For instance:
- The Awesome Gemini site has categories
=> https://github.com/kr1sp1n/awesome-gemini
- Repology has packages by operating system
=> https://repology.org/project/lagrange/versions
- Functional package managers such as Guix have details on the inputs
required to compile tools
=> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/web-browsers.scm#n695
- Manpages providing commands
=> gemini://drewdevault.com/cgi-bin/man.sh
# Is there a programmatic overview of Gemini's toolsets?
For example:
- One of the things Id like to do is provide an overview of which tools
import and export into GemText.
- I should be able to generate a selection of tools based upon criteria,
without duplicative searching
- It would make it easier the make quick evaluations
- It would make it easier to make representations of this
Im going to make a stab at collating representative list(s) of such
concerns, so I can make some fun diagrams
# Going forward
- Any tips or knowledge silos I should be considering?
- Anybody keen to help during the next fortnight?
- Are there aspects I should be considerate of?
Kind regards,
====================
Jonathan McHugh
indieterminacy at libre.brussels (mailto:indieterminacy at libre.brussels)
Link to individual message.
Alan <gemini (a) bunburya.eu>
- 📅 Sent: 2021-08-31 20:20
- 📧 Message 2 of 3
I'm not sure if this is a response to your question or a complete
tangent so apologies if it is the latter, but I have long thought it
would be very helpful to have a centralised wiki for Gemini. Something
similar to (but less ambitious than) the excellent ArchWiki
(https://wiki.archlinux.org/). It could incorporate everything you set
out below and more, including tutorials on how to set up common software.
Questions to iron out would include where to host it and who has edit
rights, etc.
It might take a while to turn into something good and I don't know if it
could be made useful by the time of your presentation, but if others
agree that it's a good idea, over time it could turn into a valuable
resource for Gemini users old and new.
On 31/08/2021 18:52, Jonathan McHugh wrote:
> Hello all,
>
> In lieu of the upcoming talk I recently mentioned:
> => https://lists.orbitalfox.eu/archives/gemini/2021/007043.html
>
> I feel that the heterogenous ecosystem of tools may benefit from
> tighter documenting. Or at least integrating
>
> For instance:
> * The Awesome Gemini site has categories
> => https://github.com/kr1sp1n/awesome-gemini
> * Repology has packages by operating system
> => https://repology.org/project/lagrange/versions
> * Functional package managers such as Guix have details on the inputs
> required to compile tools
> =>
> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/web-browsers.scm#n695
> * Manpages providing commands
> => gemini://drewdevault.com/cgi-bin/man.sh
>
> # Is there a programmatic overview of Gemini's toolsets?
> For example:
> * One of the things Id like to do is provide an overview of which
> tools import and export into GemText.
> * I should be able to generate a selection of tools based upon
> criteria, without duplicative searching
> * It would make it easier the make quick evaluations
> * It would make it easier to make representations of this
>
> Im going to make a stab at collating representative list(s) of such
> concerns, so I can make some fun diagrams
>
> # Going forward
> * Any tips or knowledge silos I should be considering?
> * Anybody keen to help during the next fortnight?
> * Are there aspects I should be considerate of?
>
> Kind regards,
>
>
> ====================
> Jonathan McHugh
> indieterminacy at libre.brussels <mailto:indieterminacy at libre.brussels>
Link to individual message.
Jonathan McHugh <indieterminacy (a) libre.brussels>
- 📅 Sent: 2021-08-31 20:43
- 📧 Message 3 of 3
Hi Alan,
No worries, I like tangents.
Infact, Im planning on spending time looking into the concept of
interlinking gemini capsules.
Hopefully, a body of knowledge and interpretions can bring out concepts
for project planning (such
as issues management). An early foray will include generating kanban boards.
When I discussed this with some people suggestions included:
- Using federating Git forges [aa][ab]
- Creating micro servers to capture and relay very specific information
=> https://github.com/forgefed/forgefed
=> https://fedeproxy.eu/
While I havent evaluated these Git forge tools, I like the concept of
people being able to propagate their revisions effectively.
I personally would be happy to see key Gemini goto lists off GitHub or at
least on alternative servers.
Finally, I have no idea how security issues get managed for in a
decentralised community. I assume OSes such as Arch
have their established procedures, which contain both strengths and weaknesses.
====================
Jonathan McHugh
indieterminacy at libre.brussels
August 31, 2021 10:20 PM, "Alan" <gemini at bunburya.eu> wrote:
> I'm not sure if this is a response to your question or a complete
tangent so apologies if it is the
> latter, but I have long thought it would be very helpful to have a
centralised wiki for Gemini.
> Something similar to (but less ambitious than) the excellent ArchWiki
> (https://wiki.archlinux.org/). It could incorporate everything you set
out below and more,
> including tutorials on how to set up common software.
>
> Questions to iron out would include where to host it and who has edit rights, etc.
>
> It might take a while to turn into something good and I don't know if it
could be made useful by
> the time of your presentation, but if others agree that it's a good
idea, over time it could turn
> into a valuable resource for Gemini users old and new.
>
> On 31/08/2021 18:52, Jonathan McHugh wrote:
>
>> Hello all,
>>
>> In lieu of the upcoming talk I recently mentioned:
>> => https://lists.orbitalfox.eu/archives/gemini/2021/007043.html
>>
>> I feel that the heterogenous ecosystem of tools may benefit from
tighter documenting. Or at least
>> integrating
>>
>> For instance:
>> * The Awesome Gemini site has categories
>> => https://github.com/kr1sp1n/awesome-gemini
>> * Repology has packages by operating system
>> => https://repology.org/project/lagrange/versions
>> * Functional package managers such as Guix have details on the inputs
required to compile tools
>> => https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/web-browsers.scm#n695
>> * Manpages providing commands
>> => gemini://drewdevault.com/cgi-bin/man.sh
>>
>> # Is there a programmatic overview of Gemini's toolsets?
>> For example:
>> * One of the things Id like to do is provide an overview of which tools
import and export into
>> GemText.
>> * I should be able to generate a selection of tools based upon
criteria, without duplicative
>> searching
>> * It would make it easier the make quick evaluations
>> * It would make it easier to make representations of this
>>
>> Im going to make a stab at collating representative list(s) of such
concerns, so I can make some
>> fun diagrams
>>
>> # Going forward
>> * Any tips or knowledge silos I should be considering?
>> * Anybody keen to help during the next fortnight?
>> * Are there aspects I should be considerate of?
>>
>> Kind regards,
>>
>> ====================
>> Jonathan McHugh
>> indieterminacy at libre.brussels
Link to individual message.
---
Previous Thread: Upcoming Gemini Presentation, Brussels
Next Thread: [Tool Discussion][Not a Programmer] Idea i'm not sure if has been done for gemtext editing