News for hackers. Stuff that matters.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by mmjaa on Wednesday February 21, 2018 @12:40PM (#16431265)
IPFS should be enabled and treated as a first-class service by my distro. I install said distro, it comes with a folder - and a basic service - upon which I can replace Dropbox, Facebook, and Instagram - for my target peer group, i.e. any of my friends and family who will also run the very same distro, for this purpose.

Like, plug and play OS support, and its a go.

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by braderhart on Wednesday February 21, 2018 @02:44PM (#16432322)
I agree. I am working on an Arch distro (may roll my own for containers) that includes secure decentralized storage and configuration by default, and a federated marketplace for sharing your own local and server resources.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by diggan on Wednesday February 21, 2018 @06:57PM (#16434061)
That sounds really interesting, do you have a link to a work in progress or something like that?
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by braderhart on Friday February 23, 2018 @05:10AM (#16445375)
Haha... right now I have my desktop that I can show, which isn't perfect but I have an idea of where I want to go and how to get there (mostly). I am still running i3 for compatibility, but definitely moving towards Sway.

I've seen some great looking desktops that I still need to mimic, and the make them more fluid/responsive for multiple devices. I would like to review and look at what George Singer is up to:

https://github.com/SimulaVR/Simula

Seems like he may be offering VR devices for developers that are able to demonstrate some requirements. How cool is that? I would like to take something like Sway, and add or combine it with a project similar to SimularVR, with a Vulkan backend. That is the end goal.

I will likely just start with Sway and build a kick ass plugin and application manager that uses containers. I will re-explore the current application isolation solutions, such as AppImage vs FLatpak vs Snap, but likely try my hand at building my own.

Part of that process is repeatable builds. I would like to build the OS compilation into the decentralization process, and make distributed (and localized) compilation a core component of the crypto solution, as it will later be used for rendering all types of resources on top of something like IPFS and Git.

Ideally, package maintainers will be solely focused on automated builds directly from source repos, so that everything is compiled and versioned automatically, so that you can switch software versions at anytime, with some compatibility-script support for DB and data changes.

Anyway, that is a lot of talk, so I will have to share more when I make more progress. It is a longer term goal, but feel free to help me get started:

https://discord.gg/R6NQ7aj

For example, you can see a UI kit here that I would like to utilize initially, although I am still inclined to try to implement my own idea here, which involves combining a

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by QasimK on Wednesday February 21, 2018 @05:05PM (#16433412)
I was thinking of something similar for applications. Just earlier today I needed a large dataset for some machine learning with Jupyter notebook in a git repo. I don't want to store the dataset in the git repo due to the size, and I don't really want to deal with "downloading the file if it isn't already downloaded into some location".

What would be awesome is something like this little bit of hypothetical Python code:

  import ipfs
  file = ipfs.file(FILE_HASH, keep=True, share=True)  # THIS LINE
  with open(file) as fin:
      # Do stuff like a normal file.
No need to distinguish between local files and cloud files! You can choose whether to keep the file permanently or temporarily, and whether to share it back to other IPFS nodes. You would probably need a system service to do this seamlessly as you suggested.

Sure, it might take a some time to download it at first - but you have to deal with that either way. On subsequent runs, it all just works. (I assume for popular enough files you don't have to worry about the availability of the file, especially if people tend to share back by default).

The big benefit being it is simpler to share datasets and actually use datasets - you can do both at the same time with one little file content identifier (FILE_HASH above).

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by Jtsummers on Wednesday February 21, 2018 @06:05PM (#16433770)
IPFS includes a way to mount it as a filesystem. So if you know the IPNS URL for some data, or the hash, you can access it like accessing any other file. If it's already downloaded then there shouldn't be any overhead versus just opening a file, if it hasn't it'll download it. You oughtn't need any extra library or logic for it.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by QasimK on Wednesday February 21, 2018 @06:24PM (#16433876)
That's brilliant! I think that means it should also support reading the file in chunks, as it gets downloaded, automatically.

I wonder how purging less important files is/could be handled through this? It would be good if there was some way to say, "this file is likely only going to be used temporarily (or just once), so feel free to delete it if disk space is required". That hinting might not be necessary as IPFS could use some least-recently used algorithm, but there should be some way to at least pin files, "this is really important, don't delete this".

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by foota on Wednesday February 21, 2018 @09:50PM (#16434810)
Iirc pinning is basically required for a file to continue existing.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by Jtsummers on Wednesday February 21, 2018 @09:56PM (#16434834)
To guarantee it persists, yes. But it'll remain cached if recently used on the local system until garbage collection runs.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by voltagex_ on Wednesday February 21, 2018 @10:48PM (#16435027)
Windows has been experimenting with variations of remote-files-as-local via OneDrive for some time now. I really think it needs to be baked in to the filesystem or at least the file browser to be successful, and be absolutely transparent for the application that's requesting the file.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by ericfrederich on Wednesday February 21, 2018 @04:39PM (#16433222)
Isn't this open for everyone to see though?

I think you want something like KeyBase for encrypted storage which can be shared among groups, right?

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by mmjaa on Thursday February 22, 2018 @12:23PM (#16439267)
>Isn't this open for everyone to see though?

Once the scale problem starts to be solved, the question becomes discoverability. And the answer to that is, there is an infinite namespace of things - one might suggest it up to the distro maintainers to adopt policies - behind which one can hide ones content. Like, if the distro has a button that says 'publish your stuff' and a button that says 'keep this stuff secret' but inform your closest friends when there are updates so they can get approved copies, well .. thats a distro thing.

Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by restuijs on Thursday February 22, 2018 @07:35AM (#16437104)
Why not something like dat instead? Genuinely curious.
Re:Paper review: IPFS – Content addressed, versioned, P2P fi... by nerdponx on Wednesday February 21, 2018 @03:26PM (#16432661)
Isn't that kind of thing already handled by package managers?