Recent Replies

  • Replying to: @leeS

    @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.

  • Replying to: @leeS

    @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?

  • Replying to: mstdn.ca

    @mabel I'm not sure if this is helpful in your case, but most search engines let you narrow down your search to a specific site with a query like this site:https://veronique.ink kurt. Example using DuckDuckGo.

  • Replying to: @ericgregorich

    @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.

  • Replying to: @Mtt

    @Mtt Sorry, no, that's a video quote from the linked article.

  • Replying to: @Mtt

    @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.

  • Replying to: @Mtt

    @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. 😊

  • Replying to: @Mtt

    @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.

  • Replying to: @Mtt

    @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.

  • Replying to: @val

    @Miraz @val Thanks you two! 🥰

  • Replying to: www.manton.org

    @manton A belated congrats on launching! 🎉

  • Replying to: maique.eu

    @maique 😍

  • Replying to: @vikingsversussamurai

    @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.

  • Replying to: @ddanielson

    @ddanielson It's a MINI Cooper SE (this one).

  • Replying to: @tdh

    @tdh Hej Thord, sköj att se en svensk till i Micro.blog-flödet. Välkommen!

  • Replying to: kimberlyhirsh.com

    @KimberlyHirsh 👏 It's my favorite Zelda. Or, at least, it's in my top three. It's hard to pick only one. 😊

  • Replying to: @pimoore

    @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.

  • Replying to: @anniegreens

    @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.

  • Replying to: @manton

    @manton It happened to me as well; I noticed it yesterday.

  • Replying to: @fromjason

    @fromjason Yeah, it's Panic's gaming console, but teenage engineering designed the hardware.

  • Replying to: @fromjason

    @fromjason Yes! 🏆 🎉

  • Replying to: micro.fromjason.xyz

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

  • Replying to: blog.timokoola.com

    @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.

  • Replying to: mastodon.social

    @ohhelloana Many good URLs in there, thanks for sharing! I dump hyperlinks from time to time as well. It's weirdly rewarding, a bit like spring-cleaning. 🧹

  • Replying to: blog.timokoola.com

    @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?"