@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

@mojo Tell me you don’t know what IPFS without telling me you don’t know what IPFS is, lol. What the fuck does IPFS have to do with crypto?

@Kalcifer

@Kalcifer

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.

@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?

What do you mean “quickly?”

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.

400C is like 650K. Not even close to absolute zero

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.

Same. I don’t see anything but one star reviews.

2.2M downloads and only 3.3 stars. You gotta be really shitty to have that low of a rating at that volume.

Dang I guess you can now. It wasn’t working when I first tried it. Awesome

I like it, but the fact that you can’t pinch to zoom an image almost kills it for me.

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.

A&W zero sugar root beer. I guess things could be worse

That’s changing the AP protocol, which is a huge undertaking, as it affects everyone in the Fediverse at that point, requiring new code to whatever platform that they are using. I think that’s the hardest route to go down.

Its does let people see that their comment has been seen as is unpopular, compared with just unnoticed. I’m okay with that style of downvote being private.

I think that’s the fundamental problem though. Just because a comment is unpopular doesn’t mean it’s not valuable or even correct. It’s often the unpopular opinions that are the most important. No always, obviously, but social change starts from unpopular opinions. It’s a double-edged sword.

I used to be against removing the downvote button, but honestly, it’s used a weapon more than anything else. It’s also used as “I disagree with this person” instead of an indicator of the value or veracity of a given post, which is not the intent. As such, I’ve now come around to the position that removing downvotes is the way to go.

Upvoting if you like a post, or do nothing if you don’t is the correct answer I think.