Sly Gryphon @sgryphon@qoto.org

At encampment, at Abbey Mediaeval Festival (Brisbane, Australia)

So, #Threads launched: https://about.fb.com/news/2023/07/introducing-threads-new-app-text-sharing/

I don't need an account, just like I don't need a Gmail account, because (once they federate), my existing Fediverse account will work fine to interact with them.

I see a whole lot of weird assumptions/accusations/misunderstanding about Threads and similar. That's not how federation works; and we have some good exising comparison/evidence from things like Gmail vs small email players.

Having Facebook/Instagram/Threads federated just means I can follow people that use those services and see their messages and interactions. It does not mean that Meta will send me adverts, algorithm-feeds, or anything like that; I just see the friend I followed (same as any other Fediverse account).

Well, I mean they *could* technically start spamming me with fake messages from my friend that contains adverts (just like Gmail could start sending out spam to email accounts around the world). But why would they? That would get them blacklisted.

That's not how they make money. Meta (like Gmail) doesn't make money by sending spam; they make money from showing adverts, feeds, etc to *their* users. So, my friend (on Threads) will be the one seeing all the adverts, algorithm feeds, etc. Adding federation might make them more likely to stay (because they can now also see my), but won't affect my feed.

Threads will compete with other fediverse sites by offering a better client, better search, wider apps, and additional features (because of a larger dev team), just like Gmail does for email -- but at a price of showing *their* users adverts, etc (or charging).

So each user has a choice: use Gmail/Threads with features but at the cost of adverts, or you a small/your own fediverse/email server.

The benefit of federation is that each user has the #freedom to make that choice, yet they can still communicate with each other.

Interesting race/driving test between three #selfdriving cars; all three did great, although the #tesla used the freeway. Video here: https://www.youtube.com/watch?v=6xUmZXoqaDQ

My thoughts on "#AI and #copyright: Addressing an incongruity", and why is #photograpy, which can be just a click of a button (although a good photograph may involve a lot more), protected by copyright, when AI generated art is not? Maybe it is just time to re-evaluate, stop allowing large corporations to profit from increasingly restrictive copyright and get rid of it altogether, moving towards #opensource, with technology providing solutions through patronage and crowdfunding. That way we can head towards a future where creativity, irrespective of its source -- be it human or AI -- is celebrated instead of being stifled. https://sgryphon.gamertheory.net/2023/05/20/ai-and-copyright-addressing-an-incongruity/

Work Goth Day (May 22) party at Club 1334.

Thank you not #Microsoft. It is fair enough to have systems that don't support #ipv6 yet, but to actively break/fail to work when IPv6 is enabled is pretty bad. Ignore IPv6, sure, but to have your IPv4 systems stop working simply when IPv6 is enabled doesn't really allow any kind of migration path.

So, #AWS #cloudformation vs #AWSCLI. Looks to be ending up the same as Azure #ARM vs #AzureCLI. If you already have the template, and deploy it once, it is good. But developing CLI scripts is quicker (debug one step at a time, rather than all at once). And templates run into the same dead ends: e.g. decides it needs to recreate the entire subnet, so it attempts to, but runs into an IP address conflict with the existing one, and the whole thing stops. There are things/changes that declarative approaches just can't do, and you need to use migrations (CLI scripts).