Skip to main content


in reply to Anae

La imagen muestra la portada de un libro con un fondo rojo vibrante y un borde dorado con diseños geométricos tradicionales chinos en las esquinas. En el centro, hay un símbolo circular dorado que recuerda a un diseño de Feng Shui. El título del libro, en letras blancas, dice: "STOP BLAMING OTHERS FOR YOUR UNHAPPINESS" (Deja de culpar a los demás por tu infelicidad). Debajo del título, en letras más grandes, se lee: "LEARN FENG SHUI AND BLAME YOUR FURNITURE INSTEAD" (Aprende Feng Shui y acusa a tu mobiliario en su lugar). El autor del libro es Hu Mai, y la traducción es de Cliff Pollard. El diseño y el texto sugieren un enfoque humorístico y ligeramente satírico sobre la práctica de Feng Shui.

Proporcionado por @altbot, generado de forma privada y local usando Ovis2-8B

🌱 Energía utilizada: 0.231 Wh



Efforts to Reduce Toxic Algae in Lake Erie Appear to Be Making Progress. Now They Face State and Federal Cuts
https://insideclimatenews.org/news/20072025/lake-erie-toxic-algae-control-cuts/?utm_source=flipboard&utm_medium=activitypub

Posted into Latest News @latest-news-InsideClimate



TSMC to start building four new plants with 1.4nm technology: taipeitimes.com/News/front/arc…
#hardware #cpu #gpu #tsmc


in reply to Alessandro Gaziano

L'immagine mostra una collina verde e fiorita sotto un cielo azzurro con nuvole bianche. La collina è ricoperta di erba e fiori selvatici, tra cui gialli e bianchi, che creano un paesaggio pittoresco. In lontananza, si possono vedere le funivie che si snodano lungo la collina, suggerendo che si tratta di una zona montana. Il cielo è sereno con nuvole bianche che si stagliano contro il blu intenso, creando un contrasto vivido. L'atmosfera è tranquilla e naturale, con un'ampia vista che si estende fino all'orizzonte.

Fornito da @altbot, generato localmente e privatamente utilizzando Ovis2-8B

🌱 Energia utilizzata: 0.223 Wh



You Should Learn Markdown thelinuxcast.org/posts/2025/yo…
in reply to ZeStig

We should actually get rid of #Markdown. 😉

It is one of the worst lightweight markup languages you can decide for except for adoption: it's bad with respect for learning, for typing manually and for processing.

Avoid the Markdown flavor hell and go for any other #LML that doesn't come with all the downsides.

#orgdown, the syntax of #orgmode is one of the examples where the downsides of Markdown are avoided.

Please, don't settle for a mediocre solution again.

This entry was edited (5 months ago)
in reply to Karl Voit

Out of curiosity, if you dislike markdown that much, why do you want to name the org ML after it ("orgdown"), which makes it sound like it's just yet another variant of markdown? That only causes confusion. Why wouldn't you want it to be clear that org ML is a distinct LML of its own?
in reply to Lea

Good question.

If you got the point of view of somebody very familiar with org already, you might think that way. However, that's not the majority and certainly not the most important target group I want to address.

My motivation was to promote this LML among the general public. Here, you should actually use the broad adaptation of Markdown so that the phrase "down" resembles memories to that particular thing.

So for somebody who has used Markdown in the past, #orgdown makes it way easier to explain or nudge, what orgdown actually is.

So I prioritized familiarity over distinction in order to make it more popular in a faster fashion.

After all, for non-experts, the actual differences between MD and org are quite small when you start with this LML in the first place.

Related: karl-voit.at/2021/12/02/Orgdow…

YMMV

in reply to Karl Voit

I think people who are not already familiar with emacs/org-mode (i.e. the majority), their reaction would be, "oh no, yet another variant of markdown. Not interested, I want to stick to the closest to standard as possible and not introduce even more incompatibilities with my tool chain."
in reply to Lea

Well, I don't think this is the case but we'll probably never know. Orgdown is far from there, even in the org community. So it'll stay my personal hobby to promote this great idea.

If the idea will die just because of the name, it's probably not worth following it anyhow.

in reply to Karl Voit

I guess that's up to you, whether you consider sticking with the name as more important than the idea. Good luck anyway. Personally I will never use that name for it.
in reply to Lea

That's the same the other way round: if you fight this great idea just because you would have chosen a different name, your motivation is maybe a difficult one to understand. 🤷

Sad to read that you would rather see the Org-mode syntax stay in its geeky niche instead of becoming a mainstream option as LML. 😔

in reply to Karl Voit

I thought the format itself was just "Org". GNU Emacs's org-mode being one implementation for it.
in reply to tusharhero

Unfortunately, "org" as well as "org-mode" is used for both: LML syntax and the Elisp implementation. Therefore, it's no use in using that for LML term only.
in reply to thelinuxcast

This discussion was not about using Emacs.

It was about a LML which is supported by a range of tools. If you don't want to use Emacs, that's perfectly fine.

However, if you're looking for a great syntax for your notes and documents, consider #orgdown, the the syntax of #orgmode.

in reply to Karl Voit

AFAIK OrgMode exists in its full glory only in Emacs. That means when you mention OrgMode you implicit the usage of Emacs. @thelinuxcast @zstg
in reply to Konafets

Well, this is exactly the kind of misunderstanding why I tried to coin the term #orgdown: karl-voit.at/2021/11/27/orgdow…

We were talking about a syntax to write down simple text, comparable to other lightweight markup language (LML) such as Markdown.

You are talking about tool-support for the syntax of Org-mode which originates in a specific tool called Emacs.

Those are two completely different things because you can use orgdown in many tools that are not Emacs and this is actually a perfectly good idea: gitlab.com/publicvoit/orgdown/…

In this discussion, Emacs should not have a dominant position at all. Use the Org-mode syntax with any tool you like. After all, that's the purpose of LMLs in the first place. 🤷

in reply to Karl Voit

Of course I can write text in any format in any text editor and will end up having Latex/OrgMode/Perl/whatever in Notepad and can do what exactly with it? Nothing, its just text w/o any meaning to the computer and therefore w/o any support. But OrgMode (as any other format) makes only sense with tool support, bc otherwise there is no need for a specific format.
And OrgMode comes to life, when my todos get picked up by the agenda or I can tangle my literate configuration.
in reply to Karl Voit

And this only exists in Emacs. I did not even found a feature complete interpreter of OrgMode which works outside of Emacs.

> However, there were many misunderstandings in the aftermath of my article. In many online discussions, people did not seem to be able to differ between the Elisp code and the design of the markup language.

Yeah, bc all higher benefits of OM comes only in combination with Emacs and there is no need to learn another ML with bad tool support outside of it.

in reply to Konafets

I disagree.

In my business life, we generate documents (via Gitlab CI) on the server. What editor you're using doesn't matter for the process - just for personal taste.

I did write tons of tools whose stdout output was in #orgdown, which then got processed by other tools, mostly not related to Emacs at all.

You can write your mail in orgdown syntax as a convention - one of the initial purposes of #LML.

So we have a clear disagreement on the usefulness of LML outside one particular tool.

Of course, *if* you're using orgdown and *if* you want to optimize tool support, you are perfectly fit with using #Emacs for that. 👍

But keeping that as some sort of mantra (Org-mode syntax only(!) makes sense within Emacs) and not because this LML is well-designed for being typed by hand, processed by a broad range of tools, easy to learn, ... that's a pity in my opinion and doesn't do justice to this great syntax we have at hand.

YMMV.

in reply to Karl Voit

You write post-processing tools for your OM stdout. Thats cool!

You have an academic POV on OM as "die reine Lehre", but missing the perspective of those who just want to use a format w/o fiddling with it, extending it or building the lang support by themself.

in reply to Konafets

A regular user just wants to use S/W and in case of an ML it is writing text. They might have a look at the compatibility to other platforms, the adoption rate, the learning curve, the features and how easy it is to bring team oder family members on it. And most of those points are in favour of MD and not OM.
This entry was edited (5 months ago)
in reply to Konafets

I strongly disagree, have lots of arguments and you have to wait until I publish my articles on that.

You'll be surprised, I guarantee. 😉

Another instance of "on Mastodon, you can't discuss such a topic".

in reply to Karl Voit

"I have a lot of (unpublished) article on that topic" just proves my academic POV argument ;-)
in reply to Konafets

Absolutely!

Sounds like a very reasonable argument to me.

😈 🤣 😉

in reply to thelinuxcast

Uhm... I've moved to Emacs exactly to avoid the annoying mess of Markdown "standards", and I'm very happy with Org Mode, and actually even with Emacs,
Even if I know nothing at all of Emacs Lisp. 🤷🏻‍♂️
@publicvoit @zstg
in reply to thelinuxcast

as a language, Org is just as usable as Markdown is. Imho it's up to the "environment" you're using to implement proper support. GitHub and GitLab render Org just as well as Markdown. Org is also just as easy as Markdown is.

It's just that several Org niceties (interactive notebook execution etc) work OOTB inside Emacs. Emacs is not a strict requirement.

CC: @publicvoit

in reply to ZeStig

Absolutely.

#orgdown = the name for the syntax of Org-mode which can be used anywhere and which got great support outside of Emacs just as #Markdown has support outside any MD tool you name including pandoc.

#orgmode = Elisp implementation to Support note-taking (and much more) with a #LML named orgdown in (GNU) Emacs with highlighting and modification features.

Background:
karl-voit.at/2021/11/27/orgdow…
gitlab.com/publicvoit/orgdown/

And my current main article on that:

Org Mode Syntax Is One of the Most Reasonable Markup Languages to Use for Text
karl-voit.at/2017/09/23/orgmod…

I'll publish an article on the many downsides of Markdown in a few weeks. You might want to add my blog feed to your RSS aggregator.

in reply to Karl Voit

I've noticed your "Orgdown" stuff in passing before, but not thought much about it.

I tend use Org markup in larger, more complex emails for instance and other shared documents. It seems natural to me. In fact I've had a few replies that copied what I'd done. Definitely not from Emacs org-mode users.

But, actually defining a simple Org markup not directly connected to Emacs, but just a better general markup still compatible with Emacs I think is a great idea.

in reply to Andrew Wigglesworth

This is the idea, yes.

Casual, easy to learn and type syntax. If you need more, it can be processed by tools like pandoc and such.

But foremost, it's for humans.

in reply to Karl Voit

Did you produce a document introducing Orgdown (Org syntax)?

It's something I'd be very interested in promoting in my various organisations and interactions.

in reply to thelinuxcast

Another Nobody here. I started using emacs specifically for org mode and very happy with it. Not just the syntax, but everything about it. I use it for writing, not programming.
in reply to Lea

I didn't meant to be offensive.

Just mostly nobody uses emacs. It's a very small niche. Even amongst markdown users. At least I think so.

in reply to thelinuxcast

I agree.

Therefore, the idea of a good LML is way more important than Emacs.

However, the right choice of a LML is therefore more crucial than choosing the right tool-support.



Le réel se réduit à ce qui est indexé, cartographié, scoré.




Saint-Pierre (La Réunion) : « Loi Duplomb = loi poison »
attaque.noblogs.org/post/2025/…

"Extrait de Zinfos974 / vendredi 18 juillet 2025 Des tags hostiles à la FDSEA sont apparus dans la nuit de jeudi à vendredi sur les murs de son siège à Saint-Pierre. Le syndicat agricole est pris pour cible en raison … Continuer la lecture →"





Abu Dhabi talks between Azerbaijani and Armenian leaders were constructive – Aze.Media byteseu.com/1211690/ #Armenia #RepublicOfArmenia




#Teufel hat mit #MYND Bluetooth-Lautsprecher als #OpenHardware herausgebracht. 😍 🔈

Mit Preisen ab 230€ relativ teuer aber dafür ein wirklich, wirklich interessantes und offenes Konzept mit allen notwendigen Daten zum Download: teufel.de/mynd-107002004#pdp-s… 📖

Interview mit den Entwicklern: heise.de/hintergrund/Die-Entwi…

Review durch #heise: heise.de/tests/Reparier-und-au… (ausgerechnet das stellt man hinter die #Paywall 🤦‍♂️)

Kritik/Grenzen der Offenheit: heise.de/forum/heise-online/Ko…

Hätte ich mir nicht letztes Jahr Bose #SoundLinkFlex gekauft, würde ich mit das mit Teufel sehr genau überlegen.

Bitte mehr offene Produkte wie sowas!

#Nachhaltigkeit #Lautsprecher #BluetoothSpeaker #Reparierbarkeit #Repairability #unbezahlteWerbung #Werbung

in reply to Karl Voit

die Kritik ist aus oshw Sicht verständlich aber zu erwarten das Hersteller ihre Produktauswahl nach den Gesichtspunkten treffen wird die Menge an verfügbaren Infos eher schmälern.
#OSHWA cert bekommen sie so keines aber es ist schon deutlich besser als bisher

in reply to Thomas

🤣 🤣 🤣 🤣 🤣 🤣 🤣 🤣 🤣 🤣 🤣 🤣 bwahahah awesome!


"This Week in Plasma" brings you windows with rounded corners (which can be made square again if you wish), adjustable sidebars for Discover and System Monitor, and the work in progress to improve KRunner's search results:

blogs.kde.org/2025/07/19/this-…

#Plasma6 #opensource #freesoftware #desktop

9to5Linux reshared this.



Fheroes2 version 1.1.10: github.com/ihhub/fheroes2/rele…
#linux #linuxgaming #update #release #foss #engine #fheroes2