Notices by Evilham :antifa: (evilham@chaos.social)

@liw I've seen a bunch of "here is how you use GitHub registry instead", which only moves the problem forward.

@marcos @fanta quieres decir, la @cso_kikemur ? :-)
(Estan en la fedi!)

@stefano @oxyhyxo ugh, and here I wanted to go back to dovecot since it felt simpler. cyrus does work wonders and has many features (can be a tad overwhelming), so it's a good choice

@dansup oh, that's good to know! Am I to understand though that the previous docs should still work for v0.12.1?

Because if so, I probably did something wrong at some point and should take a look again after some hours away from it :-).

Do I read this right? #Pixelfed implemented LDAP with an #NLNet grant at version v0.11.3 (https://github.com/pixelfed/pixelfed/pull/3296) and now it's basically undocumented, deprecated and pretty much not supported?

https://github.com/pixelfed/docs/commit/1aa6b9f4e50753d4799ebcfa177c3a0a9c642cef#diff-d5bc08b1d5d061d7f99334b0d2f6231810aeb1f38f1ae734472c889420a54745

Not that it ever was a great setup, but it was supposed to work '-.-

Lovely #fediverse operators / #fediadmin, can someone point me to best practices when it comes to spinning up test instances that are designed to be deleted after some time?

It is unclear to me what happens in #ActivityPub when a server that was known disappears. I know this has happened in the past in rather traumatic ways (instance gone, backups gone, ...), so it must be somewhat well-supported.

Given that this is planned and designed though, I'd like to do things "properly" :-).

I got shutdown by stripe, because "crowdfunding-like endeavours are not allowed".

Checking their ToS, it seems like that is correct: https://stripe.com/en-de/legal/restricted-businesses

How do people using @Liberapay or #fosspay solve this? Just pretend a service is being offered?

@feld I thought this was something related to our boot-loader, but no, it seems like it's grub2 itself which cannot boot from XFS and Debian will happily let one install things like that :-).

So I guess that if one doesn't want a journaling FS, the answer is to make sure there is an ext2 partition for grub2 and then the XFS partition for the rest.

Question for the #FreeBSD #bhyve people: is booting Linux from XFS partitions not supported?

It's not the first time that seemingly the same installation fails to boot with XFS, but does boot when installing with ext4.

Having a journaling file system like ext4 on top of ZFS doesn't seem very... sane.

@JustineSmithies

Hey! Just tried both river (then didn't know how to exit!) and Hyprland and can run them.

This is how:
/etc/rc.conf contains seatd_enable=YES

I export XDG_RUNTIME_DIR as a temporary directory that is no backed by ZFS (this is why: https://hub.darcs.net/raichoo/hikari/browse/README.md#41)

I also export XDG_CURRENT_DESKTOP as the binary that I'm running.

Then run:
dbus-launch --exit-with-session "${GUI}"

I am a member of these groups:
MyOwn operator video u2f webcamd

@JustineSmithies

You should also look into flags that enable more verbosity, in case there is an error that is more helpful.

@JustineSmithies

Oh, and also:

> River can either be run nested in an X11/Wayland session or directly from a tty using KMS/DRM. Simply run the river command.

Does this work under e.g. sway?

@JustineSmithies have you tried starting river as:

dbus-launch --exit-with-session river -log-level debug > /tmp/riverlog

To see if there is something more useful?

Also: is polkit installed? (pkg info polkit)

@JustineSmithies nice! Soooo, how do the permissins for `/tmp` look like? is it backed by ZFS's tmp dataset? or is it a tmpfs?

@JustineSmithies great, so your user doesn't have permissions there! (try with your user mkdir /tmp/test)

That's probably the issue, are you sure it's a temporary file system? (mount -l should say something like tmpfs)
The permissions should probably look like this: drwxrwxrwt

Finally Open Sourcing a thing!

https://pypi.org/project/buildbot-phorge/

If you use #phabricator / #phorge (ehem #FreeBSD folks, ehem) and have always wanted to integrate it with #buildbot, this is your thing.

I've been using a much clumsier version of this for years, just made the time to clean up some quirks and apply better understanding of #buildbot's APIs.

Do let me know if you find this useful :-).