XSF Discussion - 2021-01-03

for another org I volunteered with we had automated builds of every branch on staging.$domain/$branch/

Alright, I’ve optimised the docker thing a bit, it doesn’t require an xmpp.org mount anymore, instead it will git pull its inside copy.

Also no more intermediary copy, I got told having multiple RUN commands will create as many intermediary copies.

The data used by https://linkmauve.fr/extensions/ are now generated from docker.

Looks nice, the mix of logos and names is a bit confusing though

That’s because not all clients updated their DOAP with a logo yet.

marc, how else would you represent them?

I’ve also tried playing with CSS to address lskdjf’s comments, but I only managed to make it worse.

Link Mauve: BTW is Conversations doap file not working somehow?

Or do I need to register the existence of the file somewhere?

Daniel, you should add it to your entry at xmpp.org: https://github.com/xsf/xmpp.org/blob/master/data/clients.json#L139

I don’t maintain a list of my own, instead I rely on xmpp.org’s data.

I see. Thanks

You should move your logo property in the https://schema.org/ namespace, fyi.

Here: https://github.com/iNPUTmice/Conversations/blob/master/doap.rdf#L25

Also reference your actual logo (SVG preferred), instead of the DOAP file itself. ^^

(you could have been forgiving and allowed the old logo description, so that it does not make a mixed mess until all your PRs get accepted :p)

mathieui, none of the projects which used my old xmpp:logo (which lasted for only one day) use it anymore.

Both Prosody, Gajim and poezio updated to the new one, while Dino skipped the xmpp: one altogether. ✏

In the first version I shared, I was fixing the DOAP files myself to add each project’s logo.

Except for slixmpp, which doesn’t have one.

Link Mauve: maybe a fallback placeholder logo could be added? Or a coloured square with the initial of the project :)

Code welcome!

In JS or Rust.

I just hope we can merge this soon instead of forever trying to make it perfect

+1

To be clear, I'm not in a position to contribute code right now and neither will I object to it being merged without placeholder logos

Just offering a suggestion about how to fix the visual issue (the best solution is for every project to have a logo)

Haven't looked at the latest version but the one I saw was weird because it had the Prosody logo with 'slixmpp' after it sometimes

Separate columns improve that, but still potential for confusion

FWIW columns speraration is much better on the dark theme

my proposal would be to show the count of supporting clients/servers/libs only. XEP pages already have a list of all the clients/... including their logos.

Oh right, I haven’t tried the light theme in a long while.

Link Mauve: have you tried sorting it by logo presence?

First all with logos and then all without

wurstsalat, I find that extremely dire and unhelpful tbh: https://linkmauve.fr/extensions/

marc, I expect this won’t be an issue anymore once all clients have a logo.

wurstsalat, here with a denominator giving the total amount of projects.

Maybe I could do a percentage instead?

Link Mauve, it does not look as exciting, that’s right. but which info do you want the viewer to gather from a list with those logos? as soon as there are 7+ logos, you cannot display them nicely anymore.

Here with a percentage.

Link Mauve, yep, probably that's true. Except if projects don't have a logo at all :)

Although now it doesn’t indicate which ones have a complete or partial implementation, hmm…

since XEPs are for various use cases, I’d stay away from percentages :)

Indeed.

Right, it’s back to a number of implementation.

if you’d be a viewer wanting to compare clients, it would be best to make the ones selectable you want to compare, since you cannot display every client logo at once. or am I getting this use-case wrong?

Link Mauve: filled horizontal bars with the width being proportional to the number of implementations!

wurstsalat: that's something I'd love to see in the implementations list

Patches welcome! I’m not very good at web stuff.

But I’d be fine with merging that stuff as is, and leave improvements for later.

Link Mauve, following that idea, you could for example select {Conversations, Dino}, display logos of just these two clients if they support the respective xep, and add a number afterwards for remaining clients (like this: "[logo1] [logo2] (6 more)". but yes, this sounds like something to implement later :)

Interesting idea. :)

If you ignore the number afterwards you can probably do it all in just CSS with no JavaScript too.

Atm the whole integration comes from JS though. :(

Integration?

Fetching the JSON file from xmpp-doap and adding the Implementations column in the XEPs list, or the new table in each XEP.

oh, gotcha, that seems unfortunate.

Indeed, I’d rather integrate it with Pelican (hence why I labeled this a proof of concept on standards@), but I’ve never been able to build our Pelican website so I’d rather not write code blind.

Either way, you can probably do the filtering part in CSS and it's one less thing to figure out how to integrate / move over later.

Filtering and/or overflow if there are too many logos.

Indeed. :)

Overflow I tried this morning, and couldn’t figure out how.

I wanted overflow: auto, but it requires display: block, which then moves adjacent <td/> one below the other…

Another thing I plan to make with these data is an automated Compliance Suite marker in implementation lists.

very much yes! :)

any news on compliance badges btw?

I have a thing that can tell if you're compliant based on your doap

Zash: is it a webservice?

Me? A website? Never.

Is there a XEP to store URLs like defined in XEP-0048: Bookmarks? It's out of scope for XEP-0402: PEP Native Bookmarks. But 0402 should be used instead of 0048. Is it correct?

https://xmpp.org/extensions/xep-0195.html almost?

The elements looks good. I thing a mimetype field would be nice. The XEP is about browsing - current activity - but should also work for storing information. I just implemented 0048, I try to change it to those two XEPs. Thx.

One more question. Is it possible to have a kind of real time sharing of a text file? For instance, 5 people are working on a file at the same time.

I was thinking to just share the content via a pubsub node item. But maybe there is another / better way to handel this.

If you want this to be real time edits you probably need something more complex than just uploading the file to a pubsub node.

Other than that pubsub is not a bad choice I reckon

Also isn't there a collaboration edit xep already?

There certainly is one for svg

https://xmpp.org/extensions/xep-0284.html this?

Sound good 👌