XSF Discussion - 2018-07-02

https://blogs.gnome.org/tbernard/2018/05/16/banquets-and-barbecues/ Apparently a bunch of folks missed it so I'm pasting it here

Interesting

To some extent conversations already has the distinction they make here.

Not in the listing, but in the rooms themselves

pep.: how?

how?

That article has some profound chat usability analysis, I'm impressed.

pep.: pep. [17:33]: > To some extent conversations already has the distinction they make here.

members-only&realjids rooms have a different treatment

Yes, but how?

how what

Different levels of notifications maybe?

Doesn't Swift do something too, or was that just for impromptu MUCs?

How are they treated differently?

IIRC only loud notifications for direct mentions in public rooms

Smaller private rooms would notify on any message

Also the OMEMO thing

Ge0rG, uh, I thought, might be wrong indeed.

Or maybe it's just stuff I heard about

Yes private && non anon change some defaults. Like notifications and omemo

Also iirc those will automatically get bookmarked

"private" only means "members-only" here right? Or does it also imply non-public?

daniel: what notification changes are there? Highlight VS everything?

pep.: when I say private I mean members only

> daniel: what notification changes are there? Highlight VS everything? Yes

That's actually useful.

But I generally try to use that as an indication for those two styles of group chats. Even if for now it's only those two settings that change I will probably use the same metric for other things in the future

"join a banquet"

Dress up (with a fancy nickname)?

Zash, https://en.wiktionary.org/wiki/banquet the 1.

Opposite to "barbecue", which I assume they mean as a smaller group

jonasw, did you ever get that _acme-challenge cname server type thing set up like you talked about?

moparisthebest, nah, I am still on delegations

never change a running system

yea I'm thinking of changing my running system(s) to wildcard certs though, which means dns instead of http :'(

I found https://github.com/joohoi/acme-dns but meh I tthink I'm just going to hackily sed my bind zone file

I'm using dehydrated wih a manual zone editing process. It's very painful

I have always been using the DNS challenge. For my setup it's easier than http

nothing is simpler than http if all your hosts run nginx, location ~ "^/\.well-known/acme-challenge/([-_a-zA-Z0-9]+)$" { default_type text/plain; return 200 "$1.KEY_HERE"; }

no communication, no deploying anything

but can't use that for wildcard I guess