It probably will grow roots if you cut it. See here: https://en.wikipedia.org/wiki/Dracaena_sanderiana#Cultivation

You could also plant it into a real pot.

Do you fertilize the water somehow?

Ich glaube das ist eher eine Halbinsel-Lösung:

Reverse-Kompatibilität: Das Schwalbe Clik Valve kann auch mit normalen SV-Pumpen bepumpt werden.

D.h. du kannst es mit deiner normalen Pumpe verwenden, hast dann aber halt nicht alle Vorteile. Ich könnte mir vorstellen, dass sie vielleicht sogar die “normalen” Sclaverandventil Schläuche aus dem Programm nehmen? Dann hätten sie in ein paar Jahren schon eine recht große Verbreitung.

Aber dann könnten sie natürlich nicht (sehr) viel mehr Geld für das neue Ventil verlangen (?)

hoped to discover a good open source software for collaborative editing, but their solution is based on https://standardnotes.com/

Rich text in the modern world is almost exclusively solved by using markdown because it’s such a trivial solution.

citation needed

markdown is not a trivial solution: there are many different implementations, it’s a barrier for non technical people and it allows you to embed any html, so you need an additional html sanitizer.

my definition of a “rich textbox” is a WYSIWYG field, and markdown does not help you with this?!

yes, you probably would not save the formatted text normalized over multiple database columns, and only use a single field for a the text with formatting embedded in html or another format, and another one with the text without formatting for possible full text search. but even if you would solve this using markdown (which limits you to a quite small subset of text formatting and bad extensibility) you would still need a good data format to store the formatted text in memory that allows you to render the text. and markdown does not help you with this either?!

Never change a running system. Even small changes may have unexpected consequences, if the machine is as complex as our bodies…

90 millions years of evolution, or you: who knows better?

It looks funny on pictures, but i bet everything would go south if you would straighten it out or reorganize it.

If you don’t know the intend why it looks as it currently looks i would not touch it. even if you know why it looks like that and you can somehow compensate those effects, i would not do this on my own body for the first time…

you can not.

just think about it: 80 to 100 years uptime, no reboot, no fall back system, not even a cold spare. and you want to change something while its running? madness! maybe if you are very lucky you may be able to replace some of the internal components… but not to upgrade, only if your on the risk to loose the whole system…

hm. i did not think about serious illnesses when writing my comment. maybe we can specify this as a “not running system”, but i can understand that my first snarky comment could be perceived as rude when you have problems with your body. i fear i walked right in the privileged trap without realizing it?

wenn jemand sehnsucht nach “Server error” hat, kann er folgenden befehl verwenden:

curl --resolve feddit.de:443:194.36.144.161 https://feddit.de/

mit dem passenden eintrag in der hosts-datei sollte es dann sogar auch im browser erreichbar sein.

how would you federate? it comes natural for lemmy to have each community on a seperate server, but how would you do this for a project like dmoz?

i don’t think it would be a good idea that one server could own “art” for example, and no one else could contribute. and on the other side it would not be a good idea if everyone could add sites for “art” as then it’s just a federated wiki? you still would have to fight spam? do all entries in “art” have the same priority? or should there be some voting, or verifying from other instances maybe? but then rough instances could vote for each other?!

how big is the spam problem on lemmy?