Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.infosystems.gemini > #165

Re: In the news

Show all headers | View raw

David <david@arch.invalid> writes:

> On 30/01/2022 01:22, rtr wrote:
>> David writes:
>> 
>>> Article in The Register about Gemini with lots of links
>>> https://www.theregister.com/2022/01/27/gemini_protocol/
>> Also what's with this fella:
>> 
>>> A post this week gained a lot of traction on Hackernews forums, when a
>>> software engineer calling themselves "マリウス" – that's "Marius" to
>>> gaijin – called it "solutionism at its worst". They argued in a blogpost
>>> that Gemini is an answer to a problem that doesn't exist and encourages
>>> a bunker effect, excluding people who use ordinary web browsers, perhaps
>>> due to accessibility issues.
>> I'd argue that gemini is an answer to a problem that does exist. And
>> frankly, I don't think it was ever an issue for geminauts whether people
>> would or would not be excluded from gemini. It exists by itself as an
>> independent means of obtaining information. For that alone, it is really
>> great.
>
> Indeed! Suppose Gemini built on HTTP(S) instead of the current TOFU
> approach, and used AsciiDoc, MarkDown or whatever as a default text 
> format ...
> - Would http(s):plain/markdown have a catchy name, say Mercury?
> - Would such beautiful clients exist like Amfora and Lagrange?
> - Would there be concerns about privacy that do not exist with Gemini?
> - Would there be a tangible community around it, a Wikipedia page?
>   This newsgroup?
> I doubt it. Or is it just luck, that Gemini became quite popular?
> Maybe it's as simple as that: a blog post by an influential hacker
> once got enough clicks on Hackernews. At least that's how I got to
> know of Gemini, if I remember correctly.
>

Honestly, I don't think it's just luck. I think the reason why gemini
became ``popular'' is because it tried to do something different rather
than expand on HTTP(S) for the nth time. I think this is the reason why
the author's arguments missed the entire point of gemini. It was never
about ``giving access to everyone'' it's about giving them a choice.

The reason why I'm using gemini is because it's convenient for me to
keep a blog in gemini than in a normal LAMP/LEMP stack. My VPS just has
a gemini directory that I rsync from my local machine. The thought of
having my blog being accessible to everyone and their grandma never
crossed in me. If I wanted that I would have hosted my blog in HTTP
instead of gemini.

>> I took the liberty to skim this fella's blog here:
>> https://xn--gckvb8fzb.com/gemini-is-solutionism-at-its-worst/
>> It seemed to me that he is a developer of something called
>> Superhighway84 which seemed to be a USENET clone from I read about it.
>> On that, I find it funny that he is talking about Gemini being ``an
>> answer to a problem that doesn't exist'' when he himself have created
>> ``an answer to a problem that doesn't exist'' with his Superhighway84.
>
> Superhighway84 seems similar to Usenet regarding the organisation of
> messages with groups, posts and threads, but data transfer is
> different:
> - The data of the messages is kept locally in a database (OrbitDB).
> - Changes to the database are propagated to and from connected peers.
> - Peers are connect via the IPFS protocol.
> - There is no central server (or few servers as in Usenet?).
> - When installing IPFS on your machine, the software comes with a set
>   of pre-configured peer addresses to connect to initially
>  (bootstrap).
>
> So there's no single point of failure, which is impressive in itself.
> Are there other notable uses of IPFS, would sci-hub be one (or is it)?
>

I think the idea underneath is the same. It's just that its using
IPFS instead of NNTP. USENET is also decentralized, it's just that most
of us don't bother to install INN and just connect to a USENET
provider. Also, IPFS is a weird hodgepodge protocol.

Funnily enough, I was reading a lot about IPFS a few days ago because I
thought it's a neat protocol with all the fancy modern web crap that
they've pulled in their website. But then I came across this guy's blog:

https://fiatjaf.com/d5031e5b.html

Which promptly killed all of my enthusiasm with IPFS. It seems like a
half-baked protocol that sounds neat in theory but is quite bad in
practice. I don't want my files having anything to do with something
like that.

-- 
Give them an inch and they will take a mile.
--
gemini://rtr.kalayaan.xyz

Back to comp.infosystems.gemini | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

In the news David <david@arch.invalid> - 2022-01-29 19:07 +0100
  Re: In the news rtr <rtr@haraya.invalid> - 2022-01-30 08:22 +0800
    Re: In the news David <david@arch.invalid> - 2022-01-30 11:02 +0100
      Re: In the news news@zzo38computer.org.invalid - 2022-01-30 18:51 -0800
      Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
        Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 10:16 +0000
          Re: In the news Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2022-01-31 14:01 +0000
            Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 15:56 +0000
            Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:12 +0800
          Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:10 +0800
            Re: In the news Dan Purgert <dan@djph.net> - 2022-02-01 09:42 +0000
    Re: In the news oldernow <oldernow@dev.null> - 2023-12-18 19:55 +0000
      Re: In the news Kestral Gaian <kes@kesgai.com> - 2023-12-22 00:23 +0000
        Re: In the news Denez Van Dyck <denez@vandyck.invalid> - 2023-12-22 08:28 +0000
        Re: In the news oldernow <oldernow@dev.null> - 2023-12-26 20:28 +0000
          Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-09 16:27 +0000
            Re: In the news SugarBug <3883@sugar.bug> - 2024-01-09 12:18 -0600
            Re: In the news oldernow <oldernow@dev.null> - 2024-01-26 14:01 +0000
              Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-26 18:09 +0000
                Re: In the news oldernow <oldernow@dev.null> - 2024-01-27 19:31 +0000
                Re: In the news news@zzo38computer.org.invalid - 2024-01-28 10:53 -0800
          Re: In the news news@zzo38computer.org.invalid - 2024-01-09 14:23 -0800
  Re: In the news Ben <benk@tilde.team> - 2022-01-30 14:43 +0330
  Re: In the news bunburya <bunburya@tilde.club> - 2022-01-30 12:53 +0000
    Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
      Re: In the news bunburya <bunburya@tilde.club> - 2022-01-31 11:13 +0000
        Re: In the news Jason McBrayer <jmcbray@carcosa.net> - 2022-01-31 09:42 -0500
          Re: In the news !nv4l1d <invalid@invalid.com> - 2022-02-01 03:06 +0000
        Re: In the news rtr <rtr@haraya.invalid> - 2022-02-04 15:26 +0800
    Re: In the news Christian Seibold <krixano@mailbox.org> - 2022-01-31 16:06 -0600

csiph-web