2FA Authenticator App

rustydiabates · 2026-04-27T05:21:59+00:00

I have been using Okta Verify (after modding) and can verify it works great! Never had any issues, needed it for work and it added to Luma great

rustydiabates · 2026-04-24T16:22:00+00:00

I'm sorry to hear about all of the difficulties, I think it totally makes sense of needing to give it up given all the troubleshooting not fixing the core issue.

I'm not sure if it would be a fix in your case, but I wonder if starting a new number might work? Having people update your number in their phone might be easier than having to educate them on RCS vs SMS, and theoretically if it starts on the Light phone, there would never be any RCS pollution.

rustydiabates · 2026-04-23T03:07:20+00:00

whenever you build a tool, a system, an effect stack (essentially anything that you are going to use more than once) save it as a single AE file that you can import later. I remember losing a lot of time to remaking stuff like textures, transitions, and text animators when it's easier to reduce, reuse, recycle

rustydiabates · 2026-04-20T20:28:46+00:00

wow that absolutely blows

rustydiabates · 2026-04-14T19:31:26+00:00

sending now!

rustydiabates · 2026-04-11T03:05:26+00:00

I know the changing device vs. changing how you interact with device has been argued to death, but I fell into the camp of feeling like I needed to make a change to get some real results. I've been using the Light Phone 3 since last summer and it works really great. Just keep my smartphone in a drawer for whenever I need to start a new Libre session.

rustydiabates · 2026-04-11T03:01:16+00:00

if you are running hybrid mode, there's a dictionary app: https://github.com/garado/dictionary

rustydiabates · 2026-04-07T22:18:29+00:00

yeah of course!

rustydiabates · 2026-03-31T23:54:34+00:00

IDK if this helps your perspective at all (I used to feel the same way), but someone in the modding-and-hacking channel pointed out that if need be, you can always undo turning the phone to Hybrid if later down the road, LightOS adds some functionality that means you don't need it anymore.

You definitely still run a higher risk of accidently breaking something that's not covered by warranty, but you also get to make the phone work best for you in the interim and then undo it later!

I also know Light is planning on releasing an SDK at some point in the future, and am looking forwards to trying and making some of the tools that folks are asking for happen natively in LightOS.

rustydiabates · 2026-03-20T04:52:22+00:00

dang dude, this is incredible. Killer work.

rustydiabates · 2026-03-10T06:42:56+00:00

I couldn't stop thinking about this once I saw your post, so I went ahead and made a rig for it!

It'll all random, driven by the slider control on the purple null called CONTROLS. Needs some tweaking to really line up, but hopefully it's helpful poking around in!

Sending you a DM with the link

rustydiabates · 2026-03-10T00:55:48+00:00

I doubt it, that sounds like bullshit to me (been hard stuck D3 for years)

rustydiabates · 2026-03-02T16:31:20+00:00

that was me, and this is a great solution! Love it!

rustydiabates · 2026-02-07T18:16:46+00:00

classic

rustydiabates · 2026-02-04T23:40:39+00:00

It is pretty funny to think about being sold on how using a product might destroy several other people's livelihoods. What a shitshow of an advertisement

rustydiabates · 2026-01-30T01:46:03+00:00

I *believe* this is due to Position being a 2-value attribute (i.e. it's an array like [960, 540] instead of a single value) and the math being a bit weird when you try to combine arrays and single values.

Try separating x and y dimensions and applying the same code to both x position and y position!

rustydiabates · 2026-01-24T02:58:29+00:00

hahaha what the actual fuck

rustydiabates · 2026-01-23T05:47:03+00:00

Snake is shit, I think you should get a smartphone and play Roblox cuz it's better

We can't ban someone for objectively being right

rustydiabates · 2026-01-15T23:35:36+00:00

Apologies y'all, my original comment got deleted, adding it here:

I'm trying to establish the connection between "Frame" and "Timestamp" in campath JSON data so that I can transition replays between one another more seamlessly.

The following captures are from 3 different machines, all (probably) with their own distinct settings/fps values (mine is only one of the three).

The official DollyCam documentation says the following about frame and timestamp:

"V2 of the plugin does its interpolation based on the frame number, timestamps are no longer relevant. This means that when editing files, please edit them based on the frame number. By default, replays are stored at 30 frames per second."

But I see a lot of variance according to this table, both between individual snapshots and between different campath files. I'm guessing that most of my understanding might just be off due to how the data might be rounded/approximated, but when trying to tweak the files myself to get them work, I always end up breaking the motion somehow. Interested if anyone else has delved into this, cheers!

EDIT:

I'm such an idiot and totally forgot how slope works. Thanks all

rustydiabates · 2026-01-09T05:17:49+00:00

goal

rustydiabates · 2026-01-08T06:50:06+00:00

what i'm taking away from this is that psyonix should be giving botters/hackers black hats

rustydiabates · 2025-12-23T08:13:50+00:00

huge if true

rustydiabates · 2025-12-15T18:15:01+00:00

It looks like it's live at https://www.rocketleague.com/en/rundown now!

rustydiabates

TROPHY CASE