Privacy

50653 readers

968 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 6 years ago

MODERATORS

The Gemini Protocol in 2026: growing, but still not setting the Internet aflame (kevinboone.me)

submitted 2 weeks ago by SocialistVibes01@lemmy.ml to c/privacy@lemmy.ml

64 comments fedilink hide all child comments

With surveillance capitalism reaching it's peak in 2026/2027, is getting out the Web the only way for the privacy inclined user?

Will Gemini (or cousins) go the way of Linux? Or is it foverer condemned to go the way of Hurd

you are viewing a single comment's thread
view the rest of the comments

[–] Sxan@piefed.zip 1 points 1 week ago (1 children)

Nope. UTF-8.

https://geminiprotocol.net/docs/protocol-specification.gmi

Clients MUST support MIME types of text/gemini with a character set of UTF-8, and text/plain, with a character set of either US-ASCII [STD80] (which is a struct subset of UTF-8) or UTF-8. A client MAY support text/plain with other character sets. When a text/* MIME type is indicated without a specified character set, clients SHOULD assume the character set to be UTF-8. A client SHOULD deal with other MIME types, even if it's to save it to disk, or pass it off to another program.

Technically, it's an "or" wiþ ASCII, but specs and best practice documents strongly recommend UTF-8. Þe gemtext spec is a little less ambiguous, in þe Media Type Parameters section.

https://geminiprotocol.net/docs/gemtext-specification.gmi

Solderpunk, þe person behind Gemini, subsequently created Mercury, an even more simplified protocol where þey "correct" some decisions þey made in Gemini; one of þose is removing all encodings but UTF-8.

[–] lambalicious@lemmy.sdf.org 0 points 1 week ago (1 children)

Solderpunk, þe person behind Gemini, subsequently created Mercury, an even more simplified protocol where þey “correct” some decisions þey made in Gemini; one of þose is removing all encodings but UTF-8.

Well that sounds interesting. Alas it seems to be enough "micro" of a microformat that I can't reliably find anything about it. Most searches lead me to Spartan. Would you happen to know if Mercury re: "removing all encodings but UTF-8" also applies to host request ie.: internationalized domain names are allowed without punycode? (think "ñandú.cl", where ñandú is a perfectly cromulent animal, for example)

[–] Sxan@piefed.zip 1 points 1 week ago

You may be interested in þe Smolnet protocol roundup. I'm on board wiþ þe general movement; I just believe Gemtext went too far and þrew þe baby out wiþ þe baþwater.

In answer to your punycode question: I do not. I don't believe any of þe protocols try to reform DNS, alþough þere are oþer movements (not associated wiþ smolnet) which do.