Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BOUNTY] Fix script responsible for preparing IPFS mirror #64

Closed
13 tasks
lidel opened this issue Sep 10, 2019 · 15 comments
Closed
13 tasks

[BOUNTY] Fix script responsible for preparing IPFS mirror #64

lidel opened this issue Sep 10, 2019 · 15 comments
Assignees
Labels
help wanted P0 Critical: Tackled by core team ASAP snapshots issues related to snapshot creation and updates

Comments

@lidel
Copy link
Member

lidel commented Sep 10, 2019

BOUNTY: $500 (how to claim?)

Summary

TODO

Pick up where PR at #67 ended and update execute-changes.sh script to:

  • Ensure there are no JS errors when pages are loaded
  • Make it possible to navigate to other articles
    • ensure relative paths work
      • on https://ipfs.io/ipns/<cid>/wiki/
      • on https://<cid>.ipfs.dweb.link/wiki/
    • When unpacked with extract_zim, all pages are named ArticleName.html but they link to other article names without .html
      • idea: for every article, create ArticleName/index.html with a redirect page to ArticleName.html (similar to this)
  • Custom footer needs to be appended to every page
  • Update footer contents
    • add link to article snapshot at original Wikipedia
      • oldid= links can be found in page sources, for example:
        href="https://tr.wikipedia.org/w/index.php?title=<title>&amp;oldid=<timestamp>"
    • add link to the source .zim file
      • for now it can be link at download.kiwix.org, in the future it will be .zim on IPFS
    • remove logos/buttons of centralized services
    • include information on takedown policy / contact (eg. if latest snapshot includes information removed in upstream wikipedia)
  • Restore original Main Page
    • every wikipedia has a Main Page under different name
      • there are scripts to find out that name and fetch original for the right snapshot, see work started in bb9f48c
      • what needs to happen is to download original, fix it up to work locally and save it as /wiki/index.html

Acceptance Criteria

  • PR with necessary changes is submitted and merged to this repo
  • Script works and enables us to produce updated IPFS mirror of the latest Turkish snapshot: wikipedia_tr_all_maxi_2019-12.zim
    • CID of a demo output is provided
@lidel lidel added the snapshots issues related to snapshot creation and updates label Sep 10, 2019
@lidel lidel added help wanted P0 Critical: Tackled by core team ASAP labels Oct 27, 2019
@lidel lidel changed the title Update footer Fix code responsible for footer update Jan 23, 2020
@lidel lidel changed the title Fix code responsible for footer update Fix script responsible for preparing IPFS website Feb 7, 2020
@lidel lidel changed the title Fix script responsible for preparing IPFS website Fix script responsible for preparing IPFS mirror Feb 7, 2020
@parkan

This comment has been minimized.

@lidel lidel changed the title Fix script responsible for preparing IPFS mirror [BOUNTY] Fix script responsible for preparing IPFS mirror Feb 20, 2020
@jnthnvctr
Copy link

@lidel when this does work - would we be pinning this on our own IPFS node (or cluster)?

@kanej kanej mentioned this issue Feb 27, 2020
9 tasks
@lidel
Copy link
Member Author

lidel commented Feb 27, 2020

@jnthnvctr I believe we would pin to cluster like we did with older snapshot, but want to create a collaborative cluster, so we host a copy, but anyone can follow and contribute – see notes in #68

@RubenKelevra
Copy link

@lidel yes, we just need to work out implementation details. I would really like to get a static JavaScript implementation which can parse the Wikipedia markup language going, so we can seperate the data from the webpage and update them individually.

This would reduce the amount of storage required massively.

@parkan
Copy link

parkan commented Mar 5, 2020

@kanej can you confirm that #70 is intending to close this issue/collect the bounty?

@kanej
Copy link
Member

kanej commented Mar 5, 2020

@parkan yes #70 is intending to close the issue and collect the bounty.

@lidel
Copy link
Member Author

lidel commented Apr 9, 2020

#70 is merged, thank you @kanej 👍 🚀

tr.wikipedia-on-ipfs.org continued in #60 (comment)

Update: @parkan reopened this so you can try doing the DAI setup

@lidel lidel closed this as completed Apr 9, 2020
@lidel lidel reopened this Apr 9, 2020
@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 500.0 DAI (500.0 USD @ $1.0/DAI) attached to it as part of the ipfs fund.

@parkan
Copy link

parkan commented Apr 11, 2020

@kanej see above! 💸

@gitcoinbot
Copy link

gitcoinbot commented Apr 11, 2020

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 3 weeks, 5 days from now.
Please review their action plans below:

1) kanej has started work.

Rework the execute changes script into a node based script.

The script will convert the extracted zim directory into a workable website, appending the Distributed Wikipedia Mirror project notes to the bottom of each page.

Learn more on the Gitcoin Issue Details page.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work for 500.0 DAI (500.0 USD @ $1.0/DAI) has been submitted by:

  1. @kanej

@parkan please take a look at the submitted work:


@gitcoinbot
Copy link

Ipfs ⚡️ A *Ipfs* Kudos has been sent to @kanej for this issue from @parkan. ⚡️

Nice work @kanej!
Your Kudos has automatically been sent in the ETH address we have on file.

@gitcoinbot
Copy link

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


The funding of 500.0 DAI (500.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @kanej.

@parkan
Copy link

parkan commented Apr 14, 2020

paid out! thank you @kanej, was the gitcoin experience smooth for you?

@lidel let's close this for real now 🙂

@kanej
Copy link
Member

kanej commented Apr 14, 2020

@parkan thanks. I had no problems, straight forward process, but I started with previous experience of ether and gitcoin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted P0 Critical: Tackled by core team ASAP snapshots issues related to snapshot creation and updates
Projects
None yet
Development

No branches or pull requests

6 participants