Easy invite for website #27

Open
opened 2 months ago by poVoq · 7 comments
poVoq commented 2 months ago

https://github.com/ge0rg/easy-xmpp-invitation

Maybe be a cool feature to add to the joinjabber.org website.

https://github.com/ge0rg/easy-xmpp-invitation Maybe be a cool feature to add to the joinjabber.org website.

From my understanding this requires mediation by the homeserver so this doesn't apply to joinjabber.org which is a MUC server? Am i missing something?

From my understanding this requires mediation by the homeserver so this doesn't apply to joinjabber.org which is a MUC server? Am i missing something?
Poster

No this one doesn't (unlike the Snikket one). It is just a nice website to share as a link with new users.

No this one doesn't (unlike the Snikket one). It is just a nice website to share as a link with new users.
Owner

So it appears someone else is writing a such tool. Maybe the two efforts might converge, who knows. That new development is based on the idea to list public gateways when linking to other networks (eg. IRC).

Here's a few potential logos for presenting IRC: 1 2 3 4

Personally, i have preferences for 1 and 3.

So it appears someone else is writing a such tool. Maybe the two efforts might converge, who knows. That new development is based on the idea to list public gateways when linking to other networks (eg. IRC). Here's a few potential logos for presenting IRC: [1](https://dl2.macupdate.com/images/icons256/59806.png?d=1505307487) [2](https://www.podfeet.com/blog/wp-content/uploads/2016/09/irc_chat_logo.png) [3](https://raw.githubusercontent.com/factor-io/connector-irc/master/logo.png) [4](https://3.bp.blogspot.com/-07hwvoONmrs/UNMswhxbAZI/AAAAAAAAF7I/TsYP3yhW2pA/s1600/IRC_Twitter_Logo.jpg) Personally, i have preferences for 1 and 3.
Poster

I like logo 3 the most.

Such an invitation page could also be used to share server recommendations, like this:
https://xmpp-servers.404.city/?r=joinjabber.org

I like logo 3 the most. Such an invitation page could also be used to share server recommendations, like this: https://xmpp-servers.404.city/?r=joinjabber.org
Owner

Here's a comparison of solutions we could use:

  • yax.im implementation (source, user demo, MUC demo)
    • "TODO: proper error checking"
    • a page view requires 9 requests (that's a lot) but only 22KB (that's small) ; could probably be aggregated in a build pipeline for better load times
    • does not display information about JID (name, avatar) beyond its type (chatroom or user) ; does not check if it's a working XMPP address at all
    • simple javascript, no framework
  • 404.city implementation (source?, server demo)
    • only supports server recommendation? not user/room?
    • can't find the source code
    • does not display much information about that server: does not check whether it's a MUC, or if it's a XMPP server at all
    • 40 requests, 740KB page, including a lot of 3rd-party requests to xmpp.net and compliance.conversations.net (+ CDN)
    • jquery framework
  • stfefan implementation (source, IRC chan demo)
    • currently focused on onboarding XMPP users to IRC chans via public biboumi gateways ; no support for user/MUC/server recommendations
    • 5 requests, 380 KB
    • vueJS framework
    • tracking issue on bridging WG

All of them operate fully on client-side, and don't require a web backend:

  • really good for user invitations/recommendations, because it avoids leaking some social graph to the server
  • prevents querying info about the linked JID, except by bundling an actual XMPP + websocket/bosh client into the webpage (and not all servers may support that, but maybe it's a feature to "discard" those servers?)

Feel free to take this comment and update the issue accordingly :)

Here's a comparison of solutions we could use: - yax.im implementation ([source](https://github.com/ge0rg/easy-xmpp-invitation), [user demo](https://yax.im/i/#user@server), [MUC demo](https://yax.im/i/#user@server?join)) - ["TODO: proper error checking"](https://github.com/ge0rg/easy-xmpp-invitation/blob/master/scripts/main.js#L50) - a page view requires 9 requests (that's a lot) but only 22KB (that's small) ; could probably be aggregated in a build pipeline for better load times - does not display information about JID (name, avatar) beyond its type (chatroom or user) ; does not check if it's a working XMPP address at all - simple javascript, no framework - 404.city implementation (**source?**, [server demo](https://xmpp-servers.404.city/?r=joinjabber.org)) - only supports server recommendation? not user/room? - can't find the source code - does not display much information about that server: does not check whether it's a MUC, or if it's a XMPP server at all - 40 requests, 740KB page, including a lot of 3rd-party requests to xmpp.net and compliance.conversations.net (+ CDN) - jquery framework - stfefan implementation ([source](https://codeberg.org/mmbd/xmpp-irc-join), [IRC chan demo](https://ipfs.io/ipfs/QmbpeNrj2WNgfoKUqhauawCss2zH3R5cAYjVKCDwNQBX9U/?c=wikidata&h=irc.libera.chat)) - currently focused on onboarding XMPP users to IRC chans via public [biboumi](https://biboumi.louiz.org/) gateways ; no support for user/MUC/server recommendations - 5 requests, 380 KB - vueJS framework - [tracking issue](https://codeberg.org/joinjabber/bridging/issues/3) on bridging WG All of them operate fully on client-side, and don't require a web backend: - really good for user invitations/recommendations, because it avoids leaking some social graph to the server - prevents querying info about the linked JID, except by bundling an actual XMPP + websocket/bosh client into the webpage (and not all servers may support that, but maybe it's a feature to "discard" those servers?) Feel free to take this comment and update the issue accordingly :)
Poster

I think the main feature lacking from the yax.im implementation is a web-frontend for the inviter. Apparently it exists from within the yax.im Android client, but a page where you can chose a few paramaters and then have a "click here to copy link to clip-board" button would be nice.

I think the main feature lacking from the yax.im implementation is a web-frontend for the inviter. Apparently it exists from within the yax.im Android client, but a page where you can chose a few paramaters and then have a "click here to copy link to clip-board" button would be nice.
Owner

I think the main feature lacking from the yax.im implementation is a web-frontend for the inviter.

That would be super easy to do. Maybe we can give it a try?

> I think the main feature lacking from the yax.im implementation is a web-frontend for the inviter. That would be super easy to do. Maybe we can give it a try?
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.