const trustedWebInstances = [
    "app.element.io",   // first one is the default one
    "develop.element.io",
    "chat.fedoraproject.org",
    "chat.fosdem.org",
    "chat.mozilla.org",
    "webchat.kde.org",
];

In twim and matrix live a few months ago, it was revealed that hydrogen is planned to become the engine of element web.

However- with the new cross-platform rewrite of element in rustlang.

If anyone has any updated possible information, I would be appreciative! (this would assist us with deciding whether we may embed element in our company's operations).

Transpiling from rust to wasm seems inadequate to rewrite element web since wasm doesn't have API access - requiring js (and potentially hydrogen) regardless. So it may (or may not!) be worthwhile for us to wait until the great day of "hydrogen powered element-web" may happen 😀

Thank you

In reply to @yosefsinger:matrix.org

In twim and matrix live a few months ago, it was revealed that hydrogen is planned to become the engine of element web.

However- with the new cross-platform rewrite of element in rustlang.

In reply to @yosefsinger:matrix.org

If anyone has any updated possible information, I would be appreciative! (this would assist us with deciding whether we may embed element in our company's operations).

Transpiling from rust to wasm seems inadequate to rewrite element web since wasm doesn't have API access - requiring js (and potentially hydrogen) regardless. So it may (or may not!) be worthwhile for us to wait until the great day of "hydrogen powered element-web" may happen 😀

Thank you

In reply to @bwindels:matrix.org
Don't wait for that day, it may never come. If you want to integrate a matrix client into your existing product, you have the option of using matrix-js/react-sdk or hydrogen-view-sdk. Which one to use depends mostly on what features you need and whether the benefits of Hydrogen (less memory usage, better offline support) are important for your case. Also, Hydrogen is less tested and has less resources behind it.

Our requirements are actually requiring a pre-made client to embed directly in a web page (not sdk, not enough manpower)

• yet element web doesn't suffice. since it's only being used from mobile and element web doesn't have an ideal mobile layout at all yet.

That's why we were looking to hydrogen but more feature complete.

Maybe fluffy chat? It's not as performant on mobile though.

In case anyone has any ideas - feel free to message! We'll try figuring out our options! Thanks again Bruno

Our requirements actually require a pre-made client to embed directly in a web page (not sdk, not enough manpower)

yet element web doesn't suffice... since it's mainly for use on mobile (and element web doesn't have an good mobile layout yet).

That's why we were looking to hydrogen - just it needs some more feature completeness.

Maybe fluffy chat? It's not as performant on mobile devices though.

In case anyone has any ideas - feel free to message! We'll try figuring out our options! Thanks again for clarifying 👍

Our requirements actually require a pre-made client to embed directly in a web page (not sdk, not enough manpower)

yet element web doesn't suffice... since it's mainly for use on mobile (and element web doesn't have an good mobile layout yet).

That's why we were looking to hydrogen (just it needs some additional features).

Maybe fluffy chat? It's not as performant on mobile devices though.

In case anyone has any ideas - feel free to message! We'll try figuring out our options! Thanks again for clarifying 👍

Thanks for clarifying 👍

Our requirements actually need a pre-made client to embed directly in a web page and an sdk wouldn't be an option (not enough manpower)

yet element web doesn't suffice... because it's mainly for use on mobile (and element web doesn't have a good mobile layout yet).

That's why we were looking to use hydrogen (but that would need more features than it has resources for)

Maybe fluffy chat? It's not as performant on mobile devices though.

In case anyone has any possibilities in mind...

In risposta a @yosefsinger:matrix.org

Thanks for clarifying 👍

Our requirements actually need a pre-made client to embed directly in a web page and an sdk wouldn't be an option (not enough manpower)

yet element web doesn't suffice... because it's mainly for use on mobile (and element web doesn't have a good mobile layout yet).

That's why we were looking to use hydrogen (but that would need more features than it has resources for)

Maybe fluffy chat? It's not as performant on mobile devices though.

In case anyone has any possibilities in mind...

so i'm trying to sign in to my matrix instance with hydrogen web (and i don't know of a support channel so i'm here), but after logging in, the client (hydrogen web) errors with

Something went wrong: The operation is insecure..

i don't understand what it means by "the operation is insecure", given that it did not make any more requests to my home server other than a GET login, POST login, and a GET dehydrated_device which returned a 404 (error message: "No dehydrated device available"). what's a way to, well, fix the issue of not being able to login?

so i'm trying to sign in to my matrix instance with hydrogen web (and i don't know of a support channel so i'm here), but after logging in, the client (hydrogen web) errors with

Something went wrong: The operation is insecure..

i don't understand what it means by "the operation is insecure", given that it did not make any more requests to my home server other than a GET login, POST login, and a GET dehydrated_device which returned a 404 (error message: "No dehydrated device available"). what's a way to, well, fix the issue of not being able to login?

In reply to Midhun
jacksonchen666: try https://github.com/vector-im/hydrogen-web/issues/313#issuecomment-843297570