I made a draft specification of Computer Payment File, and I would want your comments about it. (One thing that it is intended is to avoid and/or mitigate some kind of dishonesty.)

https://raw.githubusercontent.com/zzo38/scorpion/refs/heads/trunk/misc/payment.txt

๐Ÿฆ‚ zzo38

Feb 14 ยท 3 months ago

5 Comments โ†“

๐Ÿš€ stack ยท Feb 15 at 20:21:

Why? Is it something traditional banking or crypto is not addressing?

Also why here, in the least commercially-oriented community imaginable?

๐Ÿฆ‚ zzo38 [OP] ยท Feb 15 at 20:35:

For the first question, it is an independent issue from banking and cryptocurrency; it is intended to avoid the dishonesty and complexity and many other problems with existing computer payment, so that it will be independent of the protocol and also will be more secure than existing methods, and not need to be always connected to the internet forever.

For the second question, it is mainly because I do not have any better place to put it at this time.

(I think non-commercial stuff is good and that you should not try to make everything commercial, although when you really need commercial as well, there should be a better way to do it.)

๐Ÿš€ LucasMW ยท Feb 16 at 13:42:

Answering @stack, I remember this from when I've posted my idea to create a software store which would work on gemini protocol

๐Ÿš€ LucasMW ยท Feb 16 at 13:44:

" least commercially-oriented community imaginable?" I thought the was GNU, or the GPL forums. Not here.

But a lot of people here fit the description, no doubt about it.

๐Ÿš€ LucasMW ยท Feb 16 at 13:45:

Addressing OP, I've yet to read and understand the specification.

Proxied content from gemini://bbs.geminispace.org/u/zzo38/37999 (external content)

Gemini request details:

Original URL
gemini://bbs.geminispace.org/u/zzo38/37999
Status code
Success
Meta
text/gemini; charset=utf-8
Proxied by
kineto

Be advised that no attempt was made to verify the remote SSL certificate.