webtorrent VS openreplay

It's because of the kind of content that is shared. BitTorrent serves a lot of content you are not allowed to redistribute, so having an open gateway immediately puts you at risk of aiding the distribution of content. But it does work, someone even made something native to browsers so browsers themselves can share content: https://webtorrent.io/. There are even fuse "gateways" to make it native to your computer and pretend the files exist locally: https://github.com/search?q=bittorrent+fuse&type=repositorie...

IPFS doesn't seem to be used for that kind of content much, it seems to be targeted more towards web-native content (html pages, images, that kind of stuff). It's probably safer for Cloudflare to run this.

title. I have some experience with c++ but not much with torrent libraries. (webtorrent, stremio)

You can stream torrents

If it fits your model, WebTorrent[0] can offload a lot of bandwidth to peers.

[0] https://github.com/webtorrent/webtorrent

Then https://github.com/webtorrent/webtorrent could be used to actually download the videos in browser, the idea being here though, that you would at least seed out as much as you got. Enabling other's to access videos without requiring creators have the infrastructure to push a video to 1000s or more clients at once.

I assume you've seen https://webtorrent.io/ ?

- Optimize user experience: use insights to refine and improve your app’s usability.

Interested? For more details, you can check out the GitHub repo [0] or documentation [1]:

[0] https://github.com/openreplay/openreplay or documentation

[1] https://docs.openreplay.com/en/rn-sdk/

Hey HN,

For anyone who uses session replay tools to debug, monitor, or analyze user journeys, this feature might come in handy. OpenReplay — the self-hosted session replay tool that helps developers troubleshoot web apps faster — now supports tabbed browsing.

*Here's how:*

1. Capture and replay user sessions that span across multiple browser tabs, all within a single recording.

2. OpenReplay's tracker communicates across browser tabs, ensuring accurate tracking of each tab, even when duplicated or opened with `window.open` without `_blank`.

3. With "co-browsing", you can watch and support users in real-time and see how they navigate across multiple tabs of your app.

*Why it’s important?*

1. This feature is convenient for developers as it allows them to easily identify bugs by reviewing a complete session in one replay, rather than having to reference multiple recordings.

2. It provides a deeper understanding of the user journey and interactions across multiple tabs in your web app, helping in the comprehension of complex user behaviors and paths.

3. It provides accurate feedback on user tab actions such as opening, switching, and closing tabs, assisting in UX/UI improvements.

Interested? For more details, you can check out the GitHub repo at https://github.com/openreplay/openreplay.

You could maybe get in a scenario where a company rather sneakily changes their license without proper announcement to make usage non-open and billable, but that's pretty rare and bad behavior and that underhandedness may bite them back if it goes to court (I am not a lawyer). That said, it can happen. As an example, see this discussion I opened where the project switched licenses and the maintainers thought it was enough to only really announce this within a 1 hour YouTube video (Rather than their blog or update notes).

OpenReplay would not be typically be considered open source. (Which I have raised with them and have since been blocked from their repos).

How does it compare to OpenReplay ?

> Before deciding on ClickHouse, we were planning to use OpenSearch

You should have tried Quickwit :)

Anyway, sounds like a great project, best of luck!

[1] https://github.com/openreplay/openreplay

[2] https://github.com/quickwit-oss/quickwit

I would disagree with OpenReplay being open source, as I raised with them back in July (I've also since been blocked from their GitHub org for opening that discussion).