Replies

@odd 😂 Sanna har slutat med Mastodon, tyvärr, men jag ska visa henne teckningen. Mitt favoritminne med Sanna och en biff skedde på en restaurang för kanske 15 år sedan, när hon slant med besticken så ett köttstycke flög iväg tvärs över två bord för att till slut träffa väggen på andra sidan rummet. 🥩🪽

@odd Välkommen tillbaka, jag har saknat dig och dina uppdateringar i tidslinjen.

@warner Phew, thanks, you had me worried there for a bit. 😅 Even if there are efforts from companies to enable some kind of control over how their bots crawl our blogs and websites, I think it’s a good to always assume traditional crawlers and AI models gobble up all the data you make publicly available on the open web.

The only way to be reasonable sure they won’t see your stuff is to keep it in a more private area of the web, behind a login or paywall, for example. And even then, there’s always the risk that some of your readers share your writing with the AI tools they use anyway.

@bixfrankonis In a super straightforward way, like ticking a checkbox? No, unfortunately. By hacking around with Hugo templates? Yes. @jsonbecker’s blog is likely close to what you want, and it is hosted on Micro.blog.

@toddgrotenhuis Are you asking about users’ timeline feeds, like https://micro.blog/feeds/toddgrotenhuis.json? If so, yes, they are identical to what you see in the web client, so if you mute a word, that will affect your timeline JSON Feed.

@leeS You should be able to paste that snippet into the plug-in’s setting named robots.txt Content. That will discourage those bots from crawling your site but allow others, like Google.

@leeS In a way, it is already highly configurable as you have full control over the robots.txt content. What kind of configuration options do you wish for?

@ericgregorich @patrickrhone You could collect all your blogs under one main account and still have separate (free) accounts hooked up to the respective blog’s feed. That way, people can follow your individual blogs even though they are technically under one account. Your main account timeline could be hooked up to all your blog feeds, if that’s what you want, or just one or a few of them.

@Mtt Here’s part of the definition from the RFC:

> The 404 (Not Found) status code indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

I wouldn’t say it’s the equivalent of failure, a resource can have gone missing mistakenly or have been deliberately deleted. Or it might have never existed in the first place (a mistyped URL). Avoiding broken URLs is a noble cause and something I strive for myself. But when something is gone for real or never existed in the first place, 404 (or 410) should be returned by the server so that humans and robots, like search crawlers, can take necessary actions.

@Mtt Yeah, I don’t have an opinion about the actual HTTP status code. It could be whatever. As long as there’s no way for an attacker to tell if there’s been a note at a certain URL or not, like in Apple’s case, I’m happy. 😊

@Mtt No, you’re not missing anything, the encryption ends when a note is shared. Apple Notes is a great example, they take this precaution as well. Try stop sharing a note in Apple Notes and then visit its URL, you won’t see “there was a note here previously”. Instead, you’re presented with a login screen. The same is true for paths that never existed, like https://www.icloud.com/notes/Micro.BlogExample. There’s no way to tell an old note URL from one that never existed.

@Mtt @manton Given the Notes feature’s focus on encryption and privacy, I would recommend against introducing extra metadata like this. Not everyone might want the world to know that they previously had a note published at a certain URL. For plausible deniability.

If Micro.blog leaks the information “there was a private note at this URL in the past” – attackers and bullies might exploit that in different ways. For example, a bully that wants to perform a character assassination on a blogger could author a nefarious post like “Hey, I just read Joe’s note here (since deleted) where he wrote [insert false statement here].” and link to a deleted note that actually said something entirely different. If Micro.blog were to leak that there actually was a private note there in the past, it would add credibility to the bully’s post.

There might be other scenarios where an attacker could be helped by knowing a note existed in the past. Generally, you want to leak as little metadata as possible when dealing with secrets and semi-secrets.

@vikingsversussamurai I don’t think there’s a built-in shortcut for playlist, unfortunately. You could create your own if you’re comfortable with Hugo template development (or don’t mind learning). Or copy the embed code YouTube provides when clicking the share button.

@pimoore Yes, I agree. Just as with all new technology, we’ll see a lot of horrible shit go down before it gets better. We’ve seen this before with electricity, cars, and so on. History often rhymes.

@anniegreens @pimoore If you with gain mean OpenAI could use the content to train their models, you’re right; that’s technically possible. But, they would take a huge risk, as their business terms and privacy policy claim:

> We do not train on your business data (data from ChatGPT Team, ChatGPT Enterprise, or our API Platform)

Hopefully, @manton uses a business account (and not his personal account) for Micro.blog’s API requests to OpenAI. And if so, you can feel reasonably safe knowing that your content won’t be used to train their models via this specific feature. That’s not stopping your content from ending up in OpenAI’s training data via other channels, though.

And, OpenAI could say one thing and do another, and they wouldn’t be the first company in the world to lie. 😊

There’s no 100% certain way to be excluded from training data, other than keeping your content away from the public internet. And even then, you can’t really control if another human copies and pastes your content into ChatGPT or something similar.

PS. In case if it’s not clear in my reply above, I see plenty of risks, moral issues, and so on with applied statistics AI as well. I’m not opposed to AI, but I do think it must be sustainably built, regulated, and rolled out responsibly.

@fromjason This post is like a game of “spot the odd one out”. Which of these gadgets is not designed by teenage engineering? 😊

@tkoola I probably know more than the average person about death, saying our final goodbyes and products related to funerals, thanks to our family business. We manufacture caskets, urns, and so on for the funeral industry in Scandinavia.

To get to know a little about a lot, at least when we have a diverse set of clients, is a neat perk of being a developer. Lots of rabbits holes to jump into. I’d bet there are plenty of interesting aspects about sewers.

@tkoola Me too! A reasonable use case for on device machine learning, maybe. “Hey, you don’t usually shitpost in this group. Are you sure you want to do this?”

@snowracer Det förstår jag. I min RSS-läsare har jag en kategori, High Volume, där mikrobloggar, länkbloggar och andra källor som uppdateras ofta hamnar. Lämnas den i fred ett par dagar har jag snabbt hundratals olästa poster där. Jag läser långt ifrån allt, utan skrollar snabbt igenom och plockar godbitarna. Just den kategorin, tillsammans med News, tror jag skulle må ganska gott i en app som Tapestry.

@manton Haha, yep, feel free to send potential future iOS Firefox-specific Micro.blog issues my way for troubleshooting from EU land. 😉

@JohnPhilpin Yep, that is correct, Micro.blog does not notify @-mentions for long posts. I’ve discussed this with @manton in the past and he had some concerns. For example: people creating very long posts, mentioning many people, as a way to get their spam out.

Regarding social timelines (on Micro.blog, Mastodon, Bluesky, etc.) and blog comments… I know Micro.blog kind of blurs the line between them, but I think they are quite different beasts. Commentary on social timelines are more ephemeral, and you have little to no control over what other people say about your blog there. A more traditional commenting system on your blog is more permanent, tied to the post, and you’re 100% in control. Don’t like a comment for whatever reason? Just delete it.

Say, for example, you had a WordPress blog set up to cross-post to Mastodon. One day, you decide to import 381 old posts from 2016. Mastodon doesn’t have a concept of importing old posts to the timeline. So if someone would like to have a discussion on Mastodon about one of your old posts, they would have to create a new entry on their timeline, linking to your post.

In theory, you could ask your WordPress blog to cross-post all the 381 old posts to Mastodon during import as new posts, just to get entry-points for commentary. But your followers probably wouldn’t like that very much. Your posts would take over their timelines. 😊 The same is true for a Micro.blog hosted blog and the Micro.blog social timeline.

All this to say, if you want a more traditional commenting system on your blog, you could hook it up to Commento or a similar service.

@JohnPhilpin The fallback link has been there from the beginning and shows up when something goes wrong. The documentation is lacking, sorry about that, but I’ve explained it a bit over here.

In this case, the problem is that you’re referring to an old post that has never existed on the Micro.blog timeline, so there’s no entry there for the plug-in to link to. And no, you can’t really comment on a blog post that has no Micro.blog timeline entry. You could send a webmention.

You can change the fallback text to something that makes more sense to you, like “Write me on Micro.blog”, or disable it completely by unchecking Show fallback link in the plug-in settings.

Thanks for pinging me, @SimonWoods, I might have missed this one otherwise.

@pratik There sure is. Hehe, yeah, I’m not sure where we will keep this one yet. It will probably sit where it is in the photo for a while, until we disassemble it and pass it along.

Sitemap for dahlstrand.net