Noticed that the way #Mastodon sanitizes HTML coming from other instances flattens out block quotes in addition to removing other #formatting.
(Totally separate from the quote-toot debate.)
If I follow someone on WordPress or GoToSocial or Calckey etc. and they include an indented quote, when it shows up in Mastodon, it’ll look like the quote is just another paragraph.
That can totally change the meaning of the post!
Found an open issue on GitHub:
It was pointed out that many of this user’s other posts also contained blockquotes, and I fear that I may have misunderstood many of their posts due to there being no indication of this.
Now you might not think this is an issue if you’re not used to being able to post blockquotes in the first place, but if you’re getting them from somewhere else and you don’t know it, that can be a problem.
For instance, the first paragraph in this post isn’t actually written by me, it’s a quote from the original GitHub issue from two years ago. Writing this on GoToSocial it’s trivial to indent it (and if you look at this post on its own site, you should see it correctly!) and it doesn’t make sense for me to have to think about how many of my followers might be on software that actually breaks my posts!
(The missing italics in the second paragraph are less of a problem, but they would be nice to see them go through.)
Ironically if ActivityPub shared the original #Markdown instead of the rendered HTML, the meaning would still be intact, because Markdown matches so closely with the plain-text #semantics that have developed over *decades* of text-only newsgroups, early email, Twitter/Facebook, and so on.
Discovered an advantage to generating the #LinkPreview on the receiving server: You'll still get previews on posts from other #ActivityPub software that doesn't provide its own.
For example, a post from #GoToSocial in its current alpha version seen on #Mastodon.
“Nostr is a distributed social media protocol that has a chance of working.”
…that involves generating a public/private key pair and sharing the public key around, signing your messages, connecting to different relays…
People coming from Twitter are confused about *picking an instance* of Mastodon. I think the barriers to entry might be a little higher on this.
If you’re trying to use the #Linode marketplace build for #mastodon, you need to fix some permissions in one of the #docker containers.
Otherwise it’ll fail on uploading media, accepting follows, possibly more.
docker exec –user root live_web_1 chown -R mastodon:mastodon /opt/mastodon/public/system
Need to use an actual Linode API key even if you’re hosting DNS somewhere else
Not sure it sets up media storage – getting 500 errors on uploading media
As terrible as the old remote interaction workflow was, the new method of showing a URL and telling the user to copy and paste it is so much worse.
Follow, reply, boost, whatever. The pop-up to send you over to your own instance was a pain. But the pop-up telling you how to work around it is like putting up a sign telling people how to get to the back entrance instead of fixing the door.
I finally added some screenshots (and more troubleshooting tips) to my guide on how to post to #Mastodon from anything (including #RSS, #WordPress etc.) using #IFTTT
How to Post to Mastodon From Anything Using IFTTT
(Incidentally: I built a new recipe from scratch to make sure I wasn’t missing any steps and tried to publish it as a reusable applet, but it turns out IFTTT won’t let you publish applets that use webhooks.)
It is so weird to see triple-digit boosts in the feed.
The funny thing is all the viral posts about how Mastodon is designed to make it harder for things to go viral.
With comment threads longer than I’ve seen in ages.
(Harder, of course, doesn’t mean impossible!)
(And yeah, I’m guilty of boosting some of them too!)
Time for me to stop contributing to the problem of over-saturating the feed with meta-commentary.
(Oh no, I’m doing it right now!)
I have been using the “advanced” interface for #mastodon (TweetDeck style) ever since I joined, mostly because I never got around to trying out the now-standard one when it was introduced.
But with all the new people on the fediverse lately, I’m kind of getting overwhelmed by the multi-column UI.
So I thought I’d give the simpler one a try.
And you know what, it’s actually a nicer balance! Going to try this and @pinafore and see which I end up liking better for desktop.
One problem: I don’t see a way to pin hashtag searches in either of them the way I can in the multi-column view. (I’m thinking it should appear similar to the Lists feature.) Am I missing something, or is it just not implemented in either of these UIs?
Just realized I hit my two-year Mastodon anniversary last week!
(I’ve really been on here two years?)
I updated my article on posting from #IFTTT to #Mastodon again to clarify a few things, and to recommend botsin.space for accounts that will *only* include automatic posts.
I use this technique for several things:
– Link to every new post from an #RSS feed at @SpeedForce
– Post differently tagged links from #Pocket here & at SpeedForce
– Cross-post a very occasional #WordPress blog here
@Virelai I believe it searches posts that the instance you’re on knows about already, without calling out to other instances. So it’ll show you hashtagged posts from:
– the local timeline
– remote users that local users are following.
– remote toots that have been boosted or searched by URL on this instance.
@VirelaiI’ve found that searching on a small instance like booktoot.club turns up fewer results than searching wandering.shop or mastodon.social, but if I search for a hashtag on a bigger instance, then copy the URL of a toot over to the search box on the smaller instance, the smaller instance will find it the next time I search for that hashtag.
Last night I threw together a quick bot to post a random item from a text file in about 20 minutes.
Then I spent 3 hours going through the archive from my old LOL_Spam project at birdsite, pulling out jokes that are too dated or cringeworthy. (I’m hoping I didn’t miss any. I was really tired by the end.)
This morning I modified the script to take a second file as a queue for new items.
So if you’re interested in funny/odd spam subjects (and OK with swearing & lewdness), check out @LOLspam
Anyway, my quick and dirty script to post queued items from one text file and random items from another is here: kvibber/fedbotrandom [edit: moved to codeberg]
Done in Perl so I could just put it in cron on any *nix box instead of worrying about installing a runtime.
Expanded on K2R
Whenever waves of new users arrive, there’s always a fine line to walk between welcoming them and helping them learn about Mastodon…and posting normally so they don’t look at the timeline and say, “WTF, all Mastodon ever talks about is Mastodon. I’m outta here.”
An interesting read on decentralizing the internet, from social networking outside of Facebook & Twitter to building mesh networks that don’t even need ISPs.
Replacing the Pillars of the Internet – Mastodon Blog – Medium
The future of the internet is bright, and it’s decentralized.