linux-nerds.org

index@activitypub.ghost.org fam just blocked an entire domain because of the fediverse chick. johnonolan@mastodon.xyz clearly means business here.

antolius@mastodon.social the thing here is that "x server federates" isn't a binary thing. We support quite fine grained privileges, and that extends to ActivityPub as well. So representing that state as a Boolean isn't quite right either.

jalefkowit@vmst.io no, I don't think I will do that.

feditips@social.growyourown.services correct, it mutes just that branch, because Mastodon doesn't understand that the entire reply tree is something that can exist. When you mute a topic on NodeBB you mute it for good

feditips@social.growyourown.services ahaldorsen@tutoteket.no feel free to reach out if you have trouble setting up or administering NodeBB. We're on the fediverse, and happy to be here!

Heute mal drüber gestolpert, das es auch so was geben kann. root@pve2:~# zpool status pool: pool_NAS state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 00:20:50 with 0 errors on Sun Apr 13 00:44:51 2025 config: NAME STATE READ WRITE CKSUM pool_NAS ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ata-WDC_WDS100T1R0A-68A4W0_230520800733 ONLINE 0 0 0 ata-WDC_WDS100T1R0A-68A4W0_230520801376 ONLINE 0 0 0 errors: No known data errors Was machen? Als erstes mal ein Backup angestoßen. Danach root@pve2:~# zpool get all pool_NAS | grep feature pool_NAS feature@async_destroy enabled local pool_NAS feature@empty_bpobj active local pool_NAS feature@lz4_compress active local pool_NAS feature@multi_vdev_crash_dump enabled local pool_NAS feature@spacemap_histogram active local pool_NAS feature@enabled_txg active local pool_NAS feature@hole_birth active local pool_NAS feature@extensible_dataset active local pool_NAS feature@embedded_data active local pool_NAS feature@bookmarks enabled local pool_NAS feature@filesystem_limits enabled local pool_NAS feature@large_blocks enabled local pool_NAS feature@large_dnode enabled local pool_NAS feature@sha512 enabled local pool_NAS feature@skein enabled local pool_NAS feature@edonr enabled local pool_NAS feature@userobj_accounting active local pool_NAS feature@encryption enabled local pool_NAS feature@project_quota active local pool_NAS feature@device_removal enabled local pool_NAS feature@obsolete_counts enabled local pool_NAS feature@zpool_checkpoint enabled local pool_NAS feature@spacemap_v2 active local pool_NAS feature@allocation_classes enabled local pool_NAS feature@resilver_defer enabled local pool_NAS feature@bookmark_v2 enabled local pool_NAS feature@redaction_bookmarks enabled local pool_NAS feature@redacted_datasets enabled local pool_NAS feature@bookmark_written enabled local pool_NAS feature@log_spacemap active local pool_NAS feature@livelist enabled local pool_NAS feature@device_rebuild enabled local pool_NAS feature@zstd_compress enabled local pool_NAS feature@draid enabled local pool_NAS feature@zilsaxattr disabled local pool_NAS feature@head_errlog disabled local pool_NAS feature@blake3 disabled local pool_NAS feature@block_cloning disabled local pool_NAS feature@vdev_zaps_v2 disabled local Das kommt von neuen Funktionen, die zu ZFS hinzugefügt wurden und bei Erstellung des Pools nicht vorhanden waren. Dann upgraden wir mal root@pve2:~# zpool upgrade pool_NAS This system supports ZFS pool feature flags. Enabled the following features on 'pool_NAS': zilsaxattr head_errlog blake3 block_cloning vdev_zaps_v2 Kontrolle root@pve2:~# zpool status pool: pool_NAS state: ONLINE scan: scrub repaired 0B in 00:20:50 with 0 errors on Sun Apr 13 00:44:51 2025 config: NAME STATE READ WRITE CKSUM pool_NAS ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ata-WDC_WDS100T1R0A-68A4W0_230520800733 ONLINE 0 0 0 ata-WDC_WDS100T1R0A-68A4W0_230520801376 ONLINE 0 0 0 errors: No known data errors Features kontrollieren root@pve2:~# zpool get all pool_NAS | grep feature pool_NAS feature@async_destroy enabled local pool_NAS feature@empty_bpobj active local pool_NAS feature@lz4_compress active local pool_NAS feature@multi_vdev_crash_dump enabled local pool_NAS feature@spacemap_histogram active local pool_NAS feature@enabled_txg active local pool_NAS feature@hole_birth active local pool_NAS feature@extensible_dataset active local pool_NAS feature@embedded_data active local pool_NAS feature@bookmarks enabled local pool_NAS feature@filesystem_limits enabled local pool_NAS feature@large_blocks enabled local pool_NAS feature@large_dnode enabled local pool_NAS feature@sha512 enabled local pool_NAS feature@skein enabled local pool_NAS feature@edonr enabled local pool_NAS feature@userobj_accounting active local pool_NAS feature@encryption enabled local pool_NAS feature@project_quota active local pool_NAS feature@device_removal enabled local pool_NAS feature@obsolete_counts enabled local pool_NAS feature@zpool_checkpoint enabled local pool_NAS feature@spacemap_v2 active local pool_NAS feature@allocation_classes enabled local pool_NAS feature@resilver_defer enabled local pool_NAS feature@bookmark_v2 enabled local pool_NAS feature@redaction_bookmarks enabled local pool_NAS feature@redacted_datasets enabled local pool_NAS feature@bookmark_written enabled local pool_NAS feature@log_spacemap active local pool_NAS feature@livelist enabled local pool_NAS feature@device_rebuild enabled local pool_NAS feature@zstd_compress enabled local pool_NAS feature@draid enabled local pool_NAS feature@zilsaxattr enabled local pool_NAS feature@head_errlog active local pool_NAS feature@blake3 enabled local pool_NAS feature@block_cloning enabled local pool_NAS feature@vdev_zaps_v2 enabled local So, alle neuen Features aktiviert. Jetzt kann der Pool weiterhin seine Arbeit machen.

groupnebula563@mastodon.social nodeinfo is present in all v4 instances even if federation is not enabled. Per my understanding, it's not ActivityPub specific, so it always returns the data when requested.

jwildeboer@social.wildeboer.net I propose we nickname the new one the first 'murican pope.

britt@mstdn.games to be fair, the reason this happens is because Marketplace lets you press the button to send the quick response, but doesn't open the chat, so people just keep browsing. It's a dumb UX and it only barely works at that.

fediforum@mastodon.social thanks, I was wondering

> The ALICE analysis shows that, during Run 2 of the LHC (2015–2018), about 86 billion gold nuclei were created during the four major experiments. In terms of mass, this corresponds to just 29 picograms (2.9 × 10-11 g). Since the luminosity in the LHC is continually increasing thanks to regular upgrades to the machines, Run 3 has produced almost double the amount of gold that Run 2 did, but the total still amounts to trillions of times less than would be required to make a piece of jewelry. We're all gonna be RICH cadey@pony.social

@silverpill@mitra.social is that part of the nodeinfo spec?

@projectmoon@forum.agnos.is said in Updates to the world page: > > > Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality? Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it. Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.

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

Im running Node 23 on my production install

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

@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.