# DWeb-ready™ We need to check wherever websites built with Sutty® Technology (specifically, the ones using our base themes) will work properly in the Distributed Web. There's many angles to revise: ## [Sutty's Jekyll themes](https://0xacab.org/sutty/jekyll) - Do they point to HTTP/S resources? - [site-analyzer] allows us to automatically detect many bugs, but some themes may intentionally depend on HTTP/S: - Do they even make sense in the DWeb without them? (Sorted by least useful to more useful in the DWeb) - [priority:low] [editorial-autogestiva-jekyll-theme](https://0xacab.org/sutty/jekyll/editorial-autogestiva-jekyll-theme) ([demo](https://subelamarea.sutty.nl/)) and other private forks are ecommerce themes that depend on our Spree API to be accessible for the cart system to work. Without it, it's just a glorified catalogue of products (but it might be what we want.) - It should be able to work while the HTTPS API is accesible, so we should check wherever we have CORS - It should make it clear when the API isn't available in the UI - [radios-comunitarias-jekyll-theme](https://0xacab.org/sutty/jekyll/radios-comunitarias-jekyll-theme) ([demo](https://radio.sutty.nl/)) is a site for community radio stations with general information about the station and the schedule. It also features a live player (dependant on whatever online stream the station has) which wouldn't work as-is in the DWeb. - [sutty-donaciones-jekyll-theme](https://0xacab.org/sutty/jekyll/sutty-donaciones-jekyll-theme) ([demo](https://donaciones.sutty.nl/)) is effectively a LinkTree clone, originally designed for linking to donation things (PayPal, MercadoPago, Bitcoin wallet, etc). In the DWeb, it could still work for crypto wallet links. - [adhesiones-jekyll-theme](https://0xacab.org/sutty/jekyll/adhesiones-jekyll-theme) ([demo](https://adhesiones.sutty.nl/)) has change.org-style form, but it requires accessing the panel's API. Without it, you can still see the the other published signatures and read the claim of the petition. - WAY FORWARD: check other themes systematically - Do they setup the right things to show the right 404 in the different DWeb platforms? - [IPFS](https://docs.ipfs.tech/how-to/websites-on-ipfs/redirects-and-custom-404s/#evaluation) - TODO: check if it supports percent encoded URLs, for URLs with spaces and also non-english sites - TODO: look up how other protocols do it - TODO: ask mauve on how this is handled for BitTorrent in Agregore - Do they use relative paths for addressing files? This is important to work properly in IPFS gateways using [path based resolution](https://docs.ipfs.tech/concepts/ipfs-gateway/#path). - IPFS docs suggest [using a Node.js tool](https://docs.ipfs.tech/how-to/websites-on-ipfs/static-site-generators/#jekyll) post-build to turn paths into relative - The few Hypercore gateway software that exists (mauve's [hyper-gateway](https://github.com/RangerMauve/hyper-gateway) for example) use the problematic path based resolution. However, few people actually use these gateways and the Hypercore team doesn't host any officially. - This is low priority as it is totally legacy, but generally Sutty websites have entirely relative paths because of [jekyll-relative-urls](https://rubygems.org/gems/jekyll-relative-urls). - distributed.press uses absolute paths, in fact. ## The panel/CMS itself - Does it upload pasted HTTP/S assets like images to the DWeb? - Not yet. [Issue](https://0xacab.org/sutty/editor/-/issues/62) - When uploading assets, are they pointed to their relative address in the site? - No, it points to an HTTPS URL to the panel. [This issue tracks it](https://0xacab.org/sutty/editor/-/issues/59) ## Specific sites - How do we handle embeds from HTTPS websites? We use [jekyll-embed-urls](https://0xacab.org/sutty/jekyll/jekyll-embed-urls) for automatically embedding links. - IDEA: We could detect on jekyll-embed-urls if it's building for the DWeb and use OGP only cards (rendered locally) - We would have to build twice, one with normal embeds and another with OGP cards. - Or do post-processing before publishing to DWeb - IDEA: Explore using [WebRecorder](https://webrecorder.net/) and linking to the archive. [site-analyzer]: https://gitea.nulo.in/Nulo/site-analyzer