Post @post@social.cleverlibre.org

@carl @me @fediverse

And we wouldn't have comments split across multiple unofficial RSS->Fediverse bots as it is now.

Bots connecting different platforms are a waste of energy (and therefore have an environmental impact) when we can instead have open protocols.

@me @carl @fediverse

A good metaphor to be used for UI/UX could be Fediverse users as friends in a room commenting TV shows/news that are RSS/Atom feeds: friends can hear each others' comments but TV is just a one-way communication medium.

@me @ch0ccyra1n @carl @fediverse

Yes, mine was a reference to the concept of *graceful degradation*:

https://www.w3.org/wiki/Graceful_degradation_versus_progressive_enhancement

@carl @ch0ccyra1n @fediverse

Even better if Fediverse servers could treat any RSS/Atom feed as a "degraded" ActivityPub actor and let users subscribe, boosts and comment posts. We would have de facto a comment platform for everything that has a RSS/Atom feed.

@silmathoron @ed_hawkins

I know dynamical systems, if you have something technical to add go ahead.

Please in your next comment include a reply to my question: is this graph intentionally misleading and some kind of metric of the effects should be presented instead?

@silmathoron @ed_hawkins

So are you saying climate "scientists" show catastrophic graphs despite they know the actual effects are toned down?

@bitbonk @nukehavoc

The team doesn't actually care about those feature requests but implements features no one asked for. Indeed that request for longform writings is 1,5 years old and there are not even official statements about it despite it is popular

@fro_vo

REAL SCIENTIST: we don't know

@nukehavoc

Check #Zettlr

https://www.zettlr.com/

It is based on local Markdown files and support wikilinks and tags like Obsidian but it is FLOSS.

@basepair

By using Logseq I learned a lot of things so probably it was worth it.

It takes months to understand how to use Logseq's full potential and indeed there is not a 1:1 replacement. Alternatives miss something.

Suggestion: keep the content of your notes separated from navigation, for example by keeping queries in dedicated pages and not mixed with content. Otherwise you will be much more tied to Logseq. At least now I can browse my notes using any Markdown editor or Zettlr that even support wikilinks.

Maybe we should organize as people that cares about privacy, digital sovereignty and related topics and try to improve Logseq. We could make bounties for features we want to get merged in Logseq or if needed we could promise that we will move our money on OpenCollective to a patched version of Logseq that tracks upstream development (kinda like Bromite with Chromium for Android).

@alfredo_liberal@universeodon.com

FYI the term you are looking for is *demagogy* while *populism* was used in a derogatory way by the aristocracy towards those who promoted democracy.

@basepair

Here there are some pro/con after ~2 years of usage and being a backer:

https://qoto.org/@post/110203051859101115

@science_quotes@c.im

I didn't expect that from Feynman and it is very questionable

@ednico

Thank you for letting me know, are you referring to this part?

"...and not only is mobile not planned yet but the developers want to limit mobile plugins to a library of their own creation..."

I hope OP misinterpreted that statement from devs about making a library of components available to plugin devs before enabling plugins on mobile.

My interpretation is that one will be free to develop plugins with plain JavaScript and CSS but also able to conveniently pick components from Logseq to make plugins look&feel more native.