@iso@lemy.lol what's a "lemmy-like" PM I think this explains why I can't log into the site.

Topic hash is topic: plus the topic id. e.g. the database entry for this one is: topic:13608.

@rimu@piefed.social I noticed today that PieFed supports the concept of soft deletes: [image: 1746454570656-7b0318bb-2838-4675-b53e-28e6904ebf45-image.png] Perhaps this FEP would be of interest to you.

Although for tests we are still using 18 and 20 https://github.com/NodeBB/NodeBB/blob/develop/.github/workflows/test.yaml#L30

@dansup@mastodon.social no, NodeBB v4 always reports activitypub in protocols, even if disabled. I can update that so it's dependent on the global switch, but it's still possible to have AP enabled but not have any categories federating. I'm just wondering whether FediDB found the forums because content got federated, or whether there was some proactive nodeinfo crawling, that's all. cc @jaz@mastodon.iftas.org

@renchap@oisaur.com how does RFC9421 differ from Mastodon's existing support for HTTP Signatures? Does this mean you're moving away from cavage-12? That's important to know, and if you're looking for an implementor to handle double-knocking, that is something I can put together for you.. we don't do it at current.

@KirillEvo seems that also deleting package-lock.json will also work.

I think the FEP process is overly complicated for what it is, but it's definitely helpful if you have multiple implementors on board. The easiest (but least accessible) solution is to document something on your own site, but that lacks the social proof that a finalized FEP has. Just some food for thought I'm looking to create an FEP for cross posting and would love to get the entire threadiverse dev community involved.

@trwnh@mastodon.social but why must a separate account be made? Account fragmentation is yet another unsolved problem because the new user on account B is functionally useless: no followers, etc. and the content isn't automatically available to the followers of the user on instance A.

@lassesuom my guess is they're sess:* keys. They can balloon up if you have lots of guests *cough* AI scrapers. There used to be logic so that guests didn't receive a session key (since they didn't really need one for regular browsing) but it could be that that detection no longer works.

@V.-Kushnir Some additional tips here: https://docs.nodebb.org/configuring/scaling/

@esoteric_programmer@social.stealthy.club that's likely because GtS handles summary as a content warning for everything. The whole summary and content warning business is in flux right now, so hopefully a standard will be set soon.

Lemmy ist nur auf Gruppen/Communitys ausgerichtet (dadurch zwar beschränkt, aber die Inhalte sind sehr gut strukturiert). Bei kbin (bzw. dessen Nachfolge mbin) ist es anders: Da hat man einen Gruppenbereich (heißt dort "Magazines") und einen Microblog-Bereich, kann also auch Einzelaccounts folgen. Ich hatte das mal ausgetestet, als kbin gerade gestartet war. Interessanter Ansatz, aber für mich persönlich zu unübersichtlich: kbin (mbin): Link-Sharing und Microblogging unter einem Dach

@kriptokyng stop using :4567 in the url.