What do you think of the name #GlutPlug to describe helping your instance serve content over I2P?

Is it too suggestive?

Would you prefer #I2PFS instead?

@zleap
We tend to ignore the turdsite stuff.

Since Monday, a new interest of ours is in using the peer-to-peer network (#I2P) to #democratise fediverse #contentDelivery. So when a person positively interacts with a toot the content is retained to be served by that person (if they have not flagged content and their battery is above 50%).

In this context moderation becomes self-fulfilling, and the use of I2P protects the users from survellance and targetting.

#cdns #fediMeta #glutPlug #i2pfs

These are essentially #baitAndSwitch attacks.

A few days ago we brainstormed how #I2P might be able to democratise #contentDelivery in #Fediverse, in ways that protect users.

See our #GlutPlug post.

We hope that #Mastodon, #Akkoma, #FireFish and #Epicyon are able to seriously consider how they might do this. App developers for #Tusky and #Fedilab also.

#i2pfs

@kravietz
Yes, the point with the system we outlined above is you'd hook a client into I2P, or have I2P integrated into a client, and then you:

A) become part of the storm you mentioned. The more in the storm/network the better, obviously. Same for all networks.
B) host the file automatically by just interacting with the toot in some way. A manual override can be done, ie. "Do not share media via {GlutPlug,#I2PFS} from this interaction". Phones might only serve if battery over 50%.

@icedquinn @Hyolobrika@mstdn.io @Moon

And then there was #I2PFS.

@sadiedoreen @i2p