yeah. rat lungworm.

a private DNS server that only has records from your local services would at least prevent apps from reaching out as long as they aren’t smart enough to fall back to an IP address if DNS fails.

Yes, this. It’s important that your local DNS server does not even forward queries from the isolated subnet to external DNS, because these queries (and responses) can contain information. (“DNS tunneling”).

What will this mean for Lemmy instances? XMPP servers? Email servers?

What if a 15 year old runs their own personal Mastodon server? LoL this is gonna be yet another entertaining Australian government shitshow.

I think a lot of comments have missed that ntfy.sh does not use UnifiedPush, the ntfy server is a UnifiedPush provider and the ntfy app is a UnifiedPush distributor.

Regarding encryption of the push message, from https://unifiedpush.org/developers/spec/android/ :

Push message: This is an array of bytes (ByteArray) sent by the application server to the push server. The distributor sends this message to the end user application. It MUST be the raw POST data received by the push server (or the rewrite proxy if present). The message MUST be an encrypted content that follows RFC8291. Its size is between 1 and 4096 bytes (inclusive).

That rules it out for me then. I like to use XMPP+OMEMO with about 4-5 clients which I can continue a conversation with at any time. Main mobile, tablet, desktop, other desktop, and backup mobile which is usually switched off. (Even if a device has been missing for too long and run out of OMEMO keys, the keys sync up again once I send a message with it.)

You have to trust the servers with your metadata, and that the servers have their inter-server communication locked down, but at least you can choose/operate servers.

Some clients are a bit flaky with their e2e encryption defaults or from a UI perspective it is easy to send an unencrypted message (in a new chat for example) before noticing that was how it was set.

There are a few XEPs the server needs which enable things like OMEMO, efficient mobile data/battery use, offline and multiple device deliverability, file transfers, etc. Audio/video calling has various requirements as I think xmpp only facilitates the setup of the call.

XMPP lacks good clients and suffers from fragmentation of protocol standards implementation

• For Android: Conversations is excellent, also on F-Droid if you don’t want to use the Google store.
• For iOS/MacOS: Siskin or iOS/MacOS: Monal.
• For Linux/Windows: Gajim or Linux: Dino.

“Protocol fragmentation” is not a valid complaint about XMPP – it’s like complaining that ActivityPub is fragmented; but that’s not a problem: you use the services (Mastodon, Lemmy, Kbin, etc) built with it which suit your needs, mostly interacting with that sector of the federation (eg, Lemmy+Kbin), but get a little interoperability with other sectors as a bonus (eg, Lemmy+Mastodon).

🤔

Most people¹, even in this very thread, clearly don’t […]

1. Signal shill-bot personas.

deleted by creator

deleted by creator

deleted by creator

The footwear, or the logic gate arrangement?

If that’s the main problem then that’s easy to solve! Simply use a free public xmpp server.

I mention the self- and paid-hosting options because businesses tend to like having a sevice agreement backed by a contract, and may have additional specialised requirements not provided by free services (xmpp or otherwise).

XMPP. A business can self-host, there are public servers, or there are many businesses which offer customised xmpp hosting as a service.

I can be federated with other xmpp servers or be a locked-down work-only service, or federate with chosen other servers (such as a client company’s xmpp servers).

An excellent discrete maths textbook for those missing the inclusion of the subject in the course: Discrete Mathematics - An Open Introduction, 3rd edition by Oscar Levin

Arkenfox is a tool to assist setting up stock Firefox.

Yeah nah, that’s not the way. Sure people can get away with it, but it’s really not eliminating the hazards.

• https://www.fnqsafetygroup.org.au/wp-content/uploads/2015/12/cutting-empty-drums.pdf
• https://www.worksafe.vic.gov.au/safety-alerts/explosions-when-cutting-used-fuel-tanks-and-metal-drums

There’s a bunch of non-obvious hazards which exist around cutting into containers which have held fuels, including but not limited to:

• An empty propane container could have an gas+air mixture inside it in proportions which could explode.
• Any liquid residue in an empty fuel container can be vapourised by the heat of the cutting, creating a fuel+air mix which can spontaneously explode from the pressure and heat, even without sparks (think: diesel engine principle but instead of a 0.25L cylinder it’s a 200L cylinder).
• An empty gas canister can be contaminated with heavier oils/waxes that could build up over the years of refilling cycles, creating the same hazard as noted for empty liquid fuel containers.

Methods to reduce the hazard include:

• Thoroughly washing the inside of the container before cutting (access can be difficult though).
• Filling with water and cutting while full of water. (Container musn’t be sealed, and the cutting method must be safe to use in a wet environment, and further hazards such as introducing oxygen into the container need to be considered).

“Current AI models cannot forget data they were trained on, even if the data was later removed from the training data set,” Han’s report said.

Bullshit. You delete the entire model and start again.