Actually; (basically) SIP over (basically) IPSec sounds pretty correct. Wish the dense technical manuals I read had explained it that way; makes a lot more sense to me as a Net Admin type of IT person.

I do remember reading that the protocol was basically encapsulated. Dunno about any encryption; probably there’s not any at the IPSec level. I do know that the SIMs themselves probably contain certs that have some value; I just don’t know if they handle any encryption or if they’re just lightweight little numbers for authentication only.

If I’m understanding how 'WiFi Calling" works; it’s still “identifying you” to the cell provider the same way; via your SIM. The only difference is they don’t get an exact location because you’re not using any cell towers typically.

I do suspect SIMs and eSIMs are still doing all the heavy cryptographic signing done on a typical phone network though…they’re just not screaming your IMEI/IMSI all over open or even encrypted airwaves; nor is a WiFI signal triangulate-able typically due to it’s short range.

They certainly make it easier to do so; by making it a switch you can toggle; which allows you to generate an identity; or choose not to and roll with the identity they’ve already seen.

Agreed.

Without concepts of privacy; things will soon fall into fascism.

(People can’t DM you)

This is false. However, you must generate an “identifier / group / channel” for them and share that link out-of-band to them." Basically it means nobody can slide into your DMs unless you yourself consent to it and forge a connection with them to do so. It does offer a way to invite other users to chat; but the other user must consent as well…which makes it far safer usually.

Keybase is better than Signal. You may not like it’s current owners but it still works, still functions, and can be used to chat privately. It’s entirely OSS on the client side; and server-side software isn’t provided; but with an open Client; it’s likely trivial to reverse and re-implement your own. (Keybase itself doesn’t provide their server code; it’s private due to abuse constraints)

Keybase is End to End Encrypted. It may not be as “feature rich” but all features are private.

I’m not sure if it’s indev anymore though; and it does allow you to be as public or as private as you’d like to be about your identity.

In general; I think even 2 billion is too much. Nobody needs that much money.

At best; I think no one should be able to have more than about 500 Million. You get one house, and one car for each adult family member if you’re married with non-adult kids. Adult kids don’t add uncounted vehicles; they have their own limit. Anything that is seaworthy or airworthy counts as about as much “Wealth” as you initially spent on it minus a reasonable depreciation rate yearly as determined by the market, so no buying a thing and having it lose 30% of it’s value the moment you drive it off the lot after buying it.

Additionally; to block too many shenanigans; wealth added by any property that is bought sticks; 3 years at minimum. This prevents people from storing too much excess in property and shell-gaming it. A company you own or have stake in cannot lend (in a long term) or gift you property in excess of 1% to 10% the wealth limit. (Depending on what the thing is). Companies may also not hold property or money in lieu of an individual personally; everything the company owns must have a global company function; and not personally benefit one or more people only. (Basically no executive-only or owner-only Jets; everyone from the tiniest manager on up should have access to it if there’s a business reason for it)

It occurs to me that adding a visual watermark might actually serve to obscure a visual watermarking scheme that is otherwise invisible by providing data that scrambles or breaks the watermark decoder itself.

Audio watermarks can be distorted in any number of ways; and it could be that some of the wildly poor audio quality in most cam-rips is probably the only way you can defeat the watermark; by using a LQ microphone and encoding the audio to a very limited bitrate and then re-upsampling; to defeat any subtle alterations a digital watermark might make to the audio waveform.

Watermarks are only an issue in-as-much as it is used to trace down which copy was leaked.

With modern digital projection systems; you don’t get a reel of film; you get a briefcase of [SS/HD]Ds containing the raw, encrypted, footage. The digital projection system will decrypt using provided keys. There’s no output except the standard ones for the theatre projectors and sound systems…so capturing the output is difficult.

If you do intercept the signal; the projection system might detect it; and refuse playback or wipe the decryption keys. Watermarking is also a danger; since your theater can get identified as the leak source and sued.

Now we wait for someone to build an absolutely wonderful chat app on top of this wonderful bit of PoC code…

I genuinely hope someone does. Imagine what this could do if this was routed over Tor using Private Services.

Run this over that; and you’d have a bullet-proof text chat. Wrap a nice GUI client around all of that and you have a proper secure, anonymous messenger with no problems. With a little more build-out; you could even implement the Matrix protocol over this wire-line and basically have full inter-federation and moderation over a secure wire protocol; allowing for complete privacy and client integration.

TL;DR: Matrix over PQChat over Tor. Think about it. A Post-Quantum Dark-Matrix web.

Ah; I don’t use Chinese branded phones at all. Never have.

Phones in the US market do not usually have them, unless they’re Samsung branded, and since I don’t include Chinese made phones in that “group”, what I’m saying is true for the US.

Uh, No. Hell to the fucking no. Bring back SD expansion. Treat it like the data storage device it was.

Your beefs with Google are misplaced; because they were trying to mess with what folders were used; and with trying to protect user privacy because applications were misusing storage to violate their user’s privacy.

• Losing SD Expansion sucks; they should bring this back. Only reason they stopped this is greed.
• Yet another Nice-To-Have that is gone; but I’ve never seen any phones that weren’t Samsung with this. This one doesn’t really even affect waterproofing; or phone size so they have no excuse.
• I certainly miss this one; but the FM Radio was present back on my 2020 Moto G6 Power. It was present on my 2020 Moto Edge. This one got stolen from us because we lost the 3.5mm Jack too…they used the wire from your wired headphones as an FM Antenna lead.
• This is nice; but I ended up having to root my Nexus 6 to make this work properly and use all the colors the LED could perform. I don’t really miss it with Bezel-less phones.
• I hate that bootloaders are frequently locked; but it’s been less necessary to root Android as it’s improved over the years. There are still a few pain points; but not quite as many that require root.
• This is another case of greed. There’s no reason why we shouldn’t have removable batteries for phones that aren’t IP67 or higher. If it ain’t waterproof; there’s no reason to seal the battery in…and replaceable batteries is a benefit when they accidentally ship units that become “spicy pillows” when the batteries swell due to bad batteries. It also simplifies disposal of phones; which don’t need disassembly if they’ve got a removable battery.

Can it? Maybe. It’s not impossible; but it isn’t practical and most ISPs limit their shenanigans to grabbing your unencrypted DNS requests.

Will it? Probably no; aside from the previously mentioned DNS redirections; they’re not interested in most people’s packets, only in how many they deliver.

Should you care? I won’t tell you not to take precaution, but I do urge you to consider your threat model carefully and consider the tradeoffs. When Security & Privacy goes up, Convenience and Functionality WILL go down. Balance your needs. Don’t put yourself in a state of Privacy fatigue.

Are there easy fixes? Maybe. I think a VPN or using Tor would solve your concerns here anyways; it’s not required that your modem be running OSS that you can control. If you can achieve it; that’s still good for you; but it’s not something to be sweating if your modem isn’t capable and your invasive ISP is the only effective option.

I’m not accounting for State laws; which may in fact be stricter. I’m talking about Federal Laws which might not explicitly forbid such things; so long as they’re done in an actually safe manner by professionals.

But, as I said before, if the DEA believes it has the power to stop that none-the-less; that’s what they will do, without respect to if the law is actually legally unclear or borderline. Unfortunately many pharmaceutical places don’t care to invite the wrath of the DEA; even if what they’re doing could be considered permissible; so long as they do not synthesize an exact drug that the Feds specifically name as a controlled substance.

Again; IANAL either. But I do think there’s a lot of room for small compounding pharmacies to synthesize various drugs to meet a patient’s needs quickly while waiting for proper shipments to arrive. There’s lots of compounds that are life-sustaining that do not fall under the DEA banner of authority.

Depending on how Vyvanse is Scheduled; it might be legal to privately make. If it’s not scheduled like a standard amphetamine; the DEA is powerless.

I have a sneaking suspicion it’s not illegal to compound this stuff. But IANAL; and it doesn’t matter if the DEA thinks it is and will hassle anyone trying.

I firmly think this would be a boon for many people; owning one of these is likely a lifeline that even small town physicians could utilize to dispense drugs freely or cheaply to patients in need.

This is something that I think small-town pharmacies could use to create compounds in cases of drug shortages. I think tools and programs and small labs like what are discussed in the article are a positive force for good; and that they should be not only allowed, but encouraged, for many drugs that are expensive, unavailable to someone in need and can be readily synthesized safely with a basic college level of chemistry training by someone in a pharmacy.

I think the potential risks and downsides are small right now; and I think more of it should be encouraged gently so that we can find out quickly what the flaws and limitations are so that we can put regulatory guardrails around it so that people do not harm themselves.

The rot is deep. Avoiding it often requires you to become a hermit.

You try convincing your tech unsavvy friends to change services, your boss to let you use linux, and all your favorite communities not to use Discord, Google and YouTube. Last of all; good luck finding that one obscure widget you need right now to make something work without using Amazon.

I promise all of the above are harder than they sound. It shouldn’t be harder; but it is.

I’m certainly concerned that now that this software has been covered in PopSci; that it will certainly suffer a needless onslaught of DMCA and other lawsuit-related shenanigans. >_>

In aggregate; 5 instances, less than 5 communities, and more than 69, nice, blocked users.

I don’t mess around. I don’t hesitate to block people who argue needlessly, make my experience less informational or less entertaining, troll, or disregard arguments made in foundational logic to push a point of view or ‘win the argument’. Similarly my instance ignores downvotes and does not display them; as with most platforms which behave similarly to reddit; they simply do not work outside of your personal, local account, local instance, user-sorting context.