From: indieterminacy <indieterminacy@libre.brussels>
To: Steve George <steve@futurile.net>, help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: You're invited to the first patch review session!
Date: Fri, 23 Feb 2024 20:43:44 +0000 [thread overview]
Message-ID: <2e494348484565a6fa49cbd19d6bca67@libre.brussels> (raw)
In-Reply-To: <ZdjuUotTJMk02Z2U@ws>
Hello,
>> On 2024-02-23 19:13, Tomas Volf wrote:
> On 2024-02-22 23:27:31 +0000, Steve George wrote:
...
> Will the Jitsi link be shared somewhere (here, irc, ...) for those of
> us who are
> not able to sign up on the page? I am getting this error:
>
>> Your IP address has been flagged as a source of spam and is blocked
>> from
>> Meetup.
>
> Since meetup.com is a commercial, third-party service, I assume there
> is not
> anything you can do about that, so I am curious if there are any
> alternatives
> how to get into the review session.
>
Well, I did use Mobilizon for the Friday dinner for Guix Days - which
though lacking some features is FOSS and Fediverse tech.
https://mobilizon.nl/events/ee570f76-1898-43ff-88f0-86f18608ff2d
It does permit email (as opposed to registration) to confirm - though I
noticed that only 1 or 2 people actually provided any information for me
to discern them.
... I guess it meant the system reduced the risk of spam signups but
simultaneously didnt enforce accountability to an organiser.
On a legal basis Id assert that the specific instance being based in the
Netherlands would be advantageous than wherever Meetup queries; routes;
and caches.
It is run by some random volunteer, with all the carnets of such trust
domains.
In any case, Im going to try to participate in these events, I reckon it
would be a good compensation for there not being a regular Guix meetup
in Belgium.
Kind regards,
Jonathan
next prev parent reply other threads:[~2024-02-23 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 23:27 You're invited to the first patch review session! Steve George
2024-02-22 23:53 ` Vagrant Cascadian
2024-02-23 6:11 ` Vivien Kraus
2024-02-23 14:59 ` Steve George
2024-02-23 19:13 ` Tomas Volf
2024-02-23 20:43 ` indieterminacy [this message]
2024-02-29 17:10 ` Daniel Littlewood
2024-02-29 17:35 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 19:11 Suhail
2024-03-05 19:19 ` Etienne B. Roesch
2024-03-06 9:40 ` Andreas Enge
2024-03-06 11:28 ` Tomas Volf
2024-03-06 11:36 ` Etienne B. Roesch
2024-03-06 11:40 ` Tomas Volf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e494348484565a6fa49cbd19d6bca67@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=steve@futurile.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).