Getting Google to care enough to fix that problem was harder and slower than a technical solution.
2,159 karma · joined August 4, 2011
Getting Google to care enough to fix that problem was harder and slower than a technical solution.
I had originally planned to make it accessible via bluetooth but when I realised the phone shell was thick brass, I decided to leave it as a 3.5mm jack
It's not about the colour of the message, it's what it signifies: this is an insecure conversation that is not end-to-end encrypted. To me it signals "switch to whatsapp/signal"
Today green means SMS, which also means that deliverability can be unreliable (in the past I've seen SMSes send and never arrive, arrive multiple times, or arrive hours late), and delivery notification is limited and unreliable. Same with tapbacks, and that voice/image/video involves MMS (which is bad, and in many countries carries per-message fees).
P.S. the incoming message bubble is black-on-grey, the same as all incoming messages no matter the medium - it's unencrypted outgoing messages that get a green bubble
It's generally a good idea to drop vowels for this reason.
Good luck with whatever approach you choose!
1: PEP 668 https://peps.python.org/pep-0668/
2: https://packaging.python.org/en/latest/specifications/extern...
You do not require a TV license if you have a TV but do not use it to watch live television (e.g. using it for YouTube/Netflix apps)
Always up-to-date and succinct auto-generated LLM-generated 'documentation' that describes a method in terms of who calls it (and perhaps why?) and the behaviour of the whole deep call graph inside the function seems like something that could be quite useful when looking at a method that doesn't have any human written documentation available, and isn't obvious... but it shouldn't masquerade as if it's actual API documentation that describes a durable contract.
If this synthesised analysis could flag incompatibilities between the contract described in API documentation and the actual code behaviour that could be useful (similar to what tools do today for nullable/non-nullable-annotated args/returns, except on fuzzier natural language descriptions of higher level behaviours). That seems like a much harder reasoning problem for the LLM to solve, though.
P.S. have you tried testing what happens when you clearly describe what you want? The prompt you're using is really low quality - more like a google search. If you asked me a question like that I'd tell you to clearly explain what it is you want.
If you have multiple files with names like `index.html.1`, `index.html.2`, etc., and you want to rename them to `image_1.png`, `image_2.png`, and so on, using Zsh, you can accomplish this with a simple loop and the `mv` command.
Here is how you could do it in a Zsh terminal:
```zsh
autoload -U zmv
zmv -W 'index.html.*' 'image_*.png'
```
The `autoload -U zmv` command loads the `zmv` function, which is a powerful utility in Zsh for batch renaming files. The `-W` option tells `zmv` to use wildcard patterns for matching and renaming files.
In the `zmv` command:
- `'index.html.*'` is the pattern to match. It matches any file that starts with `index.html.` followed by any characters.
- `'image_*.png'` is the replacement pattern. The asterisk `*` in the replacement pattern corresponds to the `*` in the match pattern, so each matched number after `index.html.` gets placed where the `*` is in `image_*.png`.
**Important:** Always make sureActually, I'd hope this is already happening regularly anyway so they can cut off any terminals captured by the enemy
Asking out of interest, because I don't know much about medical glues, and I often just use a little dab of superglue on cracked skin and haven't experienced any burns from it (I have, however, experienced a superglue burn while crafting - for anyone who doesn't know: don't use cotton to wipe off excess superglue, it will rapidly polymerise and heat up, and it'll stick to your skin while it's doing it)
1. Existing UK homes use radiators that would need to be replaced with larger radiators with an air-to-water heat pump, due to the water not being as hot as a traditional radiator system. Some of this is cost (replacing radiators), some of this is simply not having the space - many radiators are installed below windows so there isn't much scope to increase their size
2. Replacing radiators with an air-to-air system in each room is too expensive (especially since older homes often use solid brick/concrete for internal walls), as well as a large number of terraced houses with limited space for external piping/units.
3. Our mild climate (as well as housing stock age -- and, I'm betting, good historical access to local fossil fuels) means UK homes are very poorly insulated, and with our humid climate can have humidity + mould issues if retrofitted with insulation that reduces drafts.
They should, of course, have given a clear timeline for deletion at that point, but does he seriously expect other people to believe he was naive enough to think Google would continue to store his data forever after they withdrew the unlimited service he was using?
I'm no fan of Google, and I agree with you that a good service would have offered an at-or-slightly-above-cost data export for that volume of data... but he's deliberately misrepresenting the situation here (either that or is painfully naive)
Edit: as somebody else pointed out downthread, he also would have received numerous e-mails throughout 2022 telling him that the unlimited service was being shuttered
Given PostNord's less than stellar efficiency, this could be entirely unintentional on their part :-)
However, I was actually wrong more generally because Apple does have push notification type for this, Background Updates[1] are permitted to run invisibly. They say not to try sending more than 2-3 per hour, and that "the system may throttle the delivery of background notifications if the total number becomes excessive" - which sounds like you're permitted some unspecified small number between app launches.
These notifications seem to only be able to send a single boolean flag, so it doesn't seem like an awfully viable way of implementing a fixed rate message system (especially because you'd also want to be sending messages out on that same fixed rate to frustrate analysis)
1: https://developer.apple.com/documentation/usernotifications/...
If you're trying to hide from that type of attack you need to send a fixed rate stream of messages (most of which are dummy messages, except the occasional message containing genuine content -- like number stations). Furthermore, every point in the chain also needs to avoid revealing which messages are genuine (by fetching the encrypted message from the server when it receives a genuine notification, you're giving data away).
The operator of the app could send messages at fixed intervals to make it more difficult to correlate the messages (more samples required to have confidence in the recipient). If they send dummy notifications they'd probably fall foul of Apple/Google's constraints around invisible-to-the-user notifications (I know Apple prohibits them, I assume Google does as well)
I can't see that frustrating this type of attack would be interesting to Apple/Google: it would push up power & radio bandwidth requirements for everybody pretty significantly.
Same - although I have experienced an interesting extension of this: HomePods now have alarm detection (the intention being to detect a smoke/burglar alarm). It is also triggered when the fridge is left open, leading to everybody in the household getting a critical alert (which ignores silent mode).
I think we just have to embrace the fact that any text could be wholly/partially LLM generated. An LLM could be asked to introduce errors (or a human could edit the output, either to purposefully introduce errors, or naturally introduce errors as part of their process). We should focus on:
1. Developing our skills to verify people's claims (which has always been important)
2. Trying to understand the motivations/agenda behind the text (which I reckon is even more important still)
The above two steps insulate you from a wide range of propaganda/trickery, and are the sorts of things we should have been focusing on in schools for decades already.
Does anybody have any more info on this?
Also, assuming RE2 works like other engines, it also couldn't convert to a partial match without the .* prefix+suffix even if .* matched any char, because you might then ask for capture group 0