@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.
Sorry to tag you, but I'm not really sure what's going on. Kbin federation from my node to kbin.social doesn't seem to be working, or if it does, it's very intermittent.
kbin.social to my node works most of the time, but also loses information but much less frequently.
Is there any reason why kbin.social isn't accepting incoming federation from my note (showeq.com) or why it's so severely delayed when it does?
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.
That's correct and that's the problem. If a given community server goes down, that community basically just becomes an archive. It really needs to be able to continue without the host instance, similar to how a mesh works. Each remaining server routes around the dead node.
There is also the problem of search engine indexing... If a given server goes down, that information is lost to the search engine, even though it's still on other nodes.
Which also leads to duplicate content problem for search engines, as ECU m each node of a given community contains the same information for a given post, making it crappy to index and search.
Indeed, and when you kiss someone you are making one big hole connected by two assholes.
The RCS issue hits the nail on the head I think. It's really the biggest stumbling block for everyone at this point.
Crashing for me. Switched to Connect. Works well... except you can't pinch zoom images, which is a huge problem...
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.
I'm viewing this from KBin and I don't see strikethrough.
Like the title says, if you want to upvote something on KBin, you should use the Boost link, not the upvote button (Why? Don't know...)
The upvote button doesn't seem to do much, but Boost accomplishes what Reddit's upvote did. So if you're looking to encourage a post, use the Boost link.
