XSF Discussion - 2018-12-14

Ge0rG, ralphm: About SJ... [jdev] clients list,.. https://mail.jabber.org/pipermail/jdev/2013-January/thread.html [jdev] adding to list https://mail.jabber.org/pipermail/jdev/2013-February/thread.html [jdev] clients list,.. https://mail.jabber.org/pipermail/jdev/2013-March/thread.html https://mail.jabber.org/pipermail/jdev/2013-April/thread.html

Isn't it something that now that xsf knows about it, it has 30 days to enforce jabber trademark or lose it?

Maybe this'll finally kill jabber once and for all, long live XMPP

Does the XSF need to enforce that? Is that in the agreement with Cisco?

Zash: the original agreement requires the XSF to take action to not lose the sublicence.

Peter is on it

Persistent buggers...

Are they using the trademark anywhere except for in the domain name?

the application name itself?

oh no, they renamed themselves to SJ for that reason

I recall

https://mail.jabber.org/pipermail/jdev/2013-April/089420.html

yeah

We can ask what Peter did exactly back then

Has something changed in the mean time? Why is this coming up now?

Neustradamus, you brought it up, why?

From what I read in the mailing list archives, Peter was happy with them having renamed their product from "SafetyJabber" to "SJ", and retaining the domain name. From what I can read back, Peter explicitly restored their listing in our list of clients. ✏

Duplicate message?

edit

(SF -> SJ)

if your client does not support the XEP, it'll show as a new message.

Even if it does, in my case.

screenshot?

https://www.dropbox.com/s/ixy12iudbbqhrx8/Screenshot%202018-12-14%2012.47.31.png?dl=0

Might depend on your definition of last message

I like how Converse shows it: with a small icon to indicate that the message was added, which opens a popup with the change history

https://xmpp.igniterealtime.org:7483/httpfileupload/9f967081-c41e-496f-9b3c-f49089f89e08/Screenshot%20from%202018-12-14%2013-52-39.png

Hargh, one of these days I'll learn to not press the 'close' icon in a screenshot.

every. bloody. time.

Guus, thanks for remember me to update converse.js ;)

genofire github now supports a 'watch for releases only' type of thingy.

i know - i also have to current release -> just want to update to master/HEAD

quick poll: I am looking at the LCs which need to be re-emitted due to board/council switchover. There is at least one. I am considering to delay the re-opening until after western New Year’s, because I *assume* that many folks won’t be able to act on the LC anyways.

Opinions?

my opinion in this case probably doesnt count much, but seems like a sane idea, just make sure its not forgotten after NY and we find it in 3 months again

will put it in my calendar :)

jonas’: which LC is there? 0280?

'381 for board, '363 for Council

'280 is ... in an unclear state, too

Is 363 fixed now?

not sure

not as far as I can tell

there was something added about CORS, but it’s unrelated

So it's still rejected?

AFAICT, yes

you have to tell us that :)

anyways, heading to bed

I need to read the diff