Replies

@manton Works rather well. I just played a round of Tetris on Game Boy via the Delta emulator. 👾 There were plenty of Apple warning messages and tapping “yes, I really want to do this” to get AltStore PAL installed, but from there it was smooth sailing.

@Archimage That’s encouraging. 😊 Should I ever come around to implementing my own, I will probably write in assembly, targeting one of the microcontrollers I know. The Sharp LR35902 (Game Boy), most likely.

Have you visited the Forth Haiku Salon? It’s a playground for writing and sharing short visual Forth programs. It might be a fun exercise to port (some of) its glossary over to your Forth, to get basic support for graphics programming.

@Archimage Ahh, Forth, what a lovely little language that is. 🥰 Writing my own is still on my someday maybe list.

@eumrz @pratik @moonmehta It’s possible, but not something I intend to work on. A workaround might be to follow the people you want to follow on Micro.blog and subscribe to your own timeline RSS feed. That should net you the same posts and replies in your feed reader.

Also, a friendly reminder that this experimental hobby project of mine is just that, a passion project. 🥰 It costs time, attention and money to develop, maintain and host and generates zero monies for me. Like any free thing on the world wide web, it might go offline anytime without prior notice. So, you know, don’t rely on it for anything important.

@odd 🎉 Sorry I missed this yesterday, but I’m glad you solved it. 😊

@pratik Yes, almost anything is possible in the digital realm. 😊 But Search Space does not currently offer a built-in, easy to use option, unfortunately.

@clorgie Hey, sorry for my late reply. It looks like it’s there now, could it have been a timing issue?

@lucas Hey, thanks for checking out my plug-ins. Conversation on Micro.blog isn’t really set up for use on blog post listing pages, unfortunately. I’ve been thinking about adding support for it in the future, though. But for now, it’s designed to be used exclusively on the actual blog post page.

@bjoreman Yes, so dumb! Also, the “hey, it looks like you’re exercising” thing that is great when you actually forgot to start a workout but infuriating when you’re just out for a stroll or something.

@manton Oh, yes, 2024 is the year of the blogroll! 🎉 Thanks for building this into Micro.blog.

@torb I loved this one and should get back to it. Life happened, so the last chapter is still waiting for me. Thanks for the reminder!

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

Sitemap for dahlstrand.net