njamster :godot: / is on Nostr

I {enter almost any verb} games! • :godot: GodotEngine • 🎮 GameDev
♂️ He/Him • 🇬🇧 EN / 🇩🇪 DE / 🇪🇸 ES •📍Berlin, Germany

I provide ALT text for all of my media posts, but will (grudgingly!) boost posts that don't as well. And I boost a LOT of stuff! My actual post volume is lower, though: https://justmytoots.com/@njamster@mastodon.gamedev.place

Searchable via tootfinder

Last Notes

2024-05-28 14:39:56

- reply

@npub1g5t…xw4h Is that... a Leibniz cookie card back? 😂

2023-09-09 13:14:53

- reply

@npub1nhw…g2sy You're welcome! 😁 Actually, I can't tell you how often I look up something and come across my own answers. It's a *really* weird feeling reading something, going "Hey, that's a great answer", just to realize a few moments later that it's your own. 😂

2023-08-06 10:53:14

- reply

@npub18gc…v7cg 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.

2023-08-06 10:40:29

- reply

@npub18gc…v7cg 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".

2023-08-06 10:23:03

- reply

@npub18gc…v7cg 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, @npub1l5t…qq33, 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.

2023-08-06 10:03:20

- reply

@npub1svs…p66u 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.

2023-08-06 09:11:29

- reply

@npub1svs…p66u @npub1zf7…zwqy 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?
https://github.com/mastodon/mastodon/issues/18222