> @anchorite said: > > On aggregator-type sites like Reddit that prioritize new content over old but still relevant content, you have to make new posts about the same topic once the old post drops off the first page because nobody's going to go looking for it.
And you get yelled at for "reposting" just because you want to ask a question or continue a discussion that died because it's been six hours since the last time it was posted.
This is pretty neat. It's definitely more "scrollable" than the current implementation on prod. I'm finding several elements of it very counter-intuitive, though.
Topic titles come below the by line, and below any attached images, which keeps making me A) think that those images are from the previous post, and B) actually have difficulty identifying the titles.
Text is not selectable, because the entire card is hotlinked. I understand why this might be, with microblog posts not having titles to click on, but it has repeatedly tripped me up while exploring /world.
The Category labels don't really stand out to me anymore; thre's just so much more text on screen, they kind of get lost in the visuial noise.
Users who don't grok that the fediverse has a wide range of platforms and servers might be left with real questions about why some posts have different formatting and elements than others. Misskey labels remote posts with both the remote server name and their platform. This didn't seem important when /world was showing everythign as forum topics, but it stands out to me now in this new feed format.
Lemmy image and link posts now seem even weirder with "This post did not contain any content" just displayed directly in the feed over and over again (also, this is off topic, but Lemmy link posts have never worked on NodeBB)
Posts without responses (or at least Lemmy posts without responses) still show the OP in the reply preview, which can lead to things like this:
@ianhclark510@lemmy.blahaj.zone There are so many communities out there using Discord for something other than game streaming or whatever. Discord's been a right shit replacement for forums, yet people used it.
Maybe we can stop looking for the one-stop swiss-army-knife products. They're always trash, and their business model is always to treat you like garbage.
@julian said in Cross-posting is coming to NodeBB!: > different communities with (sometimes very) different values would suddenly co-exist in the same space, leading to some very negative interactions.
This is something I'm very concerned about, and it's one of the primary reasons I generally oppose efforts on Lemmy and Piefed to enable virtual community mergers and whatnot. I'm getting old and all that jazz, but from my perspective, the Internet was a more vibrant, more productive, and more fun space when communities were small enough to see other members as people, and where usernames and avatars were immediately recognizeable, rather than the giant morass of faceless voices shouting about in dark, giant, overfilled rooms. Just from a cultural homogenization point of view, it's been a negative.
But shared comments on individual posts like this poses an even bigger risk, since, as you point out, a single share to an unscrupulous server means everything is on fire.
Post syndication is one thing, but comment syndication seems like something that needs a lot of transparency, release valves, and a high degree of opt-in and opt-out control.
Like, there are definitely Lemmy and PieFed communities I'd happily sync comments with, but there are a bazillion others I would not. That means, as a moderator, I'd need black-lists and white-lists for remote communities at both the category and topic level, while as a poster I'd want some level of control over where my topics or comments can go, and maybe even the ability to flag topics or comments as local-only (which is something that maybe should be considered just from a basic federation standpoint; I've seen this in action on Misskey-based microblogging sites, and it has value).
But still, despite those hefty reservations, I cannot deny that I'm really very excited by this.
Huh. My Lemmy mobile client has the handle and host inverted. It doesn't look like this in the default web UI, though.
Also, my post from Lemmy hasn't landed here yet.
@nutomic@lemmy.ml Mostly what I've observed is significant instances of timing out when trying to find communities on new instances from non-Lemmy-based websites, something that hasn't been notable from Lemmy-to-Lemmy first encounters. From the outside, it points to y'all doing some kind of compensation for possible AP issues.
I know I said "Lemmy is rough around the edges", but I really meant "ActivityPub is rough around the edges". Lemmy's just the hegemon in the AP categorized content space.
@eeeee Yeah, Lemmy is rougher at the edges than it looks sometimes. Part of the issue, I think, is that older versions of the software don't parallelize federation, so the queues can get way backed up. I've also just had follow requests from nodeBB dropped at an unusually high rate, which makes me think that Lemmy is doing things internally to compensate for some of the sharp edges of federation.
This is incredible, Julian. I'm legitimately kind of stunned by this, how well it's working already, and how quickly this got refactored.