After quite some time, I’m finally ready to share this.
Fediverso
56
Posts
21
Posters
46
Views
-
@brozu I just published build 68 - Minimum iOS version now lowered to 18.x - Foundation models (Apple Intelligence) will be affected. Now you can try it (please give me a feedback as I couldn't test it on 18.x devices). Thank you!
@stefano crashed during login, just after I selected the instance and authorized.
-
@stefano crashed during login, just after I selected the instance and authorized.
@brozu Yes, there's a problem on iOS 18 - I'm looking into it and downloading the correct simulator to test it personally
-
@brozu Yes, there's a problem on iOS 18 - I'm looking into it and downloading the correct simulator to test it personally
@stefano thank you Stefano 🙏
-
EDIT: Build 68 should also run on iOS 18.x but it currently crashes. I'll see if I can fix it.
After quite some time, I’m finally ready to share this.
MastoBlaster is now available in public testing on TestFlight.
It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.
What makes it different:
• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usageAlt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.
It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.
Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.
TestFlight link:
https://testflight.apple.com/join/Pkxa5R1kStay tuned.
#MastoBlaster #iOS #Fediverse #Mastodon #snac #snac2 #Akkoma #GoToSocial #ActivityPub #OwnYourData
@stefano any plans to make the source available? the app looks great btw, although it seems that you can’t go to the original/parent post in a thread? in feditext you just tap on a post and it opens as the ‘selected’ one
-
@stefano any plans to make the source available? the app looks great btw, although it seems that you can’t go to the original/parent post in a thread? in feditext you just tap on a post and it opens as the ‘selected’ one
@lina thanks! I'm not sure if I'll make the source available. It surely need a nice cleanup 🙂
The tapping the post and open the entire thread is something I need to fix - it's in the todo list
-
EDIT: Build 68 should also run on iOS 18.x but it currently crashes. I'll see if I can fix it.
After quite some time, I’m finally ready to share this.
MastoBlaster is now available in public testing on TestFlight.
It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.
What makes it different:
• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usageAlt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.
It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.
Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.
TestFlight link:
https://testflight.apple.com/join/Pkxa5R1kStay tuned.
#MastoBlaster #iOS #Fediverse #Mastodon #snac #snac2 #Akkoma #GoToSocial #ActivityPub #OwnYourData
@stefano very nice, giving this a go
-
EDIT: Build 68 should also run on iOS 18.x but it currently crashes. I'll see if I can fix it.
After quite some time, I’m finally ready to share this.
MastoBlaster is now available in public testing on TestFlight.
It is a lightweight, privacy-first Fediverse client for iOS, built around a simple idea: fast, small, predictable behavior, and first-class support for snac.
What makes it different:
• snac-first by design, not "compatible by accident"
• Works with all Mastodon API compatible software, including Mastodon, snac, GoToSocial, Akkoma, and others
• EXIF stripping on upload (HDR and orientation preserved)
• Optional on-device alt text generation via Apple Intelligence for your uploads and for images in your timeline
• Markdown posting for snac
• Granular notifications, grouping, multi-account
• Blocking and moderation tools
• Very small footprint, very low RAM usageAlt text generation happens entirely on device via Apple APIs on supported hardware. Nothing is sent to external services.
It is built around my own workflow and priorities. It may not be for everyone, and that is perfectly fine.
Important note:
MastoBlaster will always be free for BSD Cafe users, illumos Cafe users, and for anyone connecting to a snac instance, including self-hosted ones.The app is already usable, but this is still a test phase. I am looking for feedback, bug reports, and real-world usage insights.
TestFlight link:
https://testflight.apple.com/join/Pkxa5R1kStay tuned.
#MastoBlaster #iOS #Fediverse #Mastodon #snac #snac2 #Akkoma #GoToSocial #ActivityPub #OwnYourData
@stefano is Android support anywhere on the roadmap?
-
@stefano is Android support anywhere on the roadmap?
@pfr not (yet). On Android, I really like Moshidon so I never felt I had the need/urge to implement something new
-
@nabeards I've just published build 68, minimum iOS version now lowered to 18.x - Foundation models (Apple Intelligence) will be affected.
@stefano just sent a crash report your way. After trying to login, the app just crashes. If you’d like any other info than what TestFlight gives you, let me know!
-
@stefano just sent a crash report your way. After trying to login, the app just crashes. If you’d like any other info than what TestFlight gives you, let me know!
@nabeards thank you! Are you on iOS 18.x?
-
@nabeards thank you! Are you on iOS 18.x?
-
@stefano awesome! Mille grazie!
I just sent two crash reports. The app crashed while authorizing and now refuses to start.@stefano the bug is fixed and I can use the app. Unbelievable, what you achieved there in such short time.
-
@stefano the bug is fixed and I can use the app. Unbelievable, what you achieved there in such short time.
@seiz Thank you. I’ve been working on it for a long time, the skeleton of the app has been there for more than 3 years. I’ve identified some points that were specific to iOS 26 and put them into a condition. I could make it work with less than 40 modified lines.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@julian@fietkau.social in a parallel conversation not about interaction controls, @rimu@piefed.social made the case for batching events, which I'm going to repurpose as an argument against sending additional activities for backward compatibility (unless absolutely necessary.)
> As a user can do a great number of notable things (posting content, liking content, following others) each minute and there can be thousands of instances to send to, a great many POST requests can be sent in a short amount of time.
>
> For example if 5 people cast 20 votes and there are 500 instances, the instance hosting the community containing the posts being voted on must send 5 * 20 * 500 = 50,000 HTTP POSTs.
-
@julian@fietkau.social @evan @julian@activitypub.space @smallcircles this makes me really wish people didn't overload the AS2 vocab so much, and were less afraid of defining their own extensions. you could swing it so that the same activity is an Add, Accept, and ReplyAck. it sucks that we have to pick one instead of using whatever makes sense. (developers: please support multityping and/or duck typing! composability is the only true path to extensibility, and one size never fits all...)
-
@trwnh There's also this, yeah. GTS interaction controls have already gone through one breaking schema revision from version 0.19 to 0.21 (with 0.20 trying to manage both), and a core goal of the FEP I'm working on is to not break compatibility again.
Sending out an Add in addition to the Accept(Note) that's already happening should be non-breaking for existing implementations, I'm pretty sure. What's left to decide is whether it's a good idea.
-
@trwnh This is in the context of a FEP draft which prescribes a meaning (including desired side effects) for compliant implementations.
Hence my fidgeting with the vocabulary. The effects are the goal, the question is how they should be expressed and broadcasted. (Principle of least surprise, potential compatibility with existing implementations that look at the replies collection, concerns around server traffic...)
-
@julian@fietkau.social @evan @julian@activitypub.space @smallcircles i think the issue here is that projects are doing things that may or may not get widely adopted, then if the proposals ever change, they have to deal with older software only understanding the old thing they tried. (this is where i would say something about protocol capability negotiation)
-
@julian@fietkau.social @evan @julian@activitypub.space @smallcircles alternatively add the Reply itself, parallel to likes/shares collections. it depends on whether you think the replies collection should always contain a specific type of object, which i don't think is something you can guarantee because publishers can do anything with it. similar to how some publishers include activities in threads and some include notes.
-
@julian@fietkau.social @evan @julian@activitypub.space @smallcircles
> replies collection is the source of truth for replies curated by the object owner.
this is fine i think, but the way to do this usually is HTTP GET. you could notify of changes to the replies collection, or you could reify the Reply and then Accept that?
the Reply has an instrument which is the Note. it has clear side effects to Add the instrument to the object.replies. the side effects can be gated behind Accept/Reject like following currently works.
-
@julian@fietkau.social @evan @julian@activitypub.space @smallcircles
> express that the owner of the replied-to object has accepted a reply, i.e. that the reply is added to the post's replies collection and shown under it in the web view
i get that, but the question is whether you can claim this understanding universally for all peers. as it stands, Accept is very vague wrt this. Accept(Note) meaning "Add to replies collection" might be a thing gts does, but that's their interpretation of Accept, not the definition.
