jdev - 2022-01-10

I'm confused about the wiki recent changes where I see membership applications for 2022 https://wiki.xmpp.org/web/Special:RecentChanges?hidebots=1&limit=50&days=7&enhanced=1&urlversion=2 but I don't see the applications list of 2022 here https://wiki.xmpp.org/web/Membership_Applications Can I apply now or I have to wait?

https://wiki.xmpp.org/web/Membership_Applications_Q1_2022 ?

Thank you Zash

Should I create my application page and name it My_Name_Application_2022 manually or it there is something else I'm missing?

xnamed, I use User:NAME/Application_YYYY, where NAME is my wiki user name and YYYY is the year number

so I don't pollute the global namespace with all that

jonas’: given that you also apply for Council, some more namespacing might be appropriate ;)

Ge0rG, User:NAME/Council_YYYY for that :)

IIRC ✏

I didn't check

:D

https://news.ycombinator.com/item?id=29871358

Thank you jonas’

i've put up a simple webhook->xmpp solution at https://slickmsg.com/ ... I'm unaware of there existing any other one open to the public. i still have to create the privacy-policy and terms-of-service, but i've tried to keep everything simple and easy to use. i plan on creating a blog section with some guides on how eager users can setup their own similar solutions. please share comments/suggestions/improvements with me ... junaid@yax.im (i know it's ugly but I don't have any plan on making it pretty any time soon)

possibly relevant: https://modules.prosody.im/mod_slack_webhooks.html

yip, there's quite a few way to implement similar. prosody alone has multiple plugins that could be used/abused to fulfil the requirement ... mod_post_msg , mod_rest, etc. majority of people just get accounts on established xmpp servers.. but are then left without an API/webhook system for automation/scripts. (API/webhook automation already established as core functionality for most other walled-garden platforms)

junaid, this is excellent! It really needed to exist :)

mmmmm, webhook.jabber.network? :)

MattJ 👍️ jonas’ that subdomain aint resolving for me, or is it a joke? in which case i prob need ☕️ refill

junaid, it was a low-key offer that I could point that subdomain at your service if you wanted to rebase it to use that.

thanks for the kind offer jonas’. i'll keep a note of it. for now, i think let's first validate the idea before making long-term decisions. user adoption and potential for abuse are my main concerns. usability is also a concern but that will only be improved as more people use it and provide feedback.

One suggestion I have is to reuse an existing API format (or better: multiple). That way you will have immediate support for lots of existing software/services.

For example, Gotify would be relatively straightforward: https://gotify.net/api-docs#/message/createMessage

good idea and added to the TODO list. any other compat-API requests?

I've been trying siskin on iOS for some days now, it's not that useable... it keeps duplicating MUC messages countlessly :( is there some specific room to complain about iOS clients?

Siskin feedback specifically would probably best addressed in the tigase MUC

nephele, https://search.jabber.network/search?q=tigase+support -> xmpp:tigase@muc.xmpp.org?join

Oh neat, a room searcher... thanks :D

jabber.network is the new Google

2 now :)

in a non anonymous room prosody returns all the connected resources of the user

is this something i can expect from other servers aswell?

it's unspecified

great

I know, right?

probably also if full jid or bare jid

exactly

so i can get, one bare jid, one full jid, or multiple full jids

wonder if i should downgrade to one bare jid at lib level

or pass on whatever i get, and let the app deal with it

I think it tends to be more annoying when a library (or any other information source) eats/strips the information you can use, rather than when it provides a bit more than needed.

Applications too

See also: most xmpp clients

disagree for applications

many users find too much information to be overwhelming

as im in the position to write the lib AND the app, i find it in the app really anoying, if i cant depend on things. and always have to if/else everything

especially if its something that is unspecified and only a few servers do, and may stop at any moment

i rarley want to depend on such things as an App

but as a lib, i parse everything into useful structs for the app, but i leave an escape hatch open as the app can always look at the stanza from which the struct was created

Guess im just a diehard power user

Hidden stuff rubs me raw

qy, you are indeed

(I am, too)

helo

Hello

I was about to say, this isn't about SMTP ;)

hello

Ehlo

501 Syntax: EHLO hostname

heol ohtsanem