thanks for your thoughts. npm is popular for a reason and vanillajs doesnt scale very well. so any deps used could be an issue.

i was also considering if with the webcomponent approach it could be “furture-proof” as it seems to be the rhetoric i hear around. im sure i wont have a great implementation any time soon, but id like to try out a few ideas to see if it holds-up. hopefully to lead to a “secure javascript ui framework” (which itself could be a whole discussion).

but based on all the feedback ive recieved, it seem for the messaging app refactor, i’ll be fine to use react on it. which is great because i already have a working-ish demo.

thanks for your thoughts.

thats not quite what im asking. im wondering if there are nuanced benefits to using webcomponents over something like react. with the key difference being the native support.

i hope with the webcomponent approach it could be “furture-proof” as it seems to be the rhetoric i hear around. im sure i wont have a great implementation any time soon, but id like to try out a few ideas to see if it holds-up. hopefully to lead to a “secure javascript ui framework” (which itself could be a whole discussion). i hope that by having it open source, i can point to an example to discuss and improve it.

it seem for the messaging app refactor, i’ll be fine to use react on it. which is great because i already have a working-ish demo.

thanks. thats what id like to aim for and i dont think its far off. the build script there is mainly for the storybook statics (as seen in the link provided for “website”).

couple things i hope to do soon, remove lit as a dependency - i use this right now because its useful for template rendering and lifecycle methods. webcomponents have a an ugly approach to this which Lit makes easier, and so i pushed it back, but its still on the todo.

after that i should be able to have a more vanilla web dx.

Thanks!

https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm/

Tldr; I had that question before myself. It doesn’t seem to introduce any improvement over WebCrypto API which itself should have gone through peer-review and auditing. (“Choose your browser wisely” could be considered the advice here.)

I’d like to still look into wasm for several other details of the project, but it seems the built-in browser cryptography functions are performant and generally pretty good if used correctly.

thanks for the clarity!

do you have any links to share about it?

By feature, do you mean “foss”? (Wondering if you’re replying to the correct thread)

If so, then it’s unfortunate I’m investigating this direction, it seems nessesary.

Otherwise feel free to let me know of a critical feature missing (if “foss” is not the feature you meant.)

No. When I type with “correct capitals”, it’s because I’m doing it from my phone. I otherwise generally might sound like chatgpt.

I’m no expert on the matter of licences either. I made the open source code some bsd licence because some of the dependencies called for it.

I created some code and made some open source. I don’t have to apply that to all my projects.

I mean to draw attention to the open source code in such a case.

If interested in how it works and to see code examples, this project is based on my beefier open-source code seen here: https://github.com/positive-intentions/chat

Thanks. I hope to get to a point where I can make the experience as seamless as workhole.

To compare solutions, a key details around providing my app as a webapp, is to avoid the requirement of a client. this opens up the set of compatible platforms.

(Note: it’s a common request for me, so by popular demand, i will aim to provide binaries for the major platforms.)

For me, it’s an achievement for it to be comparable to those tools. I aim to get to a similar feature set and make the user experience intuitive.

I tried foss. I couldn’t get it to work so i’m trying something different.

Just to be clear, my own open source code. Yes.

Strong title needed for strong claims.

Its based on open source code. https://github.com/positive-intentions/chat . I’d be happy for feedback on that too.

Webrtc would be able to outperform all other methods for transfer speed (useful for when sending larger files)

I’m sure there is a market for eople who want to transfer files. With a zero-installation, zero-registration, it should make it easy for people to get started.

Hey. I’m the dev.

this project is an investigation into monetization by going close source (to create something competitive).

A separate but related chat project is a beefier version for the functionality seen in the parent post. Id be interested to get feedback on it just as much.

https://github.com/positive-intentions/chat

Thanks for the empassioned speech/statement!

Perhaps you’d be interested in one of my open source projects. It’s a beefier version of the app presented in the parent post.

https://github.com/positive-intentions/chat

On the point about open source, it isn’t easy to pull off. I can confirm it isn’t the case that open-source be flooded with some kind of collective community review/support. It’s been an option for the chat app for a while and I’ve tried actively promoting it, it’s clear that the project is simply too complicated.

I’m a bit disappointed in how hard I tried on the open source project for it to not get the traction I wanted. To create somthing close-source and competitive in the file-transfer space is only logical at this point.

I’m sure with an enthusiastic speech like that, you’re doing your part for supporting the open source community. Unfortunately I couldn’t figure out how to get it to filter down to me.

I’m in the process of rebranding and moving domains, so the documentation links are broken. You can try the search. it seems to work reasonably well. A good place to start could be from here:

https://positive-intentions.com/docs/research/authentication#authentication-sequence

Feel free to reach out for clarity on anything.

I haven’t heard of Dibbles. Can you point me to their site?

Thanks.

I have a similar open source project. https://github.com/positive-intentions/chat

My general thoughts are that it isn’t sustainable. While it clearly isn’t a contender in the messaging-apps market, I think it demonstrates a unique concept in how it works as a webapp.