Accurate-Screen8774

joined 11 months ago

The app is still very much a work in progress, and while it's functional, it's far from being a finished product. Therefore, open-sourcing the code is not currently in our plans, especially for the experimental parts.

We place a strong emphasis on security, and you can find some of our cryptography-related code open-sourced for public review. We're committed to making sure our security measures are transparent and robust.

If there's a popular demand for downloadable statistics in a zip format, we can certainly provide that option directly within the app.

For those who are interested in self-hosting the app, it's important to note that hosting the static files is just one part of the equation; ensuring the app maintains strong security through measures like CSP headers is equally vital to protect your data from potential threats like browser plugins.

Our CSP header configuration and rating can be seen here.

[โ€“] Accurate-Screen8774@alien.top 1 points 11 months ago (2 children)

maybe in the post it isnt clear. there are 2 diferent types of self-hosting.

- selfhost the statics - ctrl/cmd+s to save the statics and host them on a static-server of your choice (easier than me providing a .zip?). this can be done with something like `npx serve /static-folder-with-files`

- the app is made to not rely on a backend for authentication, but peerjs-server is used to make initial connection. you can select the peerjs server on the "create profile" screen. (note: a profile is locked to a specific peerjs-server which is set whern you create a profile)

 

I'll try make this short and sweet. Using PeerJs its possible to connect browsers over a fast WebRTC connection. So i slapped on material-ui to see what is possible using this technology.

The app is available here.

my code results in the static files you can save from the link to the app (html, js, css, etc). you can ctrl/cmd+s to save the statics and host them on a static-server of your choice (easier than me providing a .zip?). you can also host your own peerjs-server.

The app is not production ready, but it is provided as a testable work-in-progress demo. it would be great to hear opinions on how the project is shaping up.

(feature requests + bug reports welcome :) )

 

I'm working on a self-hosted project and am contemplating the idea of introducing Google Ads. However, I have a few concerns and would love to hear your thoughts:

User Growth: I am inclined towards gaining more users at this stage and worry that introducing ads might deter some potential users. What has been your experience with introducing ads in the early stages of a project?

Security: My project prides itself on maintaining a high level of security, and integrating external JavaScript scripts like those required for Google Ads could be perceived as a compromise. Though I believe the risk is no more than on any other site, I'm wary of the perception. How have you navigated this in your projects?

Affordability: Currently, the costs for Amazon S3 are manageable without the income from ads. However, monetizing through ads could provide a cushion and potentially accelerate the growth of the project.

Community Perception: Lastly, how has the community responded to ad integration in your projects? Have you noticed a change in user engagement or community sentiment?

I truly value the insight and experiences this community can share. Thank you in advance for your help!