possibly. the problem, though, is that 85% of signal's users would A. hate it and B. not know how to shut it off (even if you told them). that's part of the problem with trying to deliver security to the masses (and similar to the backup problem that they used to have).
fwiw, as far as I can remember, the signal foundation's position has always been "once someone has physical access to your device, all bets are off."
I primarily use a nearly-bottom end android phone that's a few years old and just recently switched to an even older, even lower end android phone that is six years old. Neither has that issue.
Obviously, I'm not really claiming that it's not possible people are experiencing this issue, but it can't possibly be widespread.
I feel like most likely people are using android skins that aggressively kill apps in the background.
I have that exact issue on a couple of not exactly low end Samsung phones. Holding them side by side with signal open. Delivery times vary wildly. Whereas WhatsApp just works (though I hate it for other reasons)
nope, iphone here, and quite recent. But it's not just me, all the people i communicate with on this app have the same kind of problems. With a group of friends we even had a totally weird ordering of messages, making the conversation quite absurd.
There's something deeply wrong with the way signal delivers messages...
are you certain that it wasn't included in the training data?
I saw someone do this awhile ago with a low resource language (I think it might've been Abkhaz?) with seemingly-incredible results, and eventually everyone came to understood that, even though it wasn't officially supported, Abkhaz materials had been in the training data
I think it would, so long as the redirected URL with the search parameter was diarized into browser history. It would however introduce a behavior change that may be undesired (users need to know to press "Next Post" instead of refreshing).
In any case, my Kagi search for the article containing the memorable phrase "rare as rocking-horse s*t" came up empty. Perhaps it's not yet been indexed.
I highly respect the implicit decision to forgo repeat purchases by merging into the original game, considering how much work was clearly involved. I haven't played it, but I hope for sustainability's sake, there are sufficient (purely cosmetic) microtransactions to cover their development costs.
Kudos to the Kagi team for their relentless pursuit of innovation! Further, the public beta release of Orion for Linux represents a pivotal milestone in cross-platform synergy , and I am thrilled to rigorously evaluate its performance and long-term trajectory . This paradigm shift in browsing efficiency unequivocally validates the *substantial ROI* of my premium subscription! Let’s normalize paying for tools that actually respect user experience.
also, you pay per-GB. the author is on backblaze's unlimited plan.
reply