Hello everyone!

I created a file transportation service for IPFS, more like an upload service I guess.

My big ambition through this project is make IPFS more accessible to the general public.

I'm currently working on encryption using AES-256 and mobile version for iOS and Android.

I hope this can help in any way.

Thanks!

https://globalupload.io

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

@alanshaw can we follow up on deploying all the demos to IPFS and link them from a friendly URL so that we can share them here? //cc @victorbjelkholm for deployment

In the lead-up to the Developer Meetings we asked people to submit information about their projects to an IPFS User Registry. (see the announcement ). Now that we're able to render awesome-ipfs as a website, let's make sure everyone from the user registry (those who indicated that we can display their info publicly) is listed in awesome IPFS.

Access to the responses from the User Registry form is restricted. I can pass the necessary info to whoever takes on this task.

Note: We also have an older informally-build user registry with about 80 projects listed. We should check that one too and see if there are any missing from awesome-ipfs.

There is amazing ipfs-based work cropping up all the time. This repository is barely catching any of it. It isn't even capturing the most prominent work, despite the fact that the IPFS maintainers are very aware of that work and @jbenet is featuring that work in his presentations.

I think this is a sign that we're using the wrong approach to gather this information and keep it up to date. We should reconsider the whole thing in order to figure out the best process for featuring great ipfs-based work and allowing people to get their work featured.

Do people have ideas about what would be the right tool to keep a robust list of ipfs-based work, apps, tools and platforms?

It should

• Aim to toward comprehensiveness -- we want to know how many people are building stuff on IPFS, and what they are building
• Allow people to submit their work for inclusion in the list
• Allow maintainers/moderators to feature especially impressive or exciting work
• Have links back to the work itself and include ways to find the work's maintainers
• Allow us to categorize different work -- ie. "Social Platforms and Messaging Applications", "Media Platforms", "Archiving", "File Sharing", etc. or "IPFS+Ethereum", "Distributed Apps", etc.

We should also prominently display the "featured" work in multiple places with links and instructions for submitting your own work.

Link: https://github.com/ipfs/community/blob/master/contributing.md is a 404

Now we have a website! But many of the awesome projects don't have any labels. We should try to come up with a taxonomy and label all of them, then make sure the search and navigation between labels work.

Hello, please add my software Java-IPFS-Client, it is a lightweight IPFS client written in Java (portable to every computer)

Link: https://github.com/RHazDev/Java-IPFS-Client

Even after we made it a little bit more clear to the users in #159, since #130 all the edits on the README have to be made in the /data files. This is very much counterintuitive to what the standard awesome repositories, and I find it annoying that I have to remember people to do it.

Now I am in solution mode and I should not be: If we could generate the data from the README and enrich it with information/pictures in /data it could be a quick win for all the contributors as well as easier to maintain. That is one suggestion. An other one that I had in mind is to decouple the website with this repository and have a scraper taking care of these information.

I have noticed that some elements that are actually paid-services, are marked as "Apps" or even "tools", but those are nor apps nor tools, but Services (mostly paid).

Should we consider adding a new Services section?

Currently, the hashes are a bit long and breaks the layout a bit when included. It's a shame as we want to show the hash especially for datasets so they are easy to copy-paste/verify manually.

One idea could be to abbreviate the hashes (which we do now) and expand then without having the layout to reflow when hovering over the card (we don't do this currently).

Other ideas are welcome :)

None of the apps/companies mentioned in @jbenet's devcon2 talk (uPort, mediachain, akasha, openbazaar, etc.) are listed in this repo. They should all be added.

As mentioned before, we should have a "Featured" label that will make the project be first in the ordering within a category or other label.

so yea, what should go into that section exactly? maybe something like the xkcd clone?

Now that this repo is more a site than just a README, it would be a good idea to add build instructions (even if it’s just “run make build”).

While we’re at it, it might also help to clarify somewhere that the files to change when submitting a PR are in /data and that the README is generated from those. (That’s strongly implied in CONTRIBUTING.md, but that file never straight-up just says this. It’s also a doc someone could easily miss, especially if they are familiar with what awesome-ipfs was just a few days ago.)

I just wrote IPFessay, which is an app that lives fully on IPFS and lets you publish uncensorable essays. I'd appreciate it if you could link to it!

• https://github.com/whyrusleeping/git-ipfs-rehost
• https://github.com/cryptix/git-remote-ipfs
• Commits in IPFS Discussion

i think we should allow putting "Discussions" here that are important, things like the above commit discussion, or the CRDTs discussion

So far, we have a technical checklist and also some in-head (me and my opinion) policy on what to merge and what to reject.

What we should do is to have a POLICY.md which clearly outlines what will be accepted and what will be rejected, so anyone can start managing and merging PRs here.

As a first step, we definitely want entries to follow our "Code of Conduct", but we might want to make it even stricter in terms of what goes into this list.

We have a ton of new demos, tutorials, apps and posts to share.

Hi guys,

I wonder if you guys have a standard way of approaching a website so they can implement IPFS.
I am asking because I am seeing that MusicBrainz is having serious service issues and might be a good service to talk to.

Check this out https://blog.musicbrainz.org/2016/05/22/server-capacity-update/

https://medium.com/@tonywillenberg/web-3-0-a-truly-democratised-internet-f4b06cb4077b is an article written about IPFS by Tony Willenberg (https://twitter.com/TonyWillenberg).

I want to add it, but not sure where. Doesn't fit under "Articles - Press" in my mind, so where would we put it?

We should have one for this repo.

Suggestions of things to check for:

• 80 char wrap. I don't care, but some people do, not hard to check for.
• Alphabetized
• Date checking for articles

Anything else?

See also ipfs-inactive/docs#57

The description here is great, but we should prefix it with either 🤖 or 📚 or both. It should also have the topics type:website or type:documentation or both.

Hi, guys. I've developed a file sharing app, please see https://ipfs-forever.github.io. The source code is here.

https://github.com/jrswab/nebulus and https://github.com/jrswab/archivatory

If I click on the link, it tries to open https://github.com/ipfs/awesome-ipfs/blob/master/decentralized.cloud. If I manually open decentralized.cloud in the browser, it redirects to https://filenation.io/. So change the link to https://filenation.io/ or is 'SnapCloud' something else?

See #20

xfce-screenshooter-ipfs-support - A fork of xfce-screenshooter with IPFS upload support!(no native ipfs-nodes required!).

i like making simple single-page apps that are tools that need no servers.

examples: https://github.com/ipfs/examples/tree/master/webapps

need more

The redirect script ipfs-userscript linked in this repo wasn't working for me, neither the original version, nor the current one, which I had a little help in, so I tried to do it myself. I'm new to JS, so it's in part inspired by the JS code in the currently dormant Safari extension (ipfs-catcher).

https://github.com/JayBrown/IPRedirect

Since there's no quick toggle on/off, the script should eventually test if the local node is running, i.e. something like a quick curl to localhost:8080. If it returns "000", the node is inactive, otherwise it's running, i.e. returning "404". (I had already tried it with jQuery.ajax, but it wasn't stable; at first try it didn't redirect, then afterwards it did, but when the node was disabled, it still wanted to redirect to localhost.) So if anyone knows how to easily check for node enabled/disabled in a userscript, I'd be very grateful.

See also the related question here: http://stackoverflow.com/questions/43901231/ipfs-javascript-check-for-404-status-from-localhost8080-to-determine-in-brow

https://github.com/ipfs/ipfs/blob/master/papers/ipfs-cap2pfs/ipfs-p2p-file-system.pdf?raw=true

https://decentralized.cloud/ Decentralized Cloud enables users to quickly and easily transfer large files of any format using IPFS.

This link: http://whatdoesthequantsay.com/2015/09/13/ipfs-introduction-by-example/

• HiLoader.exe - An free tool for sharing files via IPFS with "social locker" feature

IPFS Desktop - Run your IPFS node on your machine without having to bother with command line tools. Manage your node, add your files, easily change the settings... everything from just one interface.

in README.MD is not accessible

See also 2fee357

just made this: https://github.com/jbenet/http2ipfs-web

Hey guys!
Is anybody having a look at the PR?
There are some that are still waiting and the changes are not that complex... :)

Add @noffle's https://github.com/noffle/ipget

There should be more! @sindresorhus asked for some more when this was added to the main awesome list.

https://github.com/nodesphere/nodesphere

Nodesphere is an ambitious project designed to connect the data sources that we care most about into a single unified dashboard:

• Our social networks
• Our curated collections
• Our sense-making information
  Nodesphere is a collection of isomorphic visualization-style interfaces. Each interface has particular strengths, so the user can switch between interfaces depending upon the data set and the desired interaction style.

Semantic Crunching
Nodesphere uses semantic crunching technology, which reduces data inputs into their atomic semantic nodes. Regardless of the data source, the important knowledge is digested into an interconnected graph, with appropriate connections between tags, categories, peoples' names, etc.

Open Graph Stack
The primary interface will be through the visualization layer, which allows filtering, sensemaking and visual navigation of all data (technology: javascript visualization)

• Each individual or organization will have their own instance of a graph server, to store relationships between their most used data (technology: graph database)
• All data may optionally be reflected to permanent distributed storage layers (technology: IPFS)

Status
Nodesphere is in active development, focussing on:

• Multiple visualization interfaces
• Morphing between visualizations
• Reading data from multiple backends, starting with IPFS

Epocum - Smart sharing platform that allow to generate and share decentralized link over social for advertising purpose.

So, we're starting to have a lot of items here that are a bit dis-organized and not very pretty to look at neither discoverable.

I propose we add Hugo to this repository and move all the listens to a data file (yml/toml/json format) and then build a html page that we can deploy on awesome.ipfs.io or something like that + to update the listing in the readme.

What do people think about this?

The Beaker Browser browses Dat and IPFS webpages. It is usable now, although experimental.

There's an article listed from the README:

• Downloading nodejs versions with nvm/n over IPFS (ipfs.io)

It seems to be unavailable... And when I try to find QmUx363UFtgiQqkHHsPK3TSDmwoALDo2hrbMWbcxjH2vFc it seems to not exist...

Maybe it's a typo?

Hi, am building a new platform, Blokaly, based on IPFS. Please can you add this into the app list?

Platform: https://www.blokaly.com
Doc: http://blokaly.readthedocs.io/en/latest/en/usage/

Thanks,

For two reasons:

1. Once we have a lot of videos, it'll be too much for a normal PC to render efficiently, thumbnails would be way more performant.

2. YouTube ads their own tracking with embedding, meaning that YouTube can track visitors of the website, while the website is generally tracking-free right now. Replacing embeds with thumbnails would make adblock/privacy extensions should less misleading icons