Follow

ok so after coming down the practical realities of hosting a static site using IPFS is still kinda sketchy and IDK if I want to mess around with all that plus the whole decentralized aspect kinda rings a bit hollow when it seems like most actual users are going to be interacting with the portal at ipfs.io. plus the whole third party pinning services thing and file coin, kinda sorta like its actually just a regular corporate entity with weird ideas about were to stick files.

IDK I still really want to find something to do with this it just kinda feels like a box of frogs right now.

ยท ยท 3 ยท 0 ยท 2

@tastytentacles and not the kind of frogs one creates universes with, aye ;3 ?

thanks for sharing your ipfs experience btw :3

@tastytentacles Its security is also a bit iffy. I was going to set up a node on my homeserver, but while trying to lock it down, I discovered that it, by design, probes your LAN for nodes, and there was no way to turn that off and tell it to just use the internet, or to give it a list of known nodes on the LAN instead of it probing on its own. Yeah, fuck that.

@tastytentacles i was imagining that it would be an improved version of bittorrent, so i could efficiently track and share my data collection.
also i've read recently that they were trying to introduce censorship capabilites, but i couldnt find any hard evidence to it.
regarding the ipfs.io portal: doesnt it have the same adoption issues like matrix have currently? (most of the users are using the matrix.org homeserver)
however the tech allows this to change, and any new server can take matrix.org's place. i imagine that's true with the ipfs.io gw portal, so i wouldnt see it as an ipfs design issue

@nekomata its 100% not a design issue yet and unless I understand wrong I think the final goal is to have accessing the network require running your own note / portal its just a red flag for me because I have seen to many optimistic projects build out stop gap solutions like that but then double down on the stop gap instead of delivering the original design.

like I worry that the computational requirements of running a node will push end users towards just using portals while nodes get turned into servers with extra steps, which they are kinda doing anyway with the paid hosting services. might pull the whole project away from being a distributed project to a decentralized project which would be disappointing.

Sign in to participate in the conversation
koyu.space

We create internet services for you and your friends