You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it will fit a beginner's guide such as your project, since it's better made approachable with more formatting options (bold, italics, inline links), for which Gopher-style protocol such as Gemini will be a constraint.
However, you might find it useful for internal and informal notes that fellow retrocomputing geeks probably would appreciate more than bloated HTTP websites (GitHub, GitLab, hell even Gitea). Better way to approach this would be to think carefully of what audience is expected first.
Log outputs, screenshots, questions?
No response
How to contact you
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@vintprox Hi Rodion. Great input, thanks for that. 🤛 I will read the information in your link as soon as possible. Keeping it as simple as possible is always welcome. As you mentioned above, it is a question of the intended audience of this project. At this point I'm a bit stuck with how to set this whole thing up. While my main goal for my own further software development, web and social media usage is clearly geared towards full control and ownership of my data and preventing vendor and platform lock in, I think this project itself is not wrong placed here on GitHub. It is intended to become kind of a reference point for people who want to learn more about alternatives to centralized systems. I'm thinking about setting up a let's say reference project on Gemini and document it inside this repo. This would allow us to have a live example using the technology we describe in here. This means I would work through the Gemini info you provided and then open an issue in here to set a reference project up with Gemini? What you think?
I'm thinking about setting up a let's say reference project on Gemini and document it inside this repo. This would allow us to have a live example using the technology we describe in here. This means I would work through the Gemini info you provided and then open an issue in here to set a reference project up with Gemini? What you think?
What is the topic, opinion, or issue you want to talk about?
Just stumbled upon an alternative format for authoring, and it's famous for being minimalistic, so be forewarned.
https://techhub.social/@vintprox/109491849918410041
Not sure if it will fit a beginner's guide such as your project, since it's better made approachable with more formatting options (bold, italics, inline links), for which Gopher-style protocol such as Gemini will be a constraint.
However, you might find it useful for internal and informal notes that fellow retrocomputing geeks probably would appreciate more than bloated HTTP websites (GitHub, GitLab, hell even Gitea). Better way to approach this would be to think carefully of what audience is expected first.
Log outputs, screenshots, questions?
No response
How to contact you
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: