Dass man in #Mastodon andere Toots nicht zitieren kann ist eine schlechte Designentscheidung.
Es ist für den Zitierten schlecht, da er u.U. nicht den Quellverweis bekommt, den er verdient.
Es ist für den Zitierenden schlecht, da er in den Verdacht des Plagiarismus gerät. Will man die Informationen nicht nur als Link teilen, der im Getöse untergeht, muss aufwändig der originale Toot rekreiert werden. Das kann schnell so aussehen, dass plagiiert würde.
I think inline #documentation is an important tool to making software readable. It makes software maintainable, encourages future development and makes it easier to join the project as a developer.
This is why I advocate for #mastodon to start encouraging inline documentation with #yardoc, requiring it for any new PRs and serving this API documentation on joinmastodon.org.
Is there some “dev mode” in Mastodon I can turn on to see (a) what ActivityPub messages are being received and (b) why they aren’t doing anything/got rejected? #webdev#mastodondev#activitypub#help
"I noticed that the vanilla mastodon server uses Ruby on Rails; and they picked Puma as their rack server which is a poor choice. I experimented by setting up a VM with common VPS specs and tested a single line change in the Gemfile and got massive performance and efficiency increases" https://reddit.com/r/Mastodon/comments/18q2s05/i_noticed_that_the_vanilla_mastodon_server_uses/
It "worked"! Sort of? I got back a 202 status which means that it verified the cryptographic identity of the post, but I still see the "74 posts - Older posts are not displayed" message here:
Have just opened a pull request to enable OAuth 2.0 refresh tokens for Mastodon, which is a first step towards enabling expiration of access tokens, to increase security to best practices.
I reported a Mastodon bug that exposes private DMs (now called private mentions) as public posts (aka "toots"). The ENTIRE Mastodon team REJECTS this bug as NOT REAL because this bug exists only in the UI layer and not deeper in the application code layer. Mastodon engineers INSIST that this exposure of user's PRIVATE DMs to the general public is WORKING AS DESIGNED. Mastodon further BLAMES THE USER FOR EXPECTING ANY LEVEL OF PRIVACY IN THE FIRST PLACE and says that if I want to send private DMs then I should USE A DIFFERENT PLATFORM INSTEAD!!!!!
Yes that's right, the warning/disclaimer attached to the DM User Interface implies basic privacy but not encryption, but then when pressed on an intermittent failure to deliver even the basic privacy implied by this disclaimer, the Mastodon team blames the user for expecting even basic privacy!!! This level of CONTEMPT FOR USER SAFETY & PRIVACY is utterly astounding.
This type of obtuse catch-22 abusive gaslighting mental gymnastic tap dancing and dishonest parsing of the meaning of the word "is", is something that we have all come to know and loathe in the corporate environment, but here it is now got in our house like a pigeon from hell, infecting FOSS like the disease that it is.
We all want salvation from the corporatization and enshittification of the internet. Crowd-funding of slick marketing campaigns won't save us. There needs to be substance under the hood, there needs to be vision, there needs to be some coherent ethical framework. Being okay with the leaking of user's private communications is not it!
Yes Mastodon is better than a nazi genealogical project hosted on IBM servers, but then again so is being trapped in an elevator for 24 hours with your most annoying co-worker. That's not exactly a very high standard, is it? Unfortunately when I look under the hood at Mastodon's vision, I find this team to be capable of building nothing more than a Roomba to Nowhere. Cute, but certainly not revolutionary, and for some unlucky users, downright dangerous.
[update] To thank me for reporting this bug on Github, the Mastodon team has now blocked me on Github.
@renchap@Claire@marcus@grishka@mellifluousbox@dopatwo [this list of mentioned has been edited to remove blocking users, so as to avoid having this privacy/security complaint cause any further unwanted disruption of their tranquility.]
I constantly hear "Mastodon looks clumsy" as a reason why X people don't get excited. This is why I for one have focused in making my instance feel good and familiar. The problem is, it's not like this everywhere. It's not consistent. It would be fun to see something more modern in the Mastodon core in the future. After all, Mastodon is the most viable "Twitter alternative" of them all.
If I were to suggest Firefish or Akkoma, most people would be shocked. Mastodon is "almost there". People get in, but then give up. Mastodon should attract more than just a certain type of nerds. This is why it needs more work FROM us, the nerds. #Mastodon#MementoMoriSocial#MastodonBirdUI#MastodonDev#WebDev#SocialMedia
Anyone who has any experience with the Mastodon API / Mastodon apps, is it better to use the streaming api to continuously check for updates, or to periodically make requests to the server to check for updates? I guess I'm not really sure I understand how streaming APIs work.
@Gargron should add a mode to Mastodon that creates an instance for the pool for auto-selection by new users.
This should start by informing new users that their account is temporary and time-limited, perhaps 6 months or 1 year, and telling them how to migrate to another instance for a permanent account.
Every instance that's not in the pool should ask the admin to set a maximum limit to user accounts, that defaults to 10,000.