Notices tagged with ipfs

@feld @p @silverpill @jeffcliff ok, very interesting to read these thoughts on the degraded state of IPFS and how unfit it currently is for use with fedi (in browser as an add-on and as a server).

it fits with my thesis that foss on m$github is getting slowly compromised, by the shell accounts that the corporate state have on that weaponized platform.... a controlled platform, at best, and a platform that deanonymizes devs, which is a way to control them at the very least.

Id consider going back to 2021 and looking at their codebase then, and comparing it to today, there were some very prominent independent media folk talking about IPFS back then and so i suspect that THAT is when the controlled demolition may have started. My understanding is once the corporates have their sights on a codebase they force the programmers to accept bad tradeoffs. Trade-offs exist everywhere, and permutations of tradeoffs can be chosen ad-infinitum. my learned experience is that foss on mshithub tends to not improve in ways that would allow it to compete with corposhit, especially in the #ux department.

to accelerate :butterfedyC: fediverse centric adaptations, just over a week ago i wrote about having #ipfs on another repo and i now, having read both your comments i think it may need to indeed be a fork. a week ago i suggested the acronym DCN (decentralised content network) a tongue-in-cheek reference/reversal of CDN....

so yeah if anyone wants to run with that idea, u have my blessing

#dcn #msgithub #getoffgithub

@silverpill @smallcircles Interesting thoughts.

The biggest thing pushing me away from #ActivityPub is that I want a content replication system, similar to #ipfs :
- I want an efficient way to serve content to the global network and save that content offline without losing signatures of authenticity.
- I want all the data hosted by one client/server to be transparently loadable by any other client/server with permission.
- I want clients to be able to connect to each-other, without servers.
1/3

Merged: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3654

>implementation of an upload system for attachments using IPFS.

Nowadays I think #IPFS is not the right choice (see FEP-ef61 for a better solution), but nevertheless, it is good that this topic is getting more attention

5年ぶりくらいにシリーズを更新した #ipfs
#ipfs体験記 20:curlは8.4.0からIPFSに対応している - Kotet's Personal Blog https://blog.kotet.jp/2023/10/curl-ipfs/

#アドベントカレンダー どこかに参加してみたい気もする。
あったら読んでみたいカレンダーもある。#Fediverse 以外の #分散SNS とか #IPFS とか、#Bluesky とか #ATProtocol 関係も含めたカレンダーがあったら読んでみたい。
自分が参加するかどうかはぎりぎりに考えるかな。
#adventar

Dear #people, thank you for being here. I apologize for the #reduction in the #quality of #traffic on #technotramp.com experienced by #everyone who doesn't use #IPFS directly. It seems that #c4rex is doing #maintenance on the #gateway and I hope to have it up and running soon. You can #listen to the #music now, for #example, here:

👇

https://ipfs.io/ipfs/bafybeiewkxwysf4jlnhbxs7pd4junvkrrais76qm3qgkpn3en4b2lcqxwm/index.htm

-- or --

https://bafybeiewkxwysf4jlnhbxs7pd4junvkrrais76qm3qgkpn3en4b2lcqxwm.ipfs.dweb.link/index.htm

I don't want to #change the #domain #forwarding #record because of #antivirus #companies.

🖐️😶

Had anyone in the #Activitypub universe tried to make an #IPFS image server? I'd like to run my own instances for mastodon and pixelfed, but I don't want to host all those avatars and image feeds on my disk.

I'm fine if content get GCed over time.

Ok, I will answer it. No #IPFS server (that I know of) has any type of ACL in place. If you put a IPFS server online, any file you request through it will end up on its cache. If you put a gateway online, people can put all types of crap there and good luck to you explaining why you have illegal data on your server.

There is also no way to say "Here is a list of other IPFS nodes that are managed by other people that can be trusted" You can make a cluster, but you need to own it all.

@Floppy @vandam

So I looked into this. Allowing users to upload with #IPFS, a decentralized protocol replacement for #HTTP. Currently, I am benchmarking it by replacing my #Redis servers with it, just because I can for a few weeks.

#ActivityPub can be extended to allow for some extra allocated fields, and a fork of #Mastodon can be made.

Users will be able to upload their designs, and hosting would be decentealized and automatically spread around all users.

It is possible. I will look into a prototype, allowing users to use a bot or something like @3dprinting to share their prints before going for a fork of #Mastodon. Also need to investigate existing Activity Pub solutions and would possibly use something like #Go for the backend.

I'm still deciding on the front end.

@3dprinting #3dprinting

Just loaded my first #p2p site published to the new version of https://distributed.press with proper #ipfs #hypercore and #dnslink support!

The DNSLink stuff is a bit iffy for hypercore, but I'll be fixing that up tomorrow.

Now stuff can be published via Distributed Press, and viewed via @agregore

What's cool is that in addition to keeping your content online, you can easily configure it to set up DNS keys for you by delegating with an NS DNS entry for the `_dnslink` subdomain on your domain.

The #IPFSThing 5 day gathering of #IPFS and related #DWeb ecosystems now has tickets on sale for only $99, but early bird ends this Fri, Feb 24th!

Go buy your tickets! https://lu.ma/ipfsthing2023

Brussels, Apr 15th - 19th, more details on the website https://2023.ipfs-thing.io

Updated #IPFS guide: https://codeberg.org/silverpill/mitra/src/branch/main/docs/ipfs.md

The performance of go-ipfs (now known as "kubo") remains unsatisfactory on memory-constrained devices. Recently, developers added "Resource Manager" subsystem that is supposed to provide fine-grained controls over memory consumption, but it doesn't work for me. When I set MaxMemory to 150MB the memory usage quickly grows beyond this limit, until it hits the hard limit imposed by systemd (250MB).

Overall 0.18.1 works better than 0.12.0 but the difference is not significant.

Bug in #ipfs companion app. The below image will render

1. If you dont have ipfs companion app
2. If you are using brave + ipfs companion

If you are using any other browser, with ipfs companion, then ipfs companion, will convert the below image into http://xxxxx.ipfs.localhost:8080 then because the content is http, and self hosted, it wont load. If you are an ipfs nerd, let me know if you see the image!