linux-nerds.org

Hmm... considering that Piefed cross-posts are entirely separate posts, then if the original is edited, then the modification is not carried over to the cross-posted post, correct? I'm thinking that for NodeBB we could continue to have cross-posts reference the canonical topic. They'd simply be part of a separate audience as well. Whether this is local-only or not, I am not sure yet. Perhaps for federation purposes we'd still report the original category (if there is one) under audience

@raphael@mastodon.communick.com hmm interesting, can you share the code that's making the call? Usually if it's working with curl it'll work with Node, so this suggests there's something different with the way the call is made with node. For what it's worth, internally, NodeBB uses the built-in fetch method from Node.js.

@mario@hub.somaton.com since Hubzilla posts (incl. yours) are making it in fine I'm assuming this is only for the "forum" feature?

@mario@hub.somaton.com thanks, I tested that payload and it successfully edited the post, so at least from the payload point of view there is no issue. Perhaps there is a problem with the http signature on update? Is that handled differently than a create?

@mariusor@metalhead.club I realized after I replied that I think @reiver@mastodon.social was talking about C2S? Definitely on S2S that's a no-go. There aren't enough guarantees.

Falls mal jemand von FreeOTP+ zum Bitwarden Authenticator wechseln möchte, ich habe da mal was gebaut https://forgejo.linux-nerds.org/frank/freeotpplus-export-to-bitwarden-authenticator

@MikDD Ich kann das Verhalten von Die bei mir nicht erkennen. Habe ein NAS, welches ich mit einem SystemD Dienst einfach einbinde. [Unit] Description=Mount NFS Share from 192.168.3.19:/NAS After=network-online.target Wants=network-online.target [Mount] What=192.168.3.19:/NAS Where=/mnt/NAS Type=nfs Options=defaults,timeo=900 [Install] WantedBy=multi-user.target Dann habe ich das in meinem Dateibrowser drin, suche meinen Videoordner und starte das Video. Einen kleinen Moment später startet das Video. Die Verzögerung wird die Zeitspanne sein, die benötigt wird einen Cache zu füllen. Wäre ja auch blöd, wenn man erst den ganzen Film runter laden muss. Hier, in meinem Forum, sollte man genug Informationen dazu finden. Wenn es irgendwo hakt oder klappt, stelle bitte eine Frage. Achso, Willkommen im Forum

@CWSmith hashtags in NodeBB are only relevant at the topic level — that's just how it was designed years ago. You'll note that on microblogs, tags can be added on any post. While we show them, we don't consume or index them unless they are the original post. When you use tags in NodeBB, they are federated outward with the original post. Hope that helps!

@philipp@social.anoxinon.de I kind of think this is really missing the forest for the trees if your rational is CO2 emissions... I mean, a far greater generator of CO2 emissions would be every single Mastodon instance caching every piece of media it sees...

@fionafokus@mystical.garden that was an excellent writeup. I am disappointed but not surprised by the improper response from the sole maintainer of Pixelfed. That kind of understanding of how to handle complex and severe security vulnerabilities comes with time and experience.

Thanks for the confirmation @jsonculverhouse@flipboard.social, any chance we could have the post list the magazine as a recipient, so that a backreference is established? See: https://community.nodebb.org/post/104013 @mike@flipboard.social mentioned you, but a typo got in the way

a response, should wrap up immediately.

@eeeee what were you trying to do there?

Thanks @johnonolan@mastodon.xyz! I haven't really had time to take a closer look yet, since I've been so focused on cranking out the remote categories stuff, but I'm excited to give this a spin once I update this. What kind of special handling are you looking for for this, that blog posts and forum topics send out as:Article?

@julian yes we've had this for 6+ months

neat, that worked OK.

@baris Yeah noticed it now. Actually, I also setup the nginx configuration following nodebb docs, specially the one for utilising multiple(2) cores for nodebb, but somehow missed the line related to protocol. Thanks a lot again.