Fail to load the source image

Some of the patterns still have a fallback image in patterns/<pattern name>/illustration.svg. This needs to be replaced with the final illustration.

Disposable Identity needs to be sorted into the "Identity & Agency". The current Category is [Category agency-identity not found].

Topic

Every pattern will have only 1 category. This is a first draft of the current patterns we have and some proposed categorization of them. Feedback welcome!

Discussion

These 4 categories came from what @bumbleblue shared in our meeting two weeks ago. I took our current patterns and looked at the patterns workshop we did, and then categorized them based on what seems to make most sense.

Open questions:

1. Do these categories make sense? Do we need to add, remove, or change any?
2. Do any of these patterns seem miscategorized?
3. How should categories be formatted in the markdown?

Categories

identity (& agency?)

• full address
• disposable identity
• persistent identity
• host roulette
• @ means membership

sharing (& permissions?)

• QR code verification
• paper keys
• visual hash
• standards marker
• sharing is caring
• whisper links

sync (& status?)

• network health indicator
• age indicator
• discovery pub
• physical beacon
• protocol agnosticism

moderation (& curation?)

• tombstones
• cautious optimism
• social radius slider
• content curators
• time machine
• village or city

Hi there!

I came across this via github, and it took me a while to find the link to the main site.

Would you accept a PR like this adding a link to the published library?

#69

(my earlier PR was linking to the wrong repo. #69 should be easier to merge in)

https://github.com/simplysecure/dots-patterns/blob/master/patterns/age-indicator.md

• Pattern Index page description
• Glossary page description
• Pattern Library page description

https://github.com/simplysecure/dots-patterns/blob/master/patterns/user-identity.md

https://github.com/simplysecure/dots-patterns/blob/master/patterns/cautious-optimism.md

https://github.com/simplysecure/dots-patterns/blob/master/patterns/discovery-pub.md

See full pattern at https://github.com/simplysecure/dots-patterns/blob/master/patterns/host-roulette.md

Are there any considerations to think about for formatting or otherwise for how we add images to the patterns?

I think it might be useful to add images to the examples section, i.e., a screenshot of the pattern's use in the wild in some other application. Thoughts?
@cafca @kirakirawes

Network-Health-Indicator

patterns/network-health-indicator.md describes a reporting + heartbeat system for tracking where information has been replicated and whether those replicas remain available. The design is well described, but the rationalization is currently limited to "[Use this pattern] when users are trusting your application with storing data that is important to them."

Discussion

What are broader applications of this pattern? My starting thoughts:

• Confirm that files are widely available

• Confirm that hosts supply files for a long time (reputation/trust management, maybe related to cautious optimism or conditional file sharing, or simply preventing DDoS or Sybil attacks)

• Confirm that hosts do not continue providing files after a deletion request (as part of the implementation for the tombstones recommendation)

• Identify hosts or users with similar interests (someone mirroring files on an obscure topic likely shares that obscure interest - this is an opportunity for social peer discovery)

Note that some of these applications involve UI and informing users, while others (mostly thinking of trust management) are more algorithmic and internal to the network software.

There's also a potential limitation of network health indicators in offline-first or sneakernet networks, where peers are online and synchronizing data infrequently, and disconnect from the network for large stretches of time. In these scenarios, we may need a more detailed network health history or notification protocol, such as nodes pushing notifications that they are present and ready to be tested, rather than nodes polling all peers periodically to see which are online and available.

I'd love to brainstorm more applications and add them to the proposal.

https://licensezero.com/ is one example

https://prosperitylicense.com/versions/3.0.0