Oops thank you
The long term solution is something like IPFS object storage that’s read only for everyone but the author instance. One copy of the data but all instances can read it and it’s stored forever in a redundant medium with bitrot protection.
I’ve been running one. showeq.com
The basic service gets overloaded quickly and you’ll need to upgrade if you get any traction at all.
Also, since KBin federation is broken, it’s not great
Yes it does. My KBin node is not federating with KBin.social or only works intermittently.
@ernest it started working a couple hours ago. No idea why . Thought maybe you knocked something loose
@ernest I restarted my instance and it seems to be receiving federated content from kbin.social, but any content I post isn’t being received by kbin.social.
Thank you for the reply! I’m still not getting any federated content either direction with my node from KBin.social
I’m running a KBin node for the record, not Lemmy
Still working on it?
Ive decided not to block him so I can follow him around annoying him and downvoting everything he says
Perfect example of why voting should be public!
Blocking him is the right answer, it’s the right thing to do and solves the problem of him presenting posts you don’t want to see.
A&W zero sugar root beer. I guess things could be worse
I’m viewing this from KBin and I don’t see strikethrough.
@mojo Just keep telling people you don’t know what IPFS is without coming outright and saying it. Lol.
“IpFs GeTs PaId In FiLe CoIn”
IPFS is a protocol, you nitwit. That’s like saying “ActivityPub is gets paid in Filecoin” Makes no fucking sense. Build a Fediverse layer on IPFS, no crypto needed. FFS get educated before you start trying to talk to adults.
Jesus… just stop.
@Kalcifer