Here it’s nutrition information by the gram, serving size by the gram, packaging by the millilitre.
The only way you can compare the relative value of different ice creams is by using the serving size and # servings info from the nutrition panel to calculate the grams per package. (Or even better, comparing g/fat per package because that’s where the value is).
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”).
It’s also not even a possibility. Properly walkable (for all abilities) neighbourhoods hardly exist in Australia.
In the 79 years before turning 97, she could have not voted for policymakers who push car dependency and urban sprawl.
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.
Embedded images on lemmy are loaded directly from the servers they’re stored on, often not your home instance. Bam, adversary has your ip and access time and what caught your attention.
When i’m 90, wheel me out to the orchard and I’ll watch the chickens. If you give me a stick i’ll wave it to scare the parrots off the apples.
Excellent! Based on ConverseJS with a custom UI. OMEMO is intended but requires work to detangle ConverseJS’s implementation from the ConverseJS UI.
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).
…beyond the environment?
The symbol referred to was displayed like so: 
didnt she try block mardi gras earlier this year?
Aliexpress
Could go old school and build your own:
Page 66: https://www.worldradiohistory.com/AUSTRALIA/Electronics-Australia/EA-1992-07.pdf
Page 126: https://www.worldradiohistory.com/AUSTRALIA/ETI-Australia/90s/ETI-1990-01.pdf
^PSST, rumour is that paedophiles use HTTPS…^
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.)
Wheat and Flour Testing Methods - A Guide to Understanding Wheat and Flour Quality; Wheat Marketing Center Inc, 2004