samizdat issueshttps://0xacab.org/rysiek/samizdat/-/issues2020-12-29T22:58:24Zhttps://0xacab.org/rysiek/samizdat/-/issues/76Other work in the area2020-12-29T22:58:24ZMichał "rysiek" WoźniakOther work in the areaThis issue will gather links to similar projects or related developments.This issue will gather links to similar projects or related developments.https://0xacab.org/rysiek/samizdat/-/issues/53Add/improve live examples to better illustrate functionality2020-09-07T21:19:08ZMichał "rysiek" WoźniakAdd/improve live examples to better illustrate functionalityWe have [an example page](https://samizdat.is/example/) that only works after Samizdat is loaded (that is, after at least one visit to [the Samizdat site](https://samizdat.is/). This is useful, but can be improved upon:
- [ ] multiple d...We have [an example page](https://samizdat.is/example/) that only works after Samizdat is loaded (that is, after at least one visit to [the Samizdat site](https://samizdat.is/). This is useful, but can be improved upon:
- [ ] multiple different examples, showing how Samizdat behaves in different failure modes (depending on what we can simulate just with `nginx` configs, I guess)
- [ ] `404 Not Found`
- [ ] `500 Internal Server Error` and/or some other 50x errors
- [ ] blackholing the request (request accepted, no data returned, but connection not terminated, just hanging)
- [ ] response throttled down to a trickle (request accepted, but data returned so slow it's basically useless)
- [ ] example of `fetch()`-less Service Worker to demonstrate possible privacy gainMichał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/52What is max age samizdat can survive after blocking?2020-09-07T21:05:06Z0xf005ecWhat is max age samizdat can survive after blocking?Hi! Saw your presentation at HOPE and would like to contribute to this project.
The last time I checked this idea, it was non-viable due to 24h limit browsers put on service workers to avoid abuse (e.g. ransomware style attacks after hi...Hi! Saw your presentation at HOPE and would like to contribute to this project.
The last time I checked this idea, it was non-viable due to 24h limit browsers put on service workers to avoid abuse (e.g. ransomware style attacks after hijacking victim's domain name).
Has this limitation been lifted yet?https://0xacab.org/rysiek/samizdat/-/issues/51ServiceWorker not kicking in on force-reload2020-09-08T11:30:45ZMichał "rysiek" WoźniakServiceWorker not kicking in on force-reloadRelevant:
- https://stackoverflow.com/questions/37559415/how-to-make-serviceworker-survive-cache-reset-shiftf5
- https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle#shift-reload
Might require a simple FAQ ...Relevant:
- https://stackoverflow.com/questions/37559415/how-to-make-serviceworker-survive-cache-reset-shiftf5
- https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle#shift-reload
Might require a simple FAQ entry. Unless we want to muck around with how force-reload is handled.Michał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/48Test and document Samizdat running in subdirectories2020-07-08T16:39:48ZMichał "rysiek" WoźniakTest and document Samizdat running in subdirectoriesHow does Samizdat react to being deployed *simultaneously* in different locations on the same website, especially when it's deployed in both a location and its sub-location?How does Samizdat react to being deployed *simultaneously* in different locations on the same website, especially when it's deployed in both a location and its sub-location?Michał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/46Research, test, and document if/how Samizdat could be used behind NAT/firewall2020-10-05T17:50:10ZMichał "rysiek" WoźniakResearch, test, and document if/how Samizdat could be used behind NAT/firewallAn [interesting question was asked on the Fediverse](https://mastodon.sdf.org/@Shufei/104469126475735667): could Samizdat be used to host content behind NAT/firewall.
The minimal requirements are:
- a HTTPS-enabled site to kick-start S...An [interesting question was asked on the Fediverse](https://mastodon.sdf.org/@Shufei/104469126475735667): could Samizdat be used to host content behind NAT/firewall.
The minimal requirements are:
- a HTTPS-enabled site to kick-start Service Worker (no need to host actual content there);
- a way to push content to wherever the deployed plugins can `fetch()` it from.
With current plugins this would mean:
- hosting a skeleton site on some public hosting service (GitLab pages, etc)
- figuring out if pushing content to Gun and IPFS can happen from behind a firewall, or if running Gun and IPFS daemons behind firewall works well.
Hypothetically this would be easier with a plugin using anything that does not require a publicly accessible daemon, like pushing content to WebArchive and fetching from there.https://0xacab.org/rysiek/samizdat/-/issues/32Simplify and document the deployment process2020-10-05T17:54:24ZMichał "rysiek" WoźniakSimplify and document the deployment processCurrently deployment process of Samizdat is unclear, convoluted, and undocumented. This needs to change if Samizdat is to become useful.Currently deployment process of Samizdat is unclear, convoluted, and undocumented. This needs to change if Samizdat is to become useful.BetaMichał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/30API Documentation2020-09-08T18:36:07ZMichał "rysiek" WoźniakAPI DocumentationSamizdat is stable enough that it makes sense to write documentation for the API.Samizdat is stable enough that it makes sense to write documentation for the API.BetaMichał "rysiek" WoźniakMichał "rysiek" Woźniakhttps://0xacab.org/rysiek/samizdat/-/issues/27Measuring usage2019-12-16T00:56:03ZMichał "rysiek" WoźniakMeasuring usageSamizdat will need a way of measuring and reporting on how effective it is. That's a complicated problem. On one hand Samizdat will be used by readers in oppressive regimes, and their privacy and safety is crucial.
On the other hand, if...Samizdat will need a way of measuring and reporting on how effective it is. That's a complicated problem. On one hand Samizdat will be used by readers in oppressive regimes, and their privacy and safety is crucial.
On the other hand, if Samizdat cannot report on its effectiveness, how will website admins know it works at all?.. And how will organizations know it is worth deploying.
Possible approaches to this problem:
- keeping stats in Gun
- using Google Analytics or some other major provider (bleh!)
- using a Matomo instance on a different IP address that is not likely to be blocked
Questions:
- would it make sense to have global Samizdat stats (that is, for all Samizdat-enabled sites)?Beta