While I was away from home for a few days I was able to access data on a machine at home using ssh. Thanks to having IPv6 both at home and in the place I was staying this worked without needing to mess with fragile NAT or port-forwarding setups.
Are you f* kidding me, Apple?!
After a long time, I filed another bug report using Feedback Assistant because the bug was bad enough that it’s worth the effort of writing it all down.
When uploading a sysdiagnose (or probably any other attachments) you get the usual privacy notice that there is likely a lot of private and other sensitive info in those log files. It’s not a great feeling but it is what it is with diagnostic data and I mostly trust the folks at Apple to treat it with respect and I trust the Logging system to redact the most serious bits.
However, when filing a feedback today a noticed a new addition to the privacy notice:
"By submitting, you […] agree that Apple may use your submission to [train] Apple Intelligence models and other machine learning models."
WTF? No! I don’t want that. It’s extremely shitty behavior to a) even ask me this in this context where I entrust you with *my* sensitive data to help *you* fix your shit to b) hide it in the other privacy messaging stuff and to c) not give me any way to opt out except for not filing a bug report.
Do you really need *more* reasons for developers not to file bug reports? Are the people who decided to do this really this ignorant about the image Apple‘s bug reporting process has in the community? How can you even think for a single second that this is an acceptable idea?
So, WTF, Apple?!
LLMs can't stop making up software dependencies and sabotaging everything
Hallucinated package names fuel 'slopsquatting'
https://www.theregister.com/AMP/2025/04/12/ai_code_suggestions_sabotage_supply_chain/
A lingering problem I had was my Wireguard tunnel for client devices.
I have multiple times added some subnet and then had to individually add it to the allowed IPs on each device. I didn't want to just preemptively forward the entire 10.0.0.0/8 block, because that would be asking for trouble.
Now it just dawned on me that if I only use IPv6, that problem is gone. Not once did I have to change the v6 prefix, because I can easily leave enough room to grow.
Thanks to IPv6 I can route an IP prefix to my laptop and use it for developing software in Docker containers. The software can use this to connect to a database hosted at a cloud provider which is shared with other developers.
Since there is no NAT I don't have to worry about TCP connections stalling when the NAT times out connections.
For security the database is protected using both an IP whitelist and TLS certificates for both client and server.
A website I manage has been subject to some port scans and subsequently a management interface on a separate port number has seen password brute force attempts.
Since IPv6 gives me enough addresses I have moved the management interface to a different IP address.
IPv6 has so many addresses that scanning all of IPv6 address space is not feasible. So scans use other methods such as scanning known domain names.
If you have multiple domain names pointing to your host they don't all have to point to the same IP address.
I am considering the idea of writing a weekly post #HowIPv6HelpedMeThisWeek giving one example of something useful IPv6 has done for me in the past week.
I am aware that it may be challenging to come up with a novel example each week. And really it does not necessarily have to be novel in order to count. Doing the same useful thing each week is still useful. But the posts will obviously be more interesting, if I don't repeat the same thing week after week.
It may also be challenging to notice each time IPv6 does something useful because we tend to notice things which are broken rather than things which are working. And IPv6 just working is the experience I have most of the time when connected to networks with native IPv6.
It would probably have been easier to come up with a weekly post about how IPv4 annoyed me in the past week. But if I want to make this a regular thing, I should focus on the positive things and not turn this into IPv4 bashing.
The hashtag is of course not only for me to use. I am not the only person who have had positive experiences with IPv6.
Trump’s Liberation Day = Make America Go Away Day
#MakeAmericaGoAway #BoycottTrumpAmerica #BoycottUSA #BoycottMusk #BoycottBroligarchs #uspol #ukpol #canpol #auspol
Julie Hughes
Joachim
nixCraft 🐧
Jana
Jen Sorensen
MasterDim