samizdat issueshttps://0xacab.org/rysiek/samizdat/-/issues2020-09-30T02:29:56Zhttps://0xacab.org/rysiek/samizdat/-/issues/70Configurable plugin set and strategy2020-09-30T02:29:56ZMichał "rysiek" WoźniakConfigurable plugin set and strategySince we already have a configuration system for the Service Worker (#69), we can implement a way to configure:
- [x] what plugins are loaded
- [x] what is the content retrieval strategy (that is, what order are the plugins being deplo...Since we already have a configuration system for the Service Worker (#69), we can implement a way to configure:
- [x] what plugins are loaded
- [x] what is the content retrieval strategy (that is, what order are the plugins being deployed to fetch the content)
- [x] simple order (expressed as an array)
- [x] support for more complex structures with steps involving "any of these plugins" approaches (expressed as an array inside the simple ordered array, perhaps?)BetaMichał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/67Improve/standardize/clarify language around transports, plugins, etc.2020-09-21T09:22:24ZMichał "rysiek" WoźniakImprove/standardize/clarify language around transports, plugins, etc.From Doc Edward Morbius [over at the Fediverse](https://mastodon.social/web/statuses/104899337763392473):
>>>
So, suggested clarifications (I'm not sure which are accurate):
or any HTTP(S) site able to host the content
or one or more ...From Doc Edward Morbius [over at the Fediverse](https://mastodon.social/web/statuses/104899337763392473):
>>>
So, suggested clarifications (I'm not sure which are accurate):
or any HTTP(S) site able to host the content
or one or more HTTP(S) sites also hosting the content
or one or more previously established HTTP(S) sites also hosting the content
or one or more previously established HTTPS sites which will dynamically and automatically rehost the content
or one or more previously established sites which will dynamically and automatically rehost the content using
or any any of a mesh netwoork of sites configured to dynamically host the content
Questions being:
What site(s) can / will host content?
What protocol(s) are used? HTTP(S)? Any of a set of TCP data transports? UDP? TLS-capable only? Tor? IPFS is apparently available.
Are these preconfigured and prepopulated? Preconfigured and dynamically populated? Dynamically configured?
Is the user at all aware of alternate sourcing? Are there redirects, or is this all ServiceWorker majick? (I have NFC about Serviceworker stuff, even after scanning docs).
Existing language is ... opaque.
>>>BetaMichał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/54Document possible privacy gains from using Samizdat2020-09-21T01:19:52ZMichał "rysiek" WoźniakDocument possible privacy gains from using SamizdatSamizdat can be used not just to circumvent Internet censorship, but also to provide some (limited but perhaps useful) protection to website visitors, if the ServiceWorker is configured such that it does *not* run the direct `fetch()` pl...Samizdat can be used not just to circumvent Internet censorship, but also to provide some (limited but perhaps useful) protection to website visitors, if the ServiceWorker is configured such that it does *not* run the direct `fetch()` plugin at all, relying instead on cache (if present) and on other plugins.
This would mean that after the visitor visits the Samizdat-enabled site, all requests avoid sing `fetch()` and thus (depending on plugins used) potentially completely obscure the fact that the person is trying to visit the blocked site.Michał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/40Stop relying on pubkey in gun+ipfs plugin2020-10-05T17:53:41ZMichał "rysiek" WoźniakStop relying on pubkey in gun+ipfs pluginWe need a better strategy of getting the Gun user pubkey to use in the `gun+ipfs` plugin.We need a better strategy of getting the Gun user pubkey to use in the `gun+ipfs` plugin.BetaMichał "rysiek" WoźniakMichał "rysiek" Woźniak