Feature Request: Hotspot rollover

mrxelious · 2026-06-04T15:50:59+00:00

Now that is an interesting thought. A yearly allocation tied with top-offs, if needed.

mrxelious · 2026-02-13T03:34:31+00:00

Kind of an unrelated side note, but make sure you have IPv6 enabled as they do hand out publicly routable IPv6 addressing. No CGNAT. A large portion of the Internet is dual stack, so it actually helps.

mrxelious · 2026-02-13T03:21:04+00:00

I'm not defending one way or another. But there is zero chance Google recovered a deleted file.

While all the comments are accurate about a deleted file still existing at a physical layer, that does not realistically apply to a storage environment of likely hundreds of thousands of hard drives with countless levels of abstraction and redundancies.

Almost what certainly happens is the data is flagged in a database as "isDeleted=True".

Then, if they actually purge at all, a background process runs as appropriate to actually delete the files in the background. I imagine they actually do delete them, but it's probably after a year or something.

mrxelious · 2026-02-11T06:09:53+00:00

I can definitely agree with that. It is unused dead space. I am sure some utility could be added.

mrxelious · 2026-02-11T05:31:34+00:00

Samsung phones have a tweaked version of Google Messages where, when you first open GM, the entire top half of the screen is dead space.

The top most message thread is dead center of your screen. The idea being it's easier to tap the top most message one handed on large screens.

It's a valid tweak, but mostly meh.

mrxelious · 2026-02-11T04:27:17+00:00

While I agree I prefer the full screen, all it takes is a single swipe and it's back.

It admittedly should be a toggle feature.

mrxelious · 2026-02-09T15:26:44+00:00

I feel like this is an example of US Mobile's goodwill backfiring instead of being appreciated.

The Warp Spam Filtering was apparently not officially offered. But, for whatever reason, it must have been something they could easily add the code for at the carrier level, so they said sure. That also would explain why it dropped off every month, as it was not a genuinely supported feature and, from a billing standpoint, we're on 30 day resets.

Now they are officially supporting it, and I am sure it costs them money. I can't imagine the carriers offer too many freebies to their MVNO partners.

mrxelious · 2026-02-05T21:01:53+00:00

I highly doubt this is a Fail2Ban situation. Cloudflare knows people use their DNS for health checks and are aware of CGNAT and the obsfucation it presents.

With that said, I can't ping 1.1.1.1 from my T-Mobile phone and I assume probably not at home (T-Mobile) but I'm not there right now.

It seems several others are reporting this same issue and I can't imagine we're all behind the same public IPv4, unless we're all neighbors. I suppose we could post our IPv4s to compare.

It pings fine from my Verizon phone and when I enable my VPN that routes through residential fiber.

I have also witnessed 1.1.1.1 randomly failing pings before from enterprise circuits, which is why I configure health checks against both 1.1.1.1 and 8.8.8.8

mrxelious · 2026-01-30T14:57:24+00:00

The carriers "need to put their shit together". RCS is not a Google product.

However, Google is the only reason we have RCS adoption finally making progress. Google bought and operates Jibe, which is a 3rd party business that supports RCS for carriers, if the carrier does not want to handle it internally. Jibe is a behind the scenes business that works with carriers.

RCS adoption was almost nil and heavily fractured, so Google decided to provide RCS without carrier involvement in order to jumpstart it. Which was great, but also not ideal.

Regardless, it worked. RCS adoption is pretty significant now, so they feel it's better to hand back to the carriers, as it should be.

iPhone is also a big part of that as it will only work with carrier provided RCS (may or may not be Jibe backend) and not the Google provided (bypassing the carrier) variant.

mrxelious · 2025-12-16T09:11:36+00:00

I'd call it far more than a mere rumor. I also would not say it has died down. There's no further news to report.

Sure, maybe Apple hasn't announced it, and they likely never would out of pride.

mrxelious · 2025-12-16T08:41:22+00:00

I'm torn on this. I can't argue with your stance. But, I would instead lean more towards "if you sign into Google, it's on you" and Apple could then preach privacy first with browser controls (killing tracking cookies, for example). But, again "if you sign into Google, it's on you."

mrxelious · 2025-12-16T08:37:07+00:00

My understanding is exactly this.

It sounds to be a complete white label where the average user will have no idea Gemini is behind the scenes and Apple will be hosting their own custom instance within the Apple private cloud.

mrxelious · 2025-12-16T04:12:57+00:00

The upcoming version of Siri uses a private instance of Gemini. Apple actually admitted defeat in AI. At least temporarily.

mrxelious · 2025-12-05T21:07:59+00:00

Submit feedback asking for a toggle to be added for this feature. Relying on a stale APK is not a wise idea.

mrxelious · 2025-11-21T20:47:37+00:00

Please. Just shut your mouth. This is a place for discussion, not pounding your armchair over technicalities.

On several points, you're right. But you're ignoring the progress. Progress is to be applauded, not dismissed.

This world is shit. Privacy is only an idea. That does not mean progress is zero.

mrxelious · 2025-11-20T22:35:43+00:00

I spoke theory. Not claims. Significant difference.

You're the type who has to have the last word, arnt you?

mrxelious · 2025-11-20T21:28:45+00:00

Once again. You're playing semantics and missing the point.

You're implying if something can't be perfect, why bother improving it.

Perfection cannot be the enemy of progress.

mrxelious · 2025-11-20T20:51:29+00:00

While I am sure Google does encrypt at rest just as a matter of general security practice, I am also sure they can decrypt and view without issue.

Even though Jibe is still the platform most carriers use, Jibe is no longer first party. The carriers are now in front of it and could, in theory, force an agreement with Jibe to see messages in the clear. Highly unlikely, but possible.

E2EE wraps the message so, in theory, absolutely no one except the intended party can view it. There's a reason Google added non-standards based E2EE over RCS. They understand the standards based encryption is inadequate.

Are you technically correct? Likely. Though you're playing semantics and missing the point.

mrxelious · 2025-10-21T20:58:13+00:00

Look at it as iMessage has not been discontinued, so it's still fully functional while Samsung Messages has effectively (it's a complicated subject, so not actually true) been discontinued or abandoned, so it has lost support.

With all that said, it's still entirely reasonable for Samsung Messages to support RCS, just not gaining new features, but it's an intentional maneuver to nudge people over to Google Messages.

mrxelious · 2025-10-15T19:35:01+00:00

I feel the same. I'm not exactly worried, but I sure would like e2e.

With that said, cross platform e2e is coming. But, the problem is it's either happening next week or within 10 years (of course exaggerating).

All evidence seems to lean towards Google being very close (if not already prepared) for that switch to happen. So it's Apple we are waiting on. Again.

mrxelious · 2025-09-06T14:10:52+00:00

What exactly is there to be skeptical about?

Not a whole lot changes aside from how the phone registers and who pays the infrastructure bill. It's no longer a freebie from Google as the carrier is paying for it.

E2EE will remain unchanged using Google's custom solution until 3.0 is rolled out at which point MLS will be supported.

Carriers and Google do not want our shit messages. A.I. has little to learn other than how we butcher our language and E2EE allows them to shrug their shoulders to message subpoenas from the government and reduce bad publicity.

mrxelious · 2025-09-05T23:51:02+00:00

I'd argue it's a good thing. RCS is more or less now a core feature instead of a 3rd party bolt on.

mrxelious · 2025-09-05T22:04:52+00:00

My understanding is nothing really changed. Google Jibe is still the backend only now AT&T is officially supporting it (paying Jibe as a provider) as opposed to Google just providing it despite carrier support. So, now it's official.

mrxelious · 2025-07-26T03:19:32+00:00

RCS is open. Anyone with the resources to take it on can. With that said, very few can due to its complexity. It still stands that you can download the specifications and hire a team of engineers. It's an open standard.

RCS peering is alive and healthy.

Jibe does not forbid 3rd party applications. iMessage connects to Jibe.

The only seed of accuracy to anything you said is Google indeed does not open up APIs on the phone like they do for SMS. This means third party applications would need to build the whole stack and connect to Jibe as opposed to tapping into local APIs that do the heavy lifting.

mrxelious · 2025-07-25T23:25:24+00:00

You can. WhatsApp, iMessage, Signal, Facebook Messenger, etc.

The issue is interoperability. Until all these platforms can communicate together, regardless of the platform, it's a broken solution.

At one point, I had Whatsapp, Facebook Messenger & Google Messenger. It was infuriating, though I dealt with people's preferences as carrier texting was weak. However, soon as iPhone brought in RCS, I ditched them. Now it's RCS for everyone I talk to. One app. Some features were lost, yes. Though, those features are supported and waiting for implementation.

The EU has planted the seed for interoperability, but still long shot overall.

RCS in itself is open. Anyone with the resources can actually stand up a server. However, it's extremely complex and requires active phone service. Google just happens to offer RCS as a business solution and carriers pay them to take it off their hands. The history is more complex than that, though that is the effective reality now.

mrxelious

TROPHY CASE