Introducing @CrystalApp, a new Mastodon app for Apple TV.
Add your favorite hashtags to Crystal to play slideshows of photos and art from across the fediverse. It’s a little like having Mastodon feeds as your screensaver.
Available from the App Store on Apple TV https://apps.apple.com/us/app/crystal-for-mastodon/id6479724862
[#]MastodonApps #AppleTV
=> View attached media | View attached media | View attached media
=> More informations about this toot | View the thread
Jay Graber says independent, decentralized projects are building “alternative infrastructure”.
If you develop or admin for ActivityPub and the fediverse, you can be confident that you aren’t building alternative infrastructure. It’s all just infrastructure here.
https://fed.brid.gy/r/https://bsky.app/profile/did:plc:oky5czdrnfjpqslsw2a5iclo/post/3lfnl6m4gsc2e
=> More informations about this toot | View the thread
There might even be another solution here that doesn’t require any UI at all: by default, let apps access only the contacts where:
Would prevent apps from spamming invites to people who don’t have the app, or getting the info of people who never consented to the app having it. Legitimate communication apps wouldn’t need to ask for contacts anymore.
=> More informations about this toot | View the thread
For those tempted to argue about the impracticality of implementing my tongue-in-cheek mockup:
Imagine, instead of the silly alert message, a simple toggle in privacy settings “allow others who have me in their contacts to share my information with apps”
If it’s switched on, it flips a bit on a server that the other person’s OS can check, just like how it checks if you’ve set up iMessage etc.
The point wasn’t the UI, it’s that other people’s info shouldn’t be yours to give out to apps
=> More informations about this toot | View the thread
and what the requestees see:
=> More informations about this toot | View the thread
This is what the iOS contact permission prompt should be
=> More informations about this toot | View the thread
[#]SwiftUI onPreferenceChange now requires a Sendable non-async closure in Xcode 16.2.
Does this mean we aren't supposed to be manipulating view state when a Preference value changes? Kicking off a Task satisfies the compiler, but seems like a bad idea.
How exactly are we supposed to be using onPreferenceChange now? Are there any other ways of passing values up the hierarchy that still work? Why aren't breaking changes like this explained in the release notes?
=> More informations about this toot | View the thread
The funniest and only noticeable part of this macOS update is how you get a notification that says “Image Playground Is Here" but when you click it, it doesn't open Image Playground (honestly, probably for the best).
Instead it opens a new system settings pane called “Image Playground Is Here”
with the title "Image Playground Is Here”
which is entirely blank apart from a sub-pane also titled "Image Playground Is Here”
in which it conveniently explains that "Image Playground is now available”
=> More informations about this toot | View the thread
Saw an error message on a website that said “We have encountered an error” because their server was down.
Uhh no, you've made an error
=> More informations about this toot | View the thread
then again maybe that’s because the technical standards underpinning the fediverse have embarrassing names like webfinger that nobody wants to say
=> More informations about this toot | View the thread
We’re all used to hearing about how mastodon is too technical, but every time I read about new developments in bluesky world it always sounds like “a new way to containerize your PDS into your DID across PLC relay lexicons is laying the foundation for paid subscribers to someday be able to bookmark posts using publicly verifiable cryptography”
meanwhile in the fediverse there are entire new apps and services being launched that you can just sign up for and use
=> More informations about this toot | View the thread
I can't stand how clicking a link on GitHub no longer opens the link but instead does some weird JS stuff to swap out the page contents. It feels slower than just letting the browser handle navigation, and makes scrolling jerk all around.
Who would have thought the primary function of a web browser would be better done by a web browser instead of faking it with three megabytes of javascript? 🤯
=> More informations about this toot | View the thread
=> This profile with reblog | Go to dale_price@mastodon.online account This content has been proxied by September (3851b).Proxy Information
text/gemini