HamSwagwich Now • 66%
@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.
[@ernest](https://kbin.social/u/ernest) 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?
HamSwagwich Now • 77%
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.
HamSwagwich Now • 75%
What do you mean "quickly?"
HamSwagwich Now • 100%
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.
HamSwagwich Now • 100%
Indeed, and when you kiss someone you are making one big hole connected by two assholes.
HamSwagwich Now • 100%
The RCS issue hits the nail on the head I think. It's really the biggest stumbling block for everyone at this point.
HamSwagwich Now • 100%
Dang I guess you can now. It wasn't working when I first tried it. Awesome
HamSwagwich Now • 100%
I like it, but the fact that you can't pinch to zoom an image almost kills it for me.
HamSwagwich Now • 0%
Crashing for me. Switched to Connect. Works well... except you can't pinch zoom images, which is a huge problem...
HamSwagwich Now • 0%
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.
HamSwagwich Now • 100%
A&W zero sugar root beer. I guess things could be worse
HamSwagwich Now • 100%
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.
HamSwagwich Now • 100%
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.
HamSwagwich Now • 100%
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.
HamSwagwich Now • 100%
This explanation and suggestions from @poVoq was the absolute best I've seen and I agree with nearly all of it.
The stated rationale for up and down-votes in Lemmy is to crowd-source content curation as an alternative to what other social media platforms do with their algorithms. A secondary goal is to crowd-source a sort of light moderation of comments by partially sorting comments threads after votes. This is similar to how it works in Reddit and HN etc.
While both sounds good on paper, in my experience neither works on Lemmy. I think this is mainly because the number of votes and comments (aka the number of active participants) is just too low on 95% of the posts for it to result in a meaningful content curation signal. But to make it worse, there are some notorious heavy users that abuse the system, which is easy to do as a few down-votes are usually sufficient.
I think the Lemmy devs still hope that at some point there will be sufficient scale for their vote curation system to work, but I started to think that a design that only works at a certain scale is fundamentally flawed in a federated context.
For Kbin I think it is even less likely to work, as the decision to use boosts as upvotes will make people hesitant to up-vote. While I agree that boosts make certain sense to use for this, I also know that people un-follow accounts that do too much boosting as it results in it occupying their entire home-feed. For me a boost is a stronger signal than a star/favorite and thus should be used more seldomly.
However, I still think using boosts as upvotes is not necessarily a bad idea, but it IMHO requires to get away from the up/down vote idea of Lemmy where it is encouraged to vote as much as possible (and even that isn't at a sufficient scale for the idea to work in Lemmy).
My suggestion is to lean into the idea to use boosts as up-votes and very explicitly use the "double-arrow" boost icon where currently the up-vote button is and do away with the down-vote there all together. That will integrate better with the rest of the fediverse and not lead to people being confused that others unfollow them over boost spam. You can still count the number of boosts to do some basic "hot" sorting, but this will work better with small communities that do not have sufficient scale.
You can still add a "dislike" or so button where currently the "comments, favorites, more" buttons are, but that should be an optional thing and not federate, or only federate in the local bubble (a concept of Akkoma for forming closer relations of a small number of instances).
Edit: for comments I would forget about votes all together, as on Lemmy vote abuse is even more common in the comments. Boosting comments out of context is often a bit jarring in the fediverse anyways, so the option to boost them should be probably de-emphasized.
HamSwagwich Now • 100%
It was a divide by zero and you killed us all. Now we are in a different timeline.
https://kbin.social/m/MandelaEffect checking in.
HamSwagwich Now • 100%
@ernest I can't imagine how stressful it is for you. I've run a few larger projects (ShowEQ back in the day, being one of the bigger ones), but nothing that blew up so quickly like Kbin has and I don't envy your position. I really appreciate the work you've put into KBin and I want to see it succeed!
HamSwagwich Now • 100%
Right, so boost behaves like Reddit upvote at the moment. So the title of the post is accurate still.
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.
Like the title says, I'd like to know what's going on with KBin federation? Lemmy content is federating to pretty much all other Lemmy instances just fine, but anything on KBin is taking a *very* long time to show up on Lemmy, if it ever shows up at all. On Lemmy.world, I am subscribed to a bunch of kbin.social subs that are in pending state for 2 days now... the few that have gone from pending to joined have zero content show up on Lemmy. [/m/anime\_titties](https://kbin.social/m/anime_titties) for example has many articles on here, but show none at all on Lemmy.world. Can anyone explain the problem behind this and when there's an expected fix?
If I'm on a Lemmy instance, I can't find any Kbin.social magazines or users. Why is that? For example, if I search for myself on lemmy.world, such as [!hamswagwich@kbin.social](https://kbin.social/m/!hamswagwich@kbin.social), or [@hamswagwich](https://kbin.social/u/@hamswagwich), or hamswagwich@kbin.social it's not found. Same for Kbin.social magazines, for example, searching for [!TeslaMotors@kbin.social](https://kbin.social/m/!TeslaMotors@kbin.social) brings up nothing. Same with other lemmy instances. Why is that? [\#kbinMeta](https://kbin.social/tag/kbinMeta)