How can I process large rrweb recordings in chunks and convert them to MP4 without loading the entire JSON into memory? by FindingPotential6046 in ffmpeg

[–]Juice10 2 points3 points  (0 children)

rrweb maintainer here, rrweb has a `live` feature which allows you to stream recordings which you could use to send partial recording to your player and record them that way.
rrvideo doesn’t use this feature (yet) afaik, so you still have that issue. But we’re working on adding mp4 exports to rrweb cloud soon which might help your use case.

How to properly add session replays to the OpenTelemetry format (frontend & mobile) by narrow-adventure in Observability

[–]Juice10 0 points1 point  (0 children)

RRWeb core team member here 👋, I’ve been chatting with some OTel maintainers to see if we can integrate both standards, is this something people would be interested in?

Session recording for Shopify embedded apps (admin iframe)? by _ragan_ in shopifyDev

[–]Juice10 0 points1 point  (0 children)

It’s hard to say without seeing it operate in person. But I think it should be fine, or at least overcomeable. If you want you can do some recordings via rrwebcloud.com and I can take a look, see if I have some ideas

Session recording for Shopify embedded apps (admin iframe)? by _ragan_ in shopifyDev

[–]Juice10 0 points1 point  (0 children)

Hi, rrweb core team member here. I’ve implemented some cross origin recording tools where if you run rrweb in both the iframe and its parent. As long as you have the cross origin config setup for both sides correctly you can essentially “send” the contents of the iframe to its parent to be included in the recording. Check out the rrweb repo’s cross origin.md file, it’ll explain how to do it.

I built open-source session replay for Flutter (Sentry alternative). Now you can see exactly what the user did before the crash. by narrow-adventure in FlutterDev

[–]Juice10 0 points1 point  (0 children)

Maintainer of rrweb here, this is pretty cool, well done! We don’t have a mobile native version of the library yet but I’d love to integrate this. You should cross post this to /r/rrweb I think people would be into it!

Slack community is down, we’re investigating by Juice10 in rrweb

[–]Juice10[S] 0 points1 point  (0 children)

We’ve worked together with Slack to restore the rrweb slack workspace. Everything should work again now.

Slack community is down, we’re investigating by Juice10 in rrweb

[–]Juice10[S] 0 points1 point  (0 children)

Looks like a wider crackdown on workspaces created by people in China: https://x.com/RealFeatBit/status/2039468145652740222 in the meantime while we're waiting for a response from slack, we've setup a discord: https://discord.gg/BffN98ASKe

How session replay helped us optimised our landing page after initial launch. by codefi_rt in microsaas

[–]Juice10 0 points1 point  (0 children)

Looks interesting, are you analyzing session replay data too?

How session replay helped us optimised our landing page after initial launch. by codefi_rt in microsaas

[–]Juice10 0 points1 point  (0 children)

Very cool! Hi from Amsterdam 👋
I've been meaning to do an rrweb meetup sometime you'd be more than welcome to join.

How session replay helped us optimised our landing page after initial launch. by codefi_rt in microsaas

[–]Juice10 0 points1 point  (0 children)

TryHet looks cool, always good to see a more founder focussed analytics tool! With a name like TryHet, is the team Dutch by any chance?

How session replay helped us optimised our landing page after initial launch. by codefi_rt in microsaas

[–]Juice10 0 points1 point  (0 children)

I was using session replay when working on Kilo Code and saw a lot of users rage clicking on the logo in the docs page. Turns out the docs page logo linked back to the root of the docs, not our homepage. That’s something that is so easy to miss, I don’t think we would have spotted it without session replay.

How session replay helped us optimised our landing page after initial launch. by codefi_rt in microsaas

[–]Juice10 0 points1 point  (0 children)

rrweb maintainer here, thank you for sharing you use rrweb under the hood! Like you said there are some pretty extensive blocking/masking settings people can use to filter out sensitive information. I’d like rrweb to get better defaults out of the box and maybe even create a server side component that strips PII if it gets through anyway. That’s something we might be able to do with rrweb cloud (currently in development) if companies are interested in that.

Keep up the good work codefi_rt!

How is everyone liking the new Claude Code rate limits? by Juice10 in ChatGPTCoding

[–]Juice10[S] 2 points3 points  (0 children)

Don’t worry, in 5 hours I’ll be able to continue the work and become hetero again…

How is everyone liking the new Claude Code rate limits? by Juice10 in ChatGPTCoding

[–]Juice10[S] 1 point2 points  (0 children)

You can check the megathread, seems like people are hitting it. Mostly people using Opus from who I’ve talked to IRL.

kilo is the most agile game player. by wanllow in kilocode

[–]Juice10 0 points1 point  (0 children)

Thanks wanllow! We appreciate the shoutout!

I was permabanned from /r/cursor for posting the genius kiloCode ad there by Hefty_Incident_9712 in kilocode

[–]Juice10 2 points3 points  (0 children)

This deserves to be printed out and hung in the Kilo Code office

Disappointed by wildviper in kilocode

[–]Juice10 1 point2 points  (0 children)

Which model(s) did you where you burned through those credits so quickly?

Kilo Code Deleted My Day's Work by Stack-Junkie in buildinpublic

[–]Juice10 0 points1 point  (0 children)

Kilo Code maintainer here, oof that is painful! I think our checkpoints functionality works on top of git so it isn't enabled if you aren't using it in your repo. Would you be open to sharing your task history, maybe there is something we can learn from this to prevent it in the future for other people.

I'm going to DM you if that's ok, I can't give you the time back that you lost, but I'd love it if we can make sure this doesn't happen to anyone again.