Also sidenote but wouldn't this make build lists disjointed resulting in
build status images not reporting the correct status? If so maybe a
more elaborate collaborator check would have to be implemented

>IIUC, it's not only related to secrets (which indeed can be shared), but also to the current usage of sharing a repository in an organization-like account and using that repository to run CI jobs with a common paying account (as suggested at https://man.sr.ht/ops/builds.sr.ht-migration.md).
>
>So previously, if ~user (identified by their SSH key) pushed to ~org/repo, the job was run with ~org account. Now it is run with ~user account. So, previously, this worked as ~org is paying, but now it does not as ~user is not paying.
Yes indeed basically

>This is by design -- sharing secrets is the intended approach now.
I see, fair enough, but until organizations are implemented what about the case of collaborator accounts?

I noticed in the following commit that now if a build is submitted by
git.sr.ht on a repo where multiple people have access, then instead of
the repo owner executing the build job, the pusher will:
https://git.sr.ht/~sircmpwn/git.sr.ht/commit/59efc979876f01d701e321e38d45c3147fb5f290

I understand the security concern (even though I'd say giving full
read/write access to a repo is a very broad permission in of itself),
but considering that organizations are not implemented yet, this poses
a bit of a problem, since if I understand correctly, only paid accounts
to which one has manually shared the secret from the organization
account are able to submit jobs for repos to which they just contribute
to, which is a partial solution at best.
Am I missing something here or was this an oversight?

>I'm using Free unfortunately, so I can't really help with that.
>
>But you've managed to send them?
Don't think so either, sorry

>It has been almost a year now that I am trying to make MMS work,
>and I still haven't succeeded now. I am using a PinePhone. When
>sending MMS, they are correctly sent to the ~/.mms directory,
>but they are never sent. By looking at the modem log, it knows
>when MMS are being sent to it, but mmsd-tng never seems to receive
>them.
>
>I am using a french carrier, if that matters.
Same here and I've had at least issues receiving them, if you're using Bouygues
then maybe we can figure out what's going on in a more specific manner

Ran into the same issue, at least on my side (a PinePhone Pro on postmarketOS)
I noticed that the callaudiod package is very out of date, and compiling the
latest version from source (0.1.9) seems to work, there is a MR on aports:
https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/47223

Thanks :) applied

To git@git.sr.ht:~yopaman/alias-website
   1936d3f..5c994aa  main -> main

Thanks :) applied

To git@git.sr.ht:~yopaman/alias-website
   8d4d573..3c4cfe1  main -> main

Thanks :) applied

To git@git.sr.ht:~chilledfrogs/simple-status-reporter
   887e71e..ceca156  master -> master