Post @post@social.cleverlibre.org

@filippo

In fact Mastodon has been successful because it focused more on UI/UX than GNU Social etc, for sure.

But I am still convinced that making people aware is the only way to establish a perpetual virtuous circle.

@boris @ednico

Not sure of what you mean, but even though it currently has rough edges, Logseq publishing feature is meant to ship the whole Logseq that runs entirely in the browser: it loads a DB, read data from it and update the content of the page accordingly. This enables feature like search and queries being evaluated live.

If you are looking for exporting content as many HTML pages and a bit of JavaScript, that would be a totally different thing, perhaps desirable for some use cases, but it would be a huge effort.

At the moment there are plugins to export content to other platforms like Hugo, maybe this approach could be gradually improved by supporting more and more Logseq features and plugins without Logseq core.

@daviddelven @andric

Of course Logseq is not supposed to be used only with Datalog by design: that is just an additional feature for more advanced users (and indeed they are called "Advanced Queries").

There are already Simple Queries but they plan to ship a graphical Query Builder.

There is a huge difference in laying solid foundations for a highly flexible *tool* and build a *product* around a good intuition or two.

I definitely see Logseq shipping a Query Builder and other features by Tana in some months, while I can't say the same with Tana becoming FOSS and local or even just supporting Markdown, PDF annotations, whiteboards, plugins etc.

@daviddelven @andric

I prefer Logseq, Free and Open Source Software, open formats and protocols, local files and offline-first, especially when it comes to personal data.

I consider Tana Inc. as an unofficial R&D department and Tana as a nice experiment but nothing too serious :-)

@filippo

Google and other corporations develop standards everyone can adopt, the Web ones for example, so this model is feasible.

But for other things they preferred to build silos and remove protocols they used to support. I don't pretend they reimplement every new feature by extending the standard first, but at least keep what was working, like simple plain text messages in XMPP.

Not to mention what Google did with RSS: what Google News provides today is anything that a RSS reader can't do.

They do what suits them like anyone else, the problem is when they have so much power that the user of the service has no more way to protest, for example by switching to the competition.

They are welcome to join the Fediverse, but people should take the chance to move away from them more easily because the Extinguish phase would eventually arrive for everyone.

@filippo

What if it happens like with Google and Facebook with XMPP?

@daviddelven @andric

I know but that was not the point.

The relation Authorship could be defined as a protocol implemented by two instances that play the role of author and work respectively.

For example a Theorem could have a Name, a Book could have a Title and to implement the role of work you need something with a Name or a Title.

A convenient way to do so is Theorem/Book both implement Authorship protocol (as work) by passing their Name/Title as the name of the work.

This is just an example but as the schema grows situations like this could become a mess to manage.

@daviddelven @andric

In Tana you would have for example the superclass Person and the subclass Author, the latter can be used as value for the Author key of Books, Quotes etc.

All authors are persons but things like this can get complicated, what if later you want an organization to be an author too?

In POP you would have Person that implement the role of Author in the relation of authorship.

Later you let Organization implements authorship on its own.

@elipariser

To be clear, being a AP network means you can use a Mastodon account to comment a PeerTube video.

Imagine if YouTube channels appeared on Twitter as native Twitter accouts, new videos appear as tweets by those channels and when you comment the tweet it appears as a comment also on YouTube.

This is what happens with Mastodon and PeerTube and to some extent also with other platforms.

@elipariser

ActivityPub is like SMTP and IMAP but for things you usually find in social networks. Mastodon implemented the server-server protocol (~SMTP) to make its Twitter-like instances federate together and with other implementations of AP (YouTube-like PeerTube, Reddit-like Lemmy, Instagram-like PixelFed and so on).

Mastodon introduced its own client-server protocol that makes Mastodon clients basically browsers. Indeed all the logic is on the server and clients are used just to provide a native UI.

Instead AP client-server protocol assumes more logic for the clients and this didn't fit Mastodon clients use case.

@daviddelven @andric

Instead of starting with classes and then define their relations, start with relations and model them as "protocols", then objects play roles defined in those protocols.

Instead of building a complex structure of classes, let them freely implement protocols. You can, for example, extend protocols, so you structure protocols instead of classes. This is supposed to be a more flexible approach.

@naciketas@mastodon.uno @cicciocappuccio

Quindi ammetti che il cartello dice semplicemente una cosa che si sapeva già?

@naciketas@mastodon.uno @cicciocappuccio

Lo hai letto l'articolo? Guarda che non smentisce, ma dice "si sapeva già".

@andric

FYI #Logseq is like #Roam but it is developing options to define a schema.

About #Tana, #OOP is a mess for development, I wouldn't use that for note taking too.

It would have been better if they developed something more in the lines of #ProtocolOrientedProgramming.

@tonch @xpil@fosstodon.org @jinxd

Try #Logseq, you can use it at the same time with Obsidian on the same "vault", but it's FOSS.

@ednico @boris

For me it would be a huge improvement if the functionalities that are not supposed to work were disabled, like the editing ones.

And support for plugins.