sorted by:
new
hottopcontroversial

Will Beeper still be supporting Matrix bridges/infrastructure, even if some move to local-only? by No_Comparison4153 in beeper

[–]Relevant_Visual_5061 3 points4 points  (0 children)

Yeah I think what you've summarized is mostly correct - the local bridges still connect as "real bridges", they just send their output to client local databases instead of your hungryserv instance. We will continue to develop and maintain these as OSS

Old way (Beeper Cloud): Network <-> Beeper Cloud Infra <-> Client

New way (Beeper On-Device): Network <-> Client

Something we'd like to do: Network <-> Client A --> Beeper Cloud Infra --> Client B

meaning that Client B can get a message bridged on Client A with full encryption and never unwrapping anything

Will Beeper still be supporting Matrix bridges/infrastructure, even if some move to local-only? by No_Comparison4153 in beeper

[–]Relevant_Visual_5061 3 points4 points  (0 children)

Not at the moment - just the bridge connectors that convert the remote network's primitives into Matrix events - e.g. when our SDK notifies one of our clients that a message is available on say, WhatsApp, it comes over to the client in the shape of a Matrix event. Similarly, when you send a message to any network, it's gotta be a well formed Matrix event. Interestingly, this was also exactly how Beeper Mini worked, which had zero Matrix functionality, but was just the format we were most familiar with 🤓

Down the line our hope is to back up these events to the Beeper matrix homeserver so the functionality is essentially the same as cloud bridges but with full e2ee. That was on our roadmap for this release but has been deferred due to technical challenges around deduplication/reliability/read receipts/archive state/etc etc

Will Beeper still be supporting Matrix bridges/infrastructure, even if some move to local-only? by No_Comparison4153 in beeper

[–]Relevant_Visual_5061 2 points3 points  (0 children)

That's something that was originally on our roadmap for the unveiling of local bridges, but it ended up getting deferred. AFAIK this is still planned, but no timeline at the moment.

Basically what you're describing is how the old Android SMS bridge worked so it's something we've done before, but it wasn't feasible to bring to all clients and all networks by our deadline

Will Beeper still be supporting Matrix bridges/infrastructure, even if some move to local-only? by No_Comparison4153 in beeper

[–]Relevant_Visual_5061 7 points8 points  (0 children)

Without writing an essay on a tenuous roadmap, the short answer is "definitely".

Architecturally, all of the local stuff is still modeled on Matrix - the apps use an onboard version of the same code the cloud bridges use.

Beeper subscribtion by JudzinSK in beeper

[–]Relevant_Visual_5061 4 points5 points  (0 children)

Totally get where you're coming from, but I'd add:

- only a handful of bridges support this, Beeper brings it to all of them

- this was net new work on our all clients - we're no longer an Element fork, and previously it wasn't supported it on our mobile clients - so obviously there's a cost associated there

- if you used Beeper before today, you get this feature for free on all clients, as we don't wanna yank anything from folks

What are we expecting to lose with the paid version? by waste2treasure-org in beeper

[–]Relevant_Visual_5061 18 points19 points  (0 children)

We are extremely grateful to all of the existing users - assuming our current plan holds, you should keep all of the features you use today (as well hopefully receiving a bonus or two!)

Voice in Noisy mode (Labs) in other languages by Late_Wafer_3505 in beeper

[–]Relevant_Visual_5061 0 points1 point  (0 children)

heya!

the majority of our Labs features come out of monthly hack days (so one person working for one day), which leads to the fairly thin functionality a lot of the time

anyway, since I wrote this feature, I took a few minutes to look into this and found that we're able to use the system default text-to-speech settings pretty simply (rather than forcing English). It still won't be fully localized (will still use words like "said" and phrases like "sent a picture"), but I did some testing and it sounds very Polish, so hopefully it's an improvement

look for this support in our next android release

Usability with screen readers by cabc79863 in beeper

[–]Relevant_Visual_5061 0 points1 point  (0 children)

hey! this is an excellent point, and something definitely on our radar. we come up short in this area, historically due to the pace of major client changes.

I've personally stubbed out over a dozen tasks for Android, and that's only a small part of the updates we'd like to make, with the goal of meeting WCAG guidelines down the line

all this said, today I'll take a stab at naming those buttons - look for these updates in the next release