Pigeon Protocol Consortium Spec Notes and Possible Changes #2

Closed
opened 2020-03-24 17:11:10 +00:00 by m3talsmith · 2 comments
Owner

What is Possible?

  • Action: remove redundant play-by-mail bullet point, "A play-by-mail (or bluetooth) file sharing app"
  • Action: Get Mike Tyson to sponsor us ;)

How Pigeon Differs from Traditional Sneakernet

  • Note: This was the best explanation of Pigeon yet!

What a Message Looks Like

  • Action: Put a diagram together that demonstrates how Example 1 and Example 2 relate to each other (or don't relate)

I Have Internet Access. Why Should I Care?

  • Note: Great list of links

Prior Art

  • Action: Add a link to SSB
  • Action: Add a link to SSBC

Constraints and Design Philosophy

  • Action: Switch Offline-first with Offline-only, then continue with the explanation that the protocol is offline only (just like SQLite), but other apps and servers can utilize it for online purposes.

The Initial Implementation Should...

  • Note: I don't think the initial implementation should Allow for importing/exporting to SSB via plugins. anymore: that is an application detail at this point I think. I would remove that and put it in the What is Possible? section now.
## [What is Possible?](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-what-is-possible) - Action: remove redundant play-by-mail bullet point, "A play-by-mail (or bluetooth) file sharing app" - Action: Get Mike Tyson to sponsor us ;) ## [How Pigeon Differs from Traditional Sneakernet](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-how-pigeon-differs-from-traditional-sneakernet) - Note: This was the best explanation of Pigeon yet! ## [What a Message Looks Like](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-what-a-message-looks-like) - Action: Put a diagram together that demonstrates how **Example 1** and **Example 2** relate to each other (or don't relate) ## [I Have Internet Access. Why Should I Care?](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-i-have-internet-access-why-should-i-care) - Note: Great list of links ## [Prior Art](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-prior-art) - Action: Add a link to SSB - Action: Add a link to SSBC ## [Constraints and Design Philosophy](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-constraints-and-design-philosophy) - Action: Switch `Offline-first` with `Offline-only`, then continue with the explanation that the protocol is offline only (just like SQLite), but other apps and servers can utilize it for online purposes. ## [The Initial Implementation Should...](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-the-initial-implementation-should) - Note: I don't think the initial implementation should `Allow for importing/exporting to SSB via plugins. ` anymore: that is an application detail at this point I think. I would remove that and put it in the [What is Possible?](https://tildegit.org/PigeonProtocolConsortium/protocol_spec#user-content-what-is-possible) section now.
m3talsmith added the
proposal
label 2020-03-24 17:11:10 +00:00
netscape_navigator was assigned by m3talsmith 2020-03-24 17:11:51 +00:00
m3talsmith self-assigned this 2020-03-24 17:11:52 +00:00

Switch Offline-first with Offline-only

@m3talsmith I may wordsmith it even further to say "Offline-first means offline-only". This will hint that:

  • It is suitable for offline-first use
  • We are not entertaining ideas that require TCP/UDP currently
> Switch Offline-first with Offline-only @m3talsmith I may wordsmith it even further to say "Offline-first means offline-only". This will hint that: * It is suitable for offline-first use * We are not entertaining ideas that require TCP/UDP currently

Got some comments from a project outsider who I asked for feedback:

There is no measurable or discernible way to say one phase is done and the next phase should begin. I could see that being a trap of being stuck in each phase for too long. Minimum requirements and nice-to-haves probably should be defined for each phase.

Got some comments from a project outsider who I asked for feedback: > There is no measurable or discernible way to say one phase is done and the next phase should begin. I could see that being a trap of being stuck in each phase for too long. Minimum requirements and nice-to-haves probably should be defined for each phase.
Sign in to join this conversation.
No Milestone
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: PigeonProtocolConsortium/Protocol-Spec#2
No description provided.