jdev - 2022-05-29

Hello, I need your help https://github.com/ge0rg/easy-xmpp-invitation/issues/34

Schimon, why do you worry about file xtensions btw? I guess you can get the list of doap files from xmpp.org, or maybe it should be made available if not already. And that can be cached somewhere on the website serving the invitation thing

Also I'm not sure why you'd use doap here

1. I like things to be constructive and clear. 2. Me too. emus has suggested it, so why not? Also, these files are intended for use with other projectd, judt copy&paste.

I just pointed that there are doaps if that appears to be useful

Yes, it is, IMHO

Because, if others are interested, they can copy DOAP files from one project to another with ease (no need to make one from scratch nor to start to lookup for clients etc.) It's great

For example, some SVG files on that commit were made by myself from PNG files, and that costs time. You get the point... ✏

For example, some SVG files on that commit were made by myself from PNG files, and that costs time, and I'm not a graphics designer. You get the point... ✏

the DOAP file format is missing a "link to native app store" BTW

making it cumbersome for the specific goal within the easy-xmpp-invitation project

It might make sense to use the <download-page/> element, but I'm not sure if everybody does so, and how to allow "fallbacks"

FYI wurstsalat ^

Ok I thought you'd use doap to choose which app to suggest, which would not be practical to me

I'd love to be able to do that as well, but

> Ge0rG: > 2022-05-29 05:01 (GMT+03:00) > the DOAP file format is missing a "link to native app store" BTW XML is customizeable, so we'll add three to four (yes, that's 3 - 4) links. 1. Homepage 2. Proprietary repo 3. F-Drpid app store

Schimon: there are DOAP files for most relevant XMPP clients already

The question is how to integrate them in a useful way into a JS client app

> Ge0rG: > 2022-05-29 05:02 (GMT+03:00) > making it cumbersome for the specific goal within the easy-xmpp-invitation project I think it's gonna be simple, in the modular sense. I'll make a draft commit and you'll judge

You'll see. You'll see

> Ge0rG: > 2022-05-29 05:36 (GMT+03:00) > Schimon: there are DOAP files for most relevant XMPP clients already I know

But because this is related tp XMPP, in the UX sense, I think DOAP is a good idea

> Ge0rG: > 2022-05-29 05:15 (GMT+03:00) > It might make sense to use the <download-page/> element, but I'm not sure if everybody does so, and how to allow "fallbacks" Please explain "fallback"

Schimon: it's great to have the download link be the respective app store, but also to have some "fallback" link to f-droid, apk download or whatever's suitable

Awesome, so we'll make it 5. But this means that server has to have APKs on it's systwm, because XSS is not allowed by most web browsers.

Forget what I wrote.

Wh ywould the server need to have APKs. I think Ge0rG is saying the client DOAP may point to an APK itself. Something like Signal is doing (serving APKs on signal.org)

heh

It imeans that we must check for HTTP status 200. How can that be done in JS if XSS is not allowed in most browsers?

Or provide a fixed fallback in an additional link

Schimon: I'm not sure what you want to achieve, but your questions imply that you need to rethink your strategy :)

Yes

I think from a user-perspective there should be a pre-selection and maybe link for advance view to the new client page at xmpp.org

I'm not sure I understand, there is a link to xmpp.org already, or do you mean to something else.

pep., Ge0rG: I posted a new comment concerning fallback

I would personally avoid querying these files every time the page is queried and I'd cache them