@prologic@twtxt.net What is “ciwtuau”? I don’t understand, sorry haha

@movq@www.uninformativ.de :-D

In the meantime, I tried to add English subtitles, so the international audience has a chance of enjoying some of them, too. There are a bunch of puns, so translations don’t work at that great.

I went to an exhibition of my fine arts teacher who passed away last year. He was a pretty cool dude and good teacher. I reckon I had him in 7th and probably also 8th grade. His Schelme (imps) were very famous here in this county and presumably well beyond.

Unfortunately, picture frame glas doesn’t mix all that great with a fairly dark light and my camera. So, sorry in adavance for the poor quality. Anyway, I photographed a few funny paintings. Watch out, it may contain saucy contents: https://lyse.isobeef.org/siegfried-wagner-farrenstall-2025-03-15/.

@eapl.me@eapl.me @bender@twtxt.net @prologic@twtxt.net Not including a photo was a stupid move, sorry. There you go:

Image

This particular one is 95mm wide and 185mm high. Fairly compact.

I can only use it figure out distances to other dates and to do some basic calendar math. I’m not able to actually schedule anything. But I grew up with a month calendar like you have there where all appointments of the entire family was recorded.

By far most of my paper use is drawing random stuff on scratch paper during meetings. :-D

Image

@prologic@twtxt.net oops, I’m sorry to see disagreement leading to draining emotions.

It remind me a bit of the Conclave movie where every part wanted to defend their vision and there is only a winner. If one wins the other loses. Like the political side of many leaders and volunteers representing a broad community. I don’t think that’s the case here. Most of us (in not all) should ‘win’.

I can only add that isn’t nice to listen that ‘my idea and effort’ is not what the rest of the people expect. I personally have a kind of issue with public rejection, but I also like to argue, discuss and even fight a bit. “A gem cannot be polished without friction, nor a man perfected without trials,” they say.
This exercise and belonging to this community also brings me good feelings of smart people trying to solve a human and technical problem, which is insanely difficult to get ‘right’.

I genuinely hope we can understand each other, and even with our different and respectful thoughts on the same thing, we might reach an agreement on what’s the best for most people.

Good vibes to everyone!

(#6gfpeea) @lyse@lyse Sorry I didn’t mean to upset you or anyone here in the community. I am/was merely trying to solve what I perce …
@lyse @lyse.isobeef.org Sorry I didn’t mean to upset you or anyone here in the community. I am/was merely trying to solve what I perceive to be a problem and an ask in the community:

How do I know what a hash refers to?

I believe the reason for this stems from a curiosity of the user of whether they might … ⌘ Read more

@prologic@twtxt.net We can’t agree on this idea because that makes things even more complicated than it already is today. The beauty of twtxt is, you put one file on your server, done. One. Not five million. Granted, there might be archive feeds, so it might be already a bit more, but still faaaaaaar less than one file per message.

Also, you would need to host not your own hash files, but everybody else’s as well you follow. Otherwise, what is that supposed to achieve? If people are already following my feed, they know what hashes I have, so this is to no use of them (unless they want to look up a message from an archive feed and don’t process them). But the far more common scenario is that an unknown hash originates from a feed that they have not subscribed to.

Additionally, yarnd’s URL schema would then also break, because https://twtxt.net/twt/<hash> now becomes https://twtxt.net/user/prologic/<hash>, https://twtxt.net/user/bender/<hash> and so on. To me, that looks like you would only get hashes if they belonged to this particular user. Of course, you could define rules that if there is a /user/ part in the path, then use a different URL, but this complicates things even more.

Sorry, I don’t like that idea.

(#ajlefua) @xuu@xuu Um sorry?! A “smart” toilet?! 🤦‍♂️
@xuu @txt.sour.is Um sorry?! A “smart” toilet?! 🤦‍♂️ ⌘ Read more

@bender@twtxt.net Sorry to disappoint (again): https://blogs.nasa.gov/planetarydefense/2025/02/24/latest-calculations-conclude-asteroid-2024-yr4-now-poses-no-significant-threat-to-earth-in-2032-and-beyond/

@andros@twtxt.andros.dev yeah, sorry I couldn’t get back to you sooner. I’ve already made an account on codeberg in order to file in an issue but, I just can’t get myself to concentrate with everything going on with the family lately. I’ll do my best and get things done properly and soon

@arne@uplegger.eu @eapl_en@eapl.me I’m sorry if I don’t respond to a reply. I don’t have a notification system for mentions at the moment. The work is manual!

Very sunny 16°C, heaps of people outside. As soon as we were a bit further into the forest, we had it completely for us. From the foot we thought that the view might be rather good, but up at the summit, it turned out to be very hazy. Oh well. Surprisingly, I found four skyrocket sticks in premium quality. More than after New Year! Also, we came across two deer. It was a very nice two hours walk. No photos, though, sorry.

I don’t think so, at least the tests I did passed. If you’re pretty sure it’s a bug, please create an issue in the repository with the specific case and I’ll investigate it.
There are 2 buttons to make replicas, one makes a replica in the thread where the twt is located (this is the one that should be used the most, as it serves a thread), the other creates a replica to a specific twt.
I’ll let you know a bit about the status: I’m just now implementing the thread screen. There you can be sure where you are. It’s a bit confusing right now, sorry. I think the client is still in alpha. When I’ve finished what I’m doing, and the direct message system, I’ll freeze development and focus on creating more tests, looking for bugs and making small visual adjustments.

@arne@uplegger.eu Hi! I love that you’re implementing it! Maybe, when we’re both done, we could test the clients by communicating both.
I don’t think I’m going to be able to help you much, my knowledge of OpenSSL and PHP is not as high as I’d like it to be.
Maybe the OpenSSL version uses SHA-1 by default in PHP. Or that the IV is derived together with the key (not generated separately). But I’m not able to answer your questions, sorry.
I’m invoking the commands directly, without any libraries in between. Maybe that would help you?

I am so sorry Maggie Forest, but I won’t be voting for you for the Ryan electorate. I will continue to vote for and support Elizabeth Watson-Br …
I am so sorry Maggie Forest, but I won’t be voting for you for the Ryan electorate. I will continue to vote for and support Elizabeth Watson-Brown a voice for the people of Ryan who actually gets things done! ⌘ Read more

@sorenpeter@darch.dk Sorry, I realized that shortly after posting. Here’s another attempt to post the images:

Not me… Sorry

The Coming Unfettered Scam Economy
Robert Reich ,  The Chancellor’s Professor of Public Policy at the University of California, Berkeley, and Senior Fellow at the Blum Center for Developing Economies  -  truthdig

_Stephan: I really am sorry, my readers, but I just don’t see any good news trends in the United States. Of course, there are some local good trends happening, but not nationwide. The facts and trends are what they are so I must report them. The American government has been sold t … ⌘ Read more

@aelaraji@aelaraji.com Sorry I’m late! I still have to work on the mention system, I don’t get some of the messages. I’ll look into your case and get back to you shortly 😄
If it’s a problem that ruins your experience, don’t hesitate to create an issue.

Reddit has been complaining about this for years. I am sorry!

I’m not a huge fan of docker. Sorry for the poor screen grab quality, but this is the funniest analogy for “no docker” vs “docker” I’ve come across:

Image

(#7vunqba) @andros@andros What’s the problem sorry? haha 🤣
@andros @twtxt.andros.dev What’s the problem sorry? haha 🤣 ⌘ Read more

Sorry Simba, i had to😭 ⌘ Read more

**> Sorry it appears I have having difficulty understand how to help you.

Please contact Microsoft at aks blah balh balh**
Sorry it appears I have having difficulty understand how to help you.

Please contact Microsoft at aks blah balh balh ⌘ Read more

(#njap3hq) @movq@movq No sadly I didn’t 🤦‍♂️ I’m admitedly not very good at jokes like this (_not even sure what style t …
@movq @www.uninformativ.de No sadly I didn’t 🤦‍♂️ I’m admitedly not very good at jokes like this ( not even sure what style this is sorry!) 😢 ⌘ Read more

@lyse@lyse.isobeef.org oh yeah i forgot to mention i changed the domain to pinktape lol! sorry about that! https://pinktape.girlonthemoon.xyz/

HI SORRY I DISAPPEARED THINGS HAVE BEEN HECTIC AND WILL CONTINUE TO BE HECTIC FOR ANOTHER WEEK

I haven’t read the entire specification, but I think there is a fundamental design problem. Why would someone put an encrypted message on a public feed that is completely useless to everybody other than the one recipient? This doesn’t make sense to me. It of course depends on the threat model, but wouldn’t one also want to minimize the publicly visible metadata (who is communicating with whom and when) when privately messaging? I feel there are better ways to accomplish this. Sorry, if I miss the obvious use case, please let me know. :-)

(#h5hud5a) @aelaraji Fuck sorry!
@aelaraji @aelaraji.com Fuck sorry! ⌘ Read more

(#skcdisq) @bender@bender I still haven’t fixed that rendering sorry 🤣
@bender I still haven’t fixed that rendering sorry 🤣 ⌘ Read more

(#kjw456q) @lime360 Down at the moment due to hardware failure of one of my nodes. I have the spare parts to bring it back online, just need to …
@lime360 @lime360.nekoweb.org Down at the moment due to hardware failure of one of my nodes. I have the spare parts to bring it back online, just need to find the time 😅 Sorry for the inconvenience, I just can’t afford to run the search engine right now on the remaining two nodes 😢😢 ⌘ Read more

(#dq74i7a) @gallowsgryph Sorry to hear that dude 😢 Hope things improve for you! 👌👌
@gallowsgryph @prismdragon.net Sorry to hear that dude 😢 Hope things improve for you! 👌👌 ⌘ Read more

@doesnm@doesnm.p.psf.lt LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the moment, and I forget which one you’re using 🤣🤣

(#5uon66q) @doesnm LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the mo …
@doesnm @doesnm.p.psf.lt LOL sorry which client are you using? 🤔 You can of course have a say! There aren’t that many active/used clients at the moment, and I forget which one you’re using 🤣🤣 ⌘ Read more

Thanks 😀! @aelaraji@aelaraji.com I am working on a fork now because the new version will break the current code. Therefore, I will upgrade the current repository (https://codeberg.org/deadblackclover/twtxt-el). The original author is helping me with reviews. I am sorry for my long development, I am working in my free time and it is scarce. I will report back to you all. 😋

(#yahtbta) @aelaraji Man I’m sorry to hear this. 😢 Whatever it is you’re going through, things will get better I promise you 🤗
@aelaraji @aelaraji.com Man I’m sorry to hear this. 😢 Whatever it is you’re going through, things will get better I promise you 🤗 ⌘ Read more

Thank you @bender@twtxt.net Much appreciated 🙏 and Sorry you/anyone had to read that…

I’m usually comfortable keeping my hardship to myself, most especially AWAY from the internet; an act of kindness of sorts towards others, “Everyone’s got their own problems to worry about” kind of thing.. But maaan am I starting to believe creating a twitter account would be a healthy decision 🤣🤦 Read nothin’ out there, just a one way echo chamber of sorts to let that shi_ out of my chest. It seem that’s what everyone else’s been using it for all this time.

A Bsky would be even better! 😂 I’d get to shi_ post and yap all I want, allll the way from terminal and never ever have to look back at it or whatever comes out of it. But I digress…

I FU_ing despise this … whatever this is. I wish I could just wake up in some sort of parallel universe where everything is just sunshine and rainbows, alas, life would be just as meaningless.

and sorry you had to read this if you did.

**(#cmttsmq) Ahh fuck! Sorry I was fixing a rule 🤣 This is much better!

proxy-1:~# grep -c 'Bad ASN' /var/log/caddy/caddy.log
2441
```**
Ahh fuck! Sorry I was fixing a rule 🤣 This is **much** better!

proxy-1:~# grep -c ‘Bad ASN’ /var/log/caddy/caddy.log
2441

”` ⌘ Read more

thanks to prologic i now know i can post video here. sorry for bringing idol fancams to this humble network do you still love me

Video

@lyse@lyse.isobeef.org Oh! no need to be sorry and feel free to keep at it if it helps, I don’t mind. It’s just that I’m always on the lookout for corpo-bots and crawlers slipping through the cracks (a fun little game of sorts) 😅 the only thing I let them see is a robots.txt telling them to :diffoff

Also, I’m curious about the invalid lines in my feed. is it something I should lookout for in future?

@andros@twtxt.andros.dev Sorry I missed your messages to #twtxt on IRC. There are people there, but it can take several hours to get a response. E.g. I check it every day or two. I recommend using an IRC bouncer. To answer your question about registries, I used a couple of registries when I first started out, to try to find feeds to follow, but haven’t since then. I don’t remember which ones, but they were easy to find with web searches.

@bender@twtxt.net Sorry if I don’t reply to you. I don’t have any mention notification system… at the moment… Thanks for the suggestion and for fix the error 😄

(#fktqbyq) @kat Yeah sorry but maintaining a mobile app with Flutter became too hard and complicated as the whole mobile ecosystem is just a gia …
@kat @yarn.girlonthemoon.xyz Yeah sorry but maintaining a mobile app with Flutter became too hard and complicated as the whole mobile ecosystem is just a giant PITA 🤦‍♂️ Every new version of Xcode, Android, Flutter, etc… Something would break 😢 ⌘ Read more

(#4dbmmzq) @bender@bender sorry what do you mean?
@bender sorry what do you mean? ⌘ Read more

** Year in review, 2024 **
As a treat, I figured I could write a year in review kinda thing, too. In no particular order here are some reflections organized into some mostly sensical categories.

Since recovering from my brain bleed and the subsequent repair procedures, this year I’ve enjoyed getting back into a routine of exercising. I’ve never been one to track numbers, or reps, or distances — I mostly exercise because I enjoy doing it. This year I got back into going for regular short runs, very long walks (sorry aging d … ⌘ Read more

(#mfddciq) @movq Ahh (sorry ignore my previous Twt); Any way to optimize the no. of BIOS calls? 🤔
@movq @www.uninformativ.de Ahh ( sorry ignore my previous Twt); Any way to optimize the no. of BIOS calls? 🤔 ⌘ Read more

Thanks @bender@twtxt.net for the feedback. I fixed and expanded the article. I’m sorry for my poor interaction. Furthermore, I’m reading and writing while programming a client in Emacs.

sec-t 2024
[This has been in my draft folder since September. Sorry! It’s been a
few months with ups and downs, mostly downs. Energy to spend time on
blogging has been low. Hell, energy to do much of anything has been
low. I’m trying to clean out the drafts folder and will post more
stuff.]

I attended the security conference sec-t 2024 in Stockholm the other
week. I held a presentation during the Community Event, Wednesday
September 11: “Verifying the Tillitis TKey”.

The TKey uses a novel way of helpin … ⌘ Read more

(#4bxggqa) @bender@bender Can’t say I have sorry 😔
@bender Can’t say I have sorry 😔 ⌘ Read more

WiseTech’s Richard White says he’s ‘truly sorry’ as company cuts guidance
In a pre-recorded message, the billionaire said the past two months had taken a significant toll on his family and loved ones. ⌘ Read more

(#q3fjlbq) @wbknl@wbknl You of all are the most affected as our newest member of my pod and most recently joined. I’m so sorry 😢
@wbknl You of all are the most affected as our newest member of my pod and most recently joined. I’m so sorry 😢 ⌘ Read more

(#pt35qpq) @eldersnake sorry I meant to get to this today, please remind me to elaborate on this position a bit more later but I think it’s othe …
@eldersnake @we.loveprivacy.club sorry I meant to get to this today, please remind me to elaborate on this position a bit more later but I think it’s otherwise pretty rubbish ⌘ Read more

I am so sorry.

I am so sorry.

(#fmnhewq) @bender@bender Sorry forgot the | html filter. Rebuilding…
@bender Sorry forgot the | html filter. Rebuilding… ⌘ Read more

(#lci25ga) @asquare I’m not really sure I understand sorry. Can you explain it like I’m 5? 😅
@asquare @asquare.srht.site I’m not really sure I understand sorry. Can you explain it like I’m 5? 😅 ⌘ Read more

(#6efpbga) @aelaraji No need to be sorry 🤗
@aelaraji @aelaraji.com No need to be sorry 🤗 ⌘ Read more

Sorry. I went on a 4 day holiday and my router barfed.

@movq@www.uninformativ.de i’m sorry if I sound too contrarian. I’m not a fan of using an obscure hash as well. The problem is that of future and backward compatibility. If we change to sha256 or another we don’t just need to support sha256. But need to now support both sha256 AND blake2b. Or we devide the community. Users of some clients will still use the old algorithm and get left behind.

Really we should all think hard about how changes will break things and if those breakages are acceptable.

@movq@www.uninformativ.de i’m sorry if I sound too contrarian. I’m not a fan of using an obscure hash as well. The problem is that of future and backward compatibility. If we change to sha256 or another we don’t just need to support sha256. But need to now support both sha256 AND blake2b. Or we devide the community. Users of some clients will still use the old algorithm and get left behind.

Really we should all think hard about how changes will break things and if those breakages are acceptable.

@doesnm@doesnm.p.psf.lt Sorry I meant twet 🤦‍♂️

Sharing the comments of the poll (anonymous so I have no idea whom the comments are from):

your poll should include questions about markdown. personally i think inline bits like style, links, images are yes. block quotes, code blocks, bullet lists are mid. but tables and footnotes are no.

Yes sorry about this, I wasn’t able to change much after publishing the poll 😅

Sorry but i dont undestand b. New feed author? But why?

@bender@twtxt.net

Sorry, you’re right, I should have used numbers!

I’m don’t understand what “preserve the original hash” could mean other than “make sure there’s still a twt in the feed with that hash”. Maybe the text could be clarified somehow.

I’m also not sure what you mean by markdown already being part of it. Of course people can already use Markdown, just like presumably nothing stopped people from using (twt subjects) before they were formally described. But it’s not universal; e.g. as a jenny user I just see the plain text.

@prologic@twtxt.net I don’t trust Google with anything, sorry, pass. Oh, and you need to sign in on your Google Account (or whatever they call it these days).

Speaking of AI tech (sorry!); Just came across this really cool tool built by some engineers at Google™ (currently completely free to use without any signup) called NotebookLM 👌 Looks really good for summarizing and talking to document 📃

@prologic@twtxt.net sorry but nope. Neither jenny, nor yarnd supports it at all. This was treated as a thread because I picked one of @falsifian@www.falsifian.org’s twtxts (with the “old subject”), and replied to it (hence starting the thread).

@lyse@lyse.isobeef.org Sorry, I don’t think I ever had charset=utf8. I just noticed that a few days ago. OpenBSD’s httpd might not support including a parameter with the mime type, unfortunately. I’m going to look into it.

@jmjl@tilde.green howdy! Sorry for mistaken you with https://blog.nfld.uk/ (jlj), but glad to connect. Cheers!

@bender@twtxt.net Sorry, trust was the wrong word. Trust as in, you do not have to check with anything or anyone that the hash is valid. You can verify the hash is valid by recomputing the hash from the content of what it points to, etc.

@movq@www.uninformativ.de Thanks! Looking forward to trying it out. Sorry for the silence; I have become unexpectedly busy so no time for twtxt these past few days.

@prologic@twtxt.net Sorry, my messages don’t get included in the current convo unless I tag you. Guess something gets lossed in translation with this weird posting issue. ANYWAY, it is rather perplexing. Clearly only an issue on my Pod, but what could the source of it be 🤔

Yeah sorry just realised, but just checked again and the referrer is the same (/post) on either the POST or the GET 🤔

Haha, yeah sorry about that, I wasn’t even trying to nuke the database either but it worked out that way 😩

Sorry. I don’t understand what you’re talking about.

Room Code
⌘ Read more

I don’t see him Sorry

Hey @sorenpeter@darch.dk, I’m sorry to tell you, but the prev field in your feed’s headers is invalid. 😅

First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.

For reference, the prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html

[Fixed] Feedback Form Wizard
The Feedback Form Wizard
has been fixed so that it can now, once again, create the CAPTCHA versions (ReCAPTCHA and hCaptcha) of the script.
Apparently, somewhere along the line, I seem to have broken it during one of my internal updates. I’m very sorry
for the inconvenience. Note: you do not have to recreate your script if you successfully generated it before.
(The problem was that under certain conditions, the wizard choke … ⌘ Read more

xkcd Phone Flip
⌘ Read more

I’m curious. How many people truly believe blockchain social networks are the future?

NFTs, tokens, monetization, revenue…

I’m sorry, but how are your random social media blabbers worth any money?
Unless you’re Shakespeare or Einstein or some philosophical or scientific genius, I don’t see why anyone would want to read your posts, let alone cash out some “crypto” from some “wallet”.

And that applies to most people. Sure, your lifestyle and your thoughts may be interesting. But who’s going to start paying to view what’s going on in your life?

As if likes, upvotes, hearts, and subscriptions weren’t narcissistic enough, let’s make people think someone wants to pay them with crypto to view their random posts online.

Sorry about the Panthers.

I will release the sourcecode for the desktop client tonight. I will put it on github (sorry to anyone who prefer other places), but the reason is that I do not want my own git to be open for public. So I’ll put it on github where I have all my other public projects. I have to write the readme, then add some info on the login page (link to source etc), then it’s ready to release with the current features. I then hope others will give it a try and use it if they want :) I also have many other features I need to implement, but all the main features that makes it usable has been implemented, so I’m very pleased with it (And I use it all the time now).

I played around with parsers. This time I experimented with parser combinators for twt message text tokenization. Basically, extract mentions, subjects, URLs, media and regular text. It’s kinda nice, although my solution is not completely elegant, I have to say. Especially my communication protocol between different steps for intermediate results is really ugly. Not sure about performance, I reckon a hand-written state machine parser would be quite a bit faster. I need to write a second parser and then benchmark them.

lexer.go and newparser.go resemble the parser combinators: https://git.isobeef.org/lyse/tt2/-/commit/4d481acad0213771fe5804917576388f51c340c0 It’s far from finished yet.

The first attempt in parser.go doesn’t work as my backtracking is not accounted for, I noticed only later, that I have to do that. With twt message texts there is no real error in parsing. Just regular text as a “fallback”. So it works a bit differently than parsing a real language. No error reporting required, except maybe for debugging. My goal was to port my Python code as closely as possible. But then the runes in the string gave me a bit of a headache, so I thought I just build myself a nice reader abstraction. When I noticed the missing backtracking, I then decided to give parser combinators a try instead of improving on my look ahead reader. It only later occurred to me, that I could have just used a rune slice instead of a string. With that, porting the Python code should have been straightforward.

Yeah, all this doesn’t probably make sense, unless you look at the code. And even then, you have to learn the ropes a bit. Sorry for the noise. :-)

Towed Message
⌘ Read more

❤️ 🎶: I′m Sorry by AILEE

*sorry: connection

Biology vs Robotics
⌘ Read more

“sorry dude, you have vingean uncertainty over the EA community”

Sorry, not a big conspiracy fan. I don’t like conspiracy theories.

@darch@neotxt.dk @prologic@twtxt.net thanks for looking into this, and sorry for not getting back to you on it sooner (busy week)..

@lyse@lyse.isobeef.org, hey, thank you! :-) Yeah, I am abusing the headers on ferengi.one, sorry about that. Will change it. You know, because Lyse.

2045
⌘ Read more

Microsoft apologizes for Windows, returns to DOS
“We’re really sorry about that whole GUI thing.” ⌘ Read more

Ronald Reagan shooter says sorry for wounding former president and injuring 3 others
The assassination attempt paralysed Reagan’s press secretary James Brady, who died in 2014. It also wounded a police officer and a Secret Service agent. ⌘ Read more

❤️ 🎶: miss you more, I’m sorry by Lee Yejoon

@quark@ferengi.one Fixed the “Enter” key issue, sorry about that. I’m dumb 🤦‍♂️ Also I hate Javascript! 🤬

@prologic@twtxt.net sorry about the spelling mistakes. English is my third language.
Also I didn’t mean to question the vision as such.
Just ment a mobile up that pulls in files directly from the users follow list would line up better with the idea of decentralizing personal data. Since not everyone will be running a pod, but most everyone can have a public facing folder. Specially now with services like Skynet coming online.
Sorry hope I didn’t offend you too much.

Sorry if anyone saw my last Yarn here… I deleted it, I was wrong. Looks like everything is encrypted attachments phew but my other concerns above still stand.

Maybe I should write down my political views and thoughts in extra posts on my German blog in the future, instead of putting them in the monthly review and then translating them as well. English readers probably won’t get much out of it… Sorry! ✌️ ⌘ Read more