nostr:npub18gcrwqwmhysr7hkmuc04tkde3nmwm7wspq9qm732mhvxnlfy56tqhfv7cg It's also worth noting that you *could* post your entire blog post as one long post here if your instance allows posts of that length. Read: the maximum post length is defined by your instance, not Mastodon. I think there even is a WordPress plugin to automatically share your blog posts on Mastodon for you.
nostr:npub15y6x73rcu0867mulkdd7mdp28mrx6zlh6206suwsm3a7e7v5fsdqq4azut nostr:npub1l5tgujhhn7pyxunuaxwklaune7ak8yvf8zg0slsr45fmkhrrhgeq37qq33 That's another good point. I'm using the advanced UI and it can get very annoying to have to click to expand posts one by one.
I've also had some feedback about people who could only see the post that was boosted, and not the rest of the thread.
nostr:npub18gcrwqwmhysr7hkmuc04tkde3nmwm7wspq9qm732mhvxnlfy56tqhfv7cg Yeah, I think if I boost a post from an instance that nobody on your instance is following, you only see that one post but not the rest of the thread (unless you check the original instance of the post). So the bigger your instance, the less likely this is to happen (and vice versa), but it's always a possibility! That's why it's a good idea to indicate in every post that it belongs to a thread, e.g. "🧵3/12".
nostr:npub18gcrwqwmhysr7hkmuc04tkde3nmwm7wspq9qm732mhvxnlfy56tqhfv7cg Entirely depends on the client people are using! In the default web UI posting long threads can get very annoying, yes! My client of choice, nostr:npub1l5tgujhhn7pyxunuaxwklaune7ak8yvf8zg0slsr45fmkhrrhgeq37qq33, will collapse posts belonging to the same thread, so personally I don't mind. 🤷♂️ Worth noting that if you post stuff directly here, I'm able to boost the part(s) of your blog post that I particularly liked, not just the post as a whole.
nostr:npub15y6x73rcu0867mulkdd7mdp28mrx6zlh6206suwsm3a7e7v5fsdqq4azut What do you mean sending an extra notification? Servers might be able to get that info via ActivityPub, but clients only work with Mastodon API.
nostr:npub1svs3dzxhfc3mtdr7a59jsj48wdg0f0fgy0au2yataxu6vza6n8userp66u I read "a limitation of the protocol" as "a limitation of ActivityPub" since that is the protocol Mastodon is using. It's true that the Mastodon API doesn't support this feature and that's what stopping clients from implementing it, but that's on Mastodon itself, not the protocol it's using. As far as I can tell, ActivityPub doesn't do anything to prevent this feature from being implemented as described.
nostr:npub1zf74eseytr2qwva2pa7lek9029hhmk22a4ah5yy28ja4hd87kyuqf9zwqy I’m afraid it’s a limitation of the protocol.
nostr:npub1svs3dzxhfc3mtdr7a59jsj48wdg0f0fgy0au2yataxu6vza6n8userp66u nostr:npub1zf74eseytr2qwva2pa7lek9029hhmk22a4ah5yy28ja4hd87kyuqf9zwqy Well, yes, currently no Mastodon app will be able to implement this (as servers will only notify the original poster of a boosted post). However, that is *no* limitation of the protocol (#ActivityPub) in itself – it's a design decision of #Mastodon! Or at least I don't see any reason why it couldn't be done: The information who boosted is already there, you'd just need to send an extra notification to the server of that person, no?