Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Project Gemini

geminiprotocol.net

Post reply on HN
Print view View original

101–110 of 194 posts

Re: Project Gemini

#101

Post by zzo38computer »

rzzzt wrote: post #89
1313ed01 wrote: post #84

Earlier quoted context omitted.

There are Gemini clients that can inline images, so visitors to a site could decide to enable that if they wanted to see for instance a list of thumbnails.

Are clients permitted/expected/tolerated to run off and fetch the contents of image links for inline display, once a page containing such links is retrieved?

Only if the page is inside of a ZIP archive stored on the local computer and only if the link is to a picture within the same ZIP archive. (However, it would be good to have an option to disable inline display even in that case.)

Re: Project Gemini

#102

Post by nine_k »

astrange wrote: post #98
nine_k wrote: post #90

Earlier quoted context omitted.

I would say that it comes from the military, where projects are given codenames that try hard to be opaque random monikers, and spill no beans about the nature of the project. The Manhattan Project predates mass TV, and most of it did not happen on Manhattan.

I don't mean codenames. I mean literally saying the word "project". It's like meeting a friend and saying "hello my friend I've known for the last 20 years".

Compare: "We are working on Project Paperclip" and "We are working on a paperclip". I suppose the former implies that what you're working on is not a literal paperclip (but a secret operation to snatch scientists).

So "Project Gemini" is not about, say, he constellation.

Re: Project Gemini

#105

Post by floren »

ghssds wrote: post #104
mmaunder wrote: post #92

Read the 100 word intro and still don't know what this is. Left.

It's Gopher + TLS + UTF8 + text wrapping + headers + unordered list.

more like HTTP GET - LSB bit of response code + "please send the MIME type we like, not the MIME type we hate"

Re: Project Gemini

#106

Post by Jtsummers »

andrepd wrote: post #103
mmaunder wrote: post #92

Read the 100 word intro and still don't know what this is. Left.

Are you for real? Or is this some irony I'm not getting

Presumably these are the 100 words they read:

> Gemini is a new internet technology supporting an electronic library of interconnected text documents. That's not a new idea, but it's not old fashioned either. It's timeless, and deserves tools which treat it as a first class concept, not a vestigial corner case. Gemini isn't about innovation or disruption, it's about providing some respite for those who feel the internet has been disrupted enough already. We're not out to change the world or destroy other technologies. We are out to build a lightweight online space where documents are just documents, in the interests of every reader's privacy, attention and bandwidth.

Those words don't communicate much about Gemini at all. Gemini could be a webring for all this says (it's not, but you could build one on it), or it could be something entirely different. It turns out that Gemini is a protocol and a text format, but those 100 words don't say anything about either of those things.

Re: Project Gemini

#107

Post by floren »

nine_k wrote: post #102
astrange wrote: post #98

Earlier quoted context omitted.

I don't mean codenames. I mean literally saying the word "project". It's like meeting a friend and saying "hello my friend I've known for the last 20 years".

Compare: "We are working on Project Paperclip" and "We are working on a paperclip". I suppose the former implies that what you're working on is not a literal paperclip (but a secret operation to snatch scientists). So "Project Gemini" is not about, say, he constellation.

With modern two-random-word codenames we tended to just say things like "I'm working on Crystal Banana all next week"

(Crystal Banana was a local joke codename where I worked)

Re: Project Gemini

#108

Post by immibis »

rzzzt wrote: post #89
1313ed01 wrote: post #84

Earlier quoted context omitted.

There are Gemini clients that can inline images, so visitors to a site could decide to enable that if they wanted to see for instance a list of thumbnails.

Are clients permitted/expected/tolerated to run off and fetch the contents of image links for inline display, once a page containing such links is retrieved?

Not really, in fact they're forbidden - those clients are spec-uncompliant.

Re: Project Gemini

#109

Post by Jtsummers »

rzzzt wrote: post #89
1313ed01 wrote: post #84

Earlier quoted context omitted.

There are Gemini clients that can inline images, so visitors to a site could decide to enable that if they wanted to see for instance a list of thumbnails.

Are clients permitted/expected/tolerated to run off and fetch the contents of image links for inline display, once a page containing such links is retrieved?

Permitted? Technically, it can't be stopped (well, it kind of can, see "Tolerated?").

Expected? No, it's counter to the intentions of the community.

Tolerated? Maybe. Here's a fun one (saw this in one of the past discussions dang linked): https://github.com/makew0rld/amfora/issues/199. That was over favicons, but the response would be similar if linked images were automatically fetched. Though the protocol has a "backoff" return code that could be used to throttle those things that would be less disruptive than Drew's approach of banning specific clients.

Re: Project Gemini

#110

Post by barbazoo »

Unrelated but I went to the linked website, then a while later to Youtube and now I'm getting videos recommended about the Gemini protocol that I have never heard of before today.

I'm on Arc and use uBlock Origin Lite, NextDNS, if I had searched I would have used Kagi. How do they (Google) know?

EDIT: I'm not implying that the gemini project is doing anything wrong here

Post reply on HN