@[email protected] said in The unreasonable effectiveness of 1b12:
i also would prefer something more browsable
Absolutely
That's in a nutshell what I'd like to achieve in 2025. The building blocks are nearly all there.
Those who prefer GNU/Linux over any other OS.
@[email protected] said in The unreasonable effectiveness of 1b12:
i also would prefer something more browsable
Absolutely
That's in a nutshell what I'd like to achieve in 2025. The building blocks are nearly all there.
A lot of the effort I'm championing with the ForumWG deals with combating the inability for Mastodon (and other non-1b12 implementors) to federate content thoroughly. A lot of that is due to design decisions that were thoughtfully made, so this isn't a critique, per se.
It really does highlight that 1b12 is actually quite good at what it does (federating content out), and that 7888, et al., would be a great complement for post-hoc backfill.
I am once again astounded by how unreasonably effective FEP 1b12 is at federating content completely.
On NodeBB I have a list of "popular" topics, which is mainly populated based on number of posts within a given time period. For most content from Mastodon-based servers, this supplies a decent signal of a given topic's popularity. The more people you follow, the more effective it is, but overall it's pretty shit at getting you the whole conversation.
Enter 1b12, Lemmy's preferred federation method. Follow a community actor and you start receiving everything that happens in that community. Replies, likes, the whole lot.
It also absolutely dominates my popular feed. It's all Lemmy stuff now because the Mastodon stuff literally can't compare.
Albeit the SNR is a tad lower, so give and take...
@[email protected] @[email protected] @[email protected] I think that makes sense considering that outboxes already do contain activities, so it's not a stretch from prior art.
I'd also like to know the thinking behind excluding root-level post from the context collection. I think it belongs within, but other software may consider root level objects to be like "topics", and so would be on a separate level from replies. The easiest example I can think of right now is Lemmy, which is how it handles posts.
@bboctt oh lord!!
The ever-lasting battle between compatibility and adoption of new features.
At the end of the day, supporting older browsers gives us enough developer friction as to become a no-go. That's not to mean that it isn't important, but unfortunately that the market share isn't there for us to spend a significant amount of time on it.
But let's say... if a big bank came to us and said "This forum needs to work on IE11!!", and was going to spend the dollars to get the software there, then that is a different story.
On the upside, though, there are a couple small things we can try to address. The site's client-side js shouldn't immediately crash... stuff should work. It may be worth investing some time into getting the baseline functionality working, if it isn't already.
@eeeee correct, the wording is a bit different. So while posts and topics you can "delete" and then "purge", with categories, you're "disabling", and then "purging".
Whatever, just the same. Categories don't need to be disabled before being purged.
What shows up in the dev console when you click "purge category"? It should open a modal.
@eeee I just checked the template, the button should never be greyed out
@eeeee This menu option?
Odd that it's greyed out, probably means there's a precondition that wasn't satisfied...
@eeeee said in Efficient way to increase World posts on a topic?:
(2) When I follow someone from a Mastodon site, I seem to be following a clone of their account. I.e. account created 8 Nov 2022, 00:00, 1 post.
Not their mastodon profile with many posts and followers
When you query a remote user, they are given a local representation in NodeBB. The creation date is different because it cannot always be trusted. If a remote user reports their creation date as 1 Jan 2588, I don't think that would be correct... but it is allowed in ActivityPub to do that — so I just use the date they were first queried.