julian

@julian@activitypub.space

• ⁨Comment⁩ on ⁨Recommendations for federated CMS alternatives to Wordpress?⁩ ⁨⁨6⁩ ⁨days⁩ ago⁩:

  @hendrik@palaver.p3x.de fwiw NodeBB ended up being such a joy to author things in that we switched away from WordPress to NodeBB as our blog. We just blog on our forum.

  Now, conflicts of interest are important... I wrote NodeBB, so I am obviously pretty biased :laughing: !

• ⁨Comment⁩ on ⁨Ideas for a better Lemmy experience⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I'll give some insight from NodeBB.

  Adding in delays (x days until first post, y hours until upvote, etc.) do nothing to curb spam.

  If your spam is manual, they will discover the waiting period, update their rulebook, and go to town when the waiting period is over.

  If the spam is automated, it will work until the spammer admin discovers the waiting period, updates the script, and has the bots resume going to town when the waiting period is over.

  At the same time it severly hampers usability at its most crucial (the first post).

  The only thing that works to curb spam is a post queue with manual review... or locking the ability to post links behind reputation.

• ⁨Comment⁩ on ⁨Would a fediverse alternative of Discord be possible?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Except it's completely gated behind Discord corporate servers, unsearchable outside of Discord, and all ownership lies with... you guessed it, Discord.

  But oooh aah Nitro....

• ⁨Comment⁩ on ⁨Would a fediverse alternative of Discord be possible?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Discord has both private and public channels. I won't bother considering their threaded discussion offerings, because they're absolutely horrendous.

  ActivityPub is primarily public. You have scoped visibility that enables things like private messaging, but there is no implementation that allows for federated private group discussions.

  There are proposals and a few implementations, but they all rely on everybody else to implement the same proposal, otherwise messages leak out, and that defeats the entire assumption of the private group.

  It's not an unsolvable problem, merely one that hasn't been successfully solved yet.

  As for whether AP is a good fit... It'll work. At the end of the day you're exchanging messages. Whether they're long form or chat messages makes little difference.

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.

  NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  What is this proprietary layer you speak of?

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  This is something I believe the ActivityPub API can tackle...

• ⁨Comment⁩ on ⁨New Social Web Working Group at W3C⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  To my knowledge, one must be an "invited expert" in order to join these discussions.

  However, the working group is only one aspect. The community group has been in existence for a number of years. I am part of that group (although I admit I don't go to as many meetings as I ought to), and try to represent the threadiverse as best as I can.

• ⁨Comment⁩ on ⁨If a Lemmy user has the same name as a community, how can I tag the community on Mastodon?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Nope, it's just a.single route, no filters or qualifiers I am aware of.

  One could go through the returned accounts and see which are users and which are groups, although that's expensive and time consuming to do.

• ⁨Comment⁩ on ⁨If a Lemmy user has the same name as a community, how can I tag the community on Mastodon?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  Agreed... I didn't respond right away since I wasn't sure if I was right, but there are two constraints at play here:

  • Lemmy wants to allow communities to be named the same as a user
  • This is not allowed in webfinger (insomuch that multiple IDs reports should refer to the same entity)

  You can fault Mastodon for not handling it, but I think the onus is on Lemmy to adjust their behaviour.

  For reference, the same constraint happened with NodeBB. When we started, categories didn't have handles and were not unique with users (so, a category could be named the same as a user). I needed to make the handle unique between both categories and users, for this exact reason.

• ⁨Comment⁩ on ⁨Random idea: a federated alternative to Amazon Prime built from independent shops?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Sounds like Rakuten actually...

• ⁨Comment⁩ on ⁨Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.

  Thanks, it's this.

  Edit: oh interesting, I looked into it. We serve the absolute URL in HTML but not in markdown. I had no idea threadiverse apps read the markdown. Neat!

• ⁨Comment⁩ on ⁨Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  @rekall_incorporated@piefed.social said in Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]:

  This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

  I don't think this is true at all.

  The average user doesn't know what Lemmy is, let alone the political views of their core development team.

  But don't worry, it's like that joke about vegans:

  How do you know the Lemmy devs are politically dubious? Don't worry, someone on the threadiverse will tell you.

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Hmm, how do you reconcile the fact that not all FEPs are applicable to all application types?

  For example soft deletion is preferable but not required...

• ⁨Comment⁩ on ⁨⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Indeed, this is where the majority of improvements to the Fediverse are shared for archival.

  The very way Lemmy Piefed Mbin and NodeBB can communicate and synchronize communities is detailed in those FEPs. Check out FEP 1b12.

• ⁨Comment⁩ on ⁨Is Pixelfed sawing off the branch that the Fediverse is sitting on?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Well that is weird, why did the link get confuzzled...

• ⁨Comment⁩ on ⁨Is Pixelfed sawing off the branch that the Fediverse is sitting on?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Response from Dan

  https://mastodon.social/@dansup/115678527443322224

• ⁨Comment⁩ on ⁨Is Pixelfed sawing off the branch that the Fediverse is sitting on?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  You jest, but I'm pretty sure someone out there made a cli interface for AP.

• ⁨Comment⁩ on ⁨Looking for a PeerTube instance that actually accepts new users⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  @fijxu@programming.dev nadeko... Why does that sound familiar? I think you used to host a Canadian Invidious instance I used to use! 😂

• ⁨Comment⁩ on ⁨Looking for a PeerTube instance that actually accepts new users⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  My go-to is spectra.video, run by @deadsuperhero@lemmy.ml

• ⁨Comment⁩ on ⁨Community mention spam from Microblogs⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  @silverpill@mitra.social isn't wrong though, in many cases the posts do mean to be posted in that community.

  But it's an expressive thing. I'm able to mention a community like @startrek@startrek.website and it won't be posted there, because I'm only mentioning that community.

  And yes, Mastodon needs mention spam to function because otherwise people you reply to won't know they received a reply. It's ... an approach.

• Community mention spam from Microblogs
  Submitted ⁨⁨2⁩ ⁨months⁩ ago⁩ to ⁨fediverse@lemmy.world⁩ | ⁨7⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Looks like now Mbin, at least on mobile, mixes threads and microblog posts⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I've been looking into how to accomplish this too... because it is a UI/UX problem and I am very bad at designing user interfaces.

  Mixing them like so works, although it's hard because then it minimizes the size of topics (since it is just the title.) It means microblog content get a bit of a UI boost due to on screen size.

  Limiting the max height of microblog posts and showing a snippet of the threaded content OP is another way, but that makes the page more feed-like and less of a "topic listing", which isn't always the way to go either.

  For reference, NodeBB also mixes threads and microblog posts. We do this by generating a title from microblog posts. It's not the best solution either.

• ⁨Comment⁩ on ⁨The Fediverse and WordPress Should Be Better Friends, with Evan Prodromou⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  @auster@thebrainbin.org may I ask you to expand in what you mean by "same underlying engine"?

  If you're talking about ActivityPub then it's a open standard which isn't beholden to any one organization. It's like saying HTML is bad because websites are all forced to use it as the underlying engine.

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  There is, but I am not sold on giving up entirely on the idea simply because disparate communities might not want to talk to another.

  I agree that treading lightly is paramount, but the benefits of cross-community interaction could very much be worth it!

  One thing is for sure: making this an opt-out is not the way forward.

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  What if upon cross-posting the default is separation, but a request is sent to the original community to request a comment tree merge?

  Then you don't have to share comment space with the tankies unless you wish it

  cc @blaze@piefed.zip

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  That's one of the issues that need to be worked through. It's a totally legitimate concern.

  In cases where communities with polarising viewpoints discuss the same topic, it would lead to inter-community disputes and exacerbate some instance relationships.

  One solution would be to have the original community be responsible for moderation, and moderation actions from cross-posted communities only affect their "view", so to speak.

  I don't know what the answer is quite yet.

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  From a discoverability standpoint it would be beneficial to see other communities' conversations on the same post.

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Hmm... that's nice, but the comments are still separated.

  It would be better if the separate reply chains were integrated but I know there are potential issues that need to be thought through.

• ⁨Comment⁩ on ⁨The problem of cross-community posting⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  @blaze@piefed.zip said in The problem of cross-community posting:

  That's a complete overhaul compared to what Lemmy/PieFed/Mbin are doing now.

  That might be the case, but it really depends on how the backend is structured. Are the posts and communities so strictly structured that a post cannot be a part of multiple communities? (@rimu@piefed.social just pinging you about this)

  In NodeBB categories and topics are all distinct elements, and the fact that a topic belongs in a category is contrived. A topic could be part of a user (pinned topics anyone?), a group (group only conversations?), or in this case... multiple categories.