Replies

@pratik Yep, you’re absolutely right, rssCloud (and simillary WebSub) are for people who want close to real-time notifications from feeds. And for developers, as these protocols make it possible to build more efficient feed readers. Manton writes about that in the WebSub chapter of his book.

If you’re not a developer nor a person caring about real-time updates, you can safely ignore rssCloud and similar technologies. 😊

@pratik Micro.blog hosted blog’s import functionality is something separate from the Micro.blog timeline. That feature could in theory support rssCloud for real-time imports from external sources like Letterboxd. Maybe it does. Or it may just do it the old fashion way, checking these feeds every five minutes, every hour, or whatever @manton feels appropriate.

The statement “Micro.blog hosted blogs don’t have the cloud element in their feeds” is about the other direction. People subscribing to your Micro.blog hosted blog can’t get real-time updates via rssCloud, because Micro.blog-hosted blogs don’t have support for that in their feeds.

Puh. Now I’m going to avoid typing the word blog for a while. 😅

@pratik Sorry for the late reply, I meant to answer back then but forgot about it. 🫣 rssCloud enables feed readers (like the Micro.blog timeline) to get real-time notifications when a feed updates. This is nifty for people subscribing to the feed: they don’t have to wait minutes or hours to see new posts – they will show up instantly.

For this to work, the feed reader and the feed publisher have to implement support for rssCloud. The Micro.blog timeline has support, but Micro.blog-hosted blogs don’t.

@odd Tack! Det är fantastiskt att vår lilla podd har åtminstone en internationell lyssnare. 🥰

@njr No offense taken and, yes, you’re right that it’s my initials. But I guess it also makes me appear like some kind of a jerk? 😅 At least to British readers. I do my best to be the opposite, though. 😊

@veronique Yay! 🙌 And I just saw that you’ve shipped already. Thanks, that was fast! I will be waiting with anticipation by the mailbox. 🥰

@Munish Catching as much sunlight as possible during the day. This can be challenging if you work in an office when the sun is up, but try squeezing in outdoor time during breaks. I usually go for a walk during lunchtime.

Keeping active with hobbies, exercise, and hanging out with people you like also helps. And sometimes, it’s totally okay to just embrace the darkness. Light some candles, eat a kanelbulle (cinnamon bun), read a book, or whatever you find mysigt (cozy).

@dave Could be the static website build step that takes about a minute, maybe? You might get more intel if you keep an eye on the logs while you’re experimenting. You should see the build process there, as well as the fetching of feeds for updating the timeline.

By the way, the Micro.blog timeline supports rssCloud. 🥳 (But Micro.blog hosted blogs don’t have the cloud element in their feeds.)

@futuregeek If you really want, and aren’t afraid to tinker a bit, there are a handful of ways to figure out how popular your feed is. You could put a server (called a reverse proxy) in front of your blog and route all traffic through it. You’ll get full access to the logs and can see exactly how and when the RSS feed is fetched. This will usually cost a bit of money, Cloudflare is one provider offering reverse proxy services.

Another way is using a feed analysis/monetizing service, like Google’s Feedburner. Your blog will get a new feed address, and you will have to redirect your readers to that feed. But after that, you will get those juicy statistics. Feedburner is free.

A third option is to modify your current feed, via a custom theme, to include a tracking beacon (also called tracking pixel). Most web analytics software, like Matomo, have support for this.

But, as @manton already mentioned, regular website analytics (without RSS stats) is by far the easiest way to get started.

@gr36 One solution using complement: {{ range .Site.Taxonomies.categories.micro.Pages | complement .Site.Taxonomies.categories.photo.Pages }}.

@DrOct @odd You can put it anywhere. If you want a visible link, you can have it in the content, menu, footer, etc. on the page you’re linking to from Mastodon. If you don’t want a visible link to Mastodon on that page, you can add it as a link element in the head. You can use the curiously named Meta tags plug-in for that (it should really be called the Head plug-in).

@g Då är det helt klart möjligt att automatisera. Kände dock att mitt svar blev lite för långt för tidslinjen så flyttar över konversationen till hjälpcentret. Jag skrev ihop en liten guide där. Hoppas den går att följa. 😊

@g Då är det lite klurigare, tyvärr. 😢 Hugo (sajtgeneratorn som Micro.blog använder sig av) har en inbyggd funktion som gör det lätt att modifiera bilder som är inlagda med Markdown-syntaxen. Bilder som är infogade med HTML är meckigare att skriva om automatiskt. Det är inte omöjligt men betydligt mer jobb. Blogg-temat du använder skulle behöva modifieras och implementationen skulle bli allmänt skör.

Men, jag funderar på om det behövs ett plug-in. Har du sett att Micro.blog har inbyggt stöd för att leverera bilderna via ett innehållsleveransnätverk (CDN) nu för tiden? Om du aktiverar den funktionen skrivs adressen till bilderna om för att levereras så snabbt som möjligt via Amazons CloudFront-nätverk. Förhoppningsvis. Bilderna skalas dock inte ner utan behåller den storlek som de laddades upp i. (Eller som de eventuellt skalades ner till av klienten eller Micro.blog.) Men kanske är det tillräckligt för att du ska kunna sluta pilla manuellt men ändå få en snabb upplevelse på bloggen.

@g Hur bäddar du in bilderna i dina inlägg, med Markdown eller HTML? Ser det ut så här ![]() eller så här <img src="" alt="">?

@g Önska kan man alltid göra och det lackar ju mot jul. 😊 Hur ser ditt arbetsflöde ut idag och hur önskar du att det fungerade i stället?

@Mtt You could check for that combination with the following:

> {{ if or (not .Title) (and .Title (in .Params.categories “Bookmarks”)) }}
> {{ .Content }}
> {{ else }}
> {{ .Summary }}
> {{ end }}

@kottkrig Tack! Ja, det skulle ju absolut passa i ditt plug-in också. Känns dock lite hackigt att gå via Hugos assets pipeline och resources.ExecuteAsTemplate som jag gör. Om du hittar ett elegantare sätt att lösa det på får du gärna peta på mig. 😊

@ericgregorich Haha, no, it didn’t come across the wrong way. It put a smile on my face as well when @Mtt made me aware of my blunder. Telling a Shortcuts expert about Shortcuts… 🤦

I’m sorry, @rosemaryorchard; please ignore the first sentence in my answer. 😊 Shortcuts are probably the way to go, though. iOS is pretty locked down, and apps are sandboxed, so it might be challenging to control another app from your app without using private APIs and/or jailbreaking the device.

@rosemaryorchard Shortcuts is quite handy when it comes to automating things on iOS. An action called Seek lets you jump to a specific time, or forward and backward by some duration, in the currently playing media. (Music, audiobook, or whatever.)

@vicky At first glance, this code snippet might look bananas. But let’s take a look at a similar one: console.log(['b', 'a', 'n', 'a', 'n', 'a'].join("").toLowerCase()). That’s not too crazy! An array of characters that are joined to a string. Okay, there’s not really a character type in JavaScript; it’s an array of strings. But you get the idea. 😊

So the real question is, how come [({}+[])[2] and company are evaluted as characters? Let’s fire up a JavaScript console and see what happens when we run toString on an empty object: ({}).toString()"[object Object]".

Aha, a string is returned! And whenever we have a string, we can grab single characters from it with the charAt method: ({}).toString().charAt(2)"b". The same thing can be accomplish using bracket notation ([]): ({}).toString()[2]"b".

Another property of JavaScript is that when you add an object and array together, you will get a string back: ({}+[])"[object Object]".

Add all this together, and you will end up with the familiar first sequence from your puzzle: ({}+[])[2]"b". 😅 The code relies on similar JavaScript quirks to generate the rest of the banana, so to speak. 🍌

@danielsantos Okay, at least you’re not the only one wanting wikilink-support in Hugo. Hopefully, it will arrive someday. 😊

Is the actual syntax important, or would [My personal view on Netflix's Wednesday]() be acceptable? If so, and if you’re okay with backlinks only being available to visitors with JavaScript enabled, it’s quite possible to write a little Micro.blog plug-in for this.

@flowinho Wow, that sounds way out of proportion. But if I read the article right, Ladefuchs consciously took the risk of using someone else’s photograph without permission? So there actually was a copyright infringement. It’s just that the fee was way high, considering the circumstances?

(Sorry about those naive questions, but my understanding of German is very basic, so I have to rely on translation software.)

@flowinho Thanks for sharing. From what I can grasp from that article, trolls are trying their luck, hoping to scare people to pay up. But it’s not clear if they actually have a case that would hold up in court? I’m with you; trolls are stupid. 😊

@flowinho I’m interested in this. Are there any examples of individuals with non-commercial blogs or websites being sued?

Sitemap for dahlstrand.net