Mario (bcd06115) at 26 Mar 21:40
hubwall: fix php error
Mario (079252cb) at 26 Mar 20:51
hubwall: fix php error
Mario (30a7b3fb) at 26 Mar 17:57
pageheader: use construct_page hook to make sure the header is alwa...
Mario (7e0d3d12) at 26 Mar 17:55
pageheader: use construct_page hook to make sure the header is alwa...
Mario (1d8f14ca) at 26 Mar 09:54
Merge branch 'master' of https://framagit.org/hubzilla/addons
Mario (1d8f14ca) at 26 Mar 09:46
Merge branch 'master' of https://framagit.org/hubzilla/addons
... and 4 more commits
Mario (797ff396) at 26 Mar 09:44
we are defaulting to Note again for now
Mario (b3f8f828) at 25 Mar 17:21
do not sign or try to sign wall to wall posts
Mario (9542aeb3) at 25 Mar 17:21
pubcrawl: sign messages with author key if available, if signed wit...
Mario (2af8d6e8) at 25 Mar 17:04
do not sign or try to sign wall to wall posts
Mario (6af9f134) at 25 Mar 16:36
pubcrawl: sign messages with author key if available, if signed wit...
Hubzilla 9 has changed how Pubcrawl works: By default, everything goes out as an Article-type object now. A switch can restore the old behaviour, namely everything going out as a Note-type object.
Now, Mastodon handles Note-type objects like native toots. But when it receives an Article-type object, it does not show its content at all. Instead, it shows the title, then the summary, then a link to the original, finally the hashtags. This is by design, fully intentional and absolutely justified; it shall prevent massive blog posts from appearing in Mastodon users' timelines at full length.
But this behaviour does not work well with comments from Hubzilla. Comments can neither have a title nor a summary, and frankly, they shouldn't because they're comments, so they only appear as links with nothing describing or announcing them. Likewise, it doesn't make sense for them to only appear as links on Mastodon, even less when they're comments on Mastodon toots.
The only alternative currently is to switch everything back to being Note-type objects. But to be honest, long, blog-style posts work much better and cause much less trouble on Mastodon as Article-type objects that are only announced as links.
Currently, the only way to have the best of both worlds is to always have the Pubcrawl settings page open and flick that Article/Note switch back and forth. This is rather inconvenient.
Thus, my suggestion is to turn this one switch into four switches:
The default settings would make Hubzilla mimick Friendica's behaviour: Friendica always sends everything as an Article-type object if it has a title and as a Note-type object if it doesn't have a title.
Friendica has a nifty, while probably undocumented feature: Posts with a title go out via ActivityPub not as Note objects (= microblogging posts), but as Article objects (= long-form blog posts). Posts without a title still go out as Note objects. So adding a title changes as what kind of object a post goes out.
This has a certain advantage on ActivityPub-based microblogging projects, actually including Mastodon: If they understand Article objects, they may display them differently from Note objects, taking the usually greater length and more advanced formatting and styling of Article objects into consideration.
Mastodon, for example, handles Article objects by only showing the title with a link to the post at its origin. And it does so with Friendica posts which have a title.
The advantage of this is that Mastodon users can see the article in its original formatting, with all images in place and in an environment where they do expect posts that are longer than 500 characters.
Hubzilla, on the other hand, always sends all posts as Note objects. Projects like Mastodon show them the same way as they show microblogging posts, regardless of length. They show walls of text of thousands or tens of thousands of characters, disturbing Mastodon users who are only used to 500 characters per post. And they rip all images out of their context because they don't know image embedding and convert them into file attachments, only the last four in Mastodon's case.
Currently, the only way on Hubzilla to circumvent this is to install the Articles app, write long posts as articles and then manually write posts with links to these articles. At the same time, there is no way to keep normal Hubzilla posts from showing up in timelines on Mastodon and other ActivityPub-based microblogging projects at full length.
If Hubzilla did as Friendica does, if Hubzilla sent posts with titles as Article objects, ActivityPub-based projects could handle them accordingly and would no longer show them as gigantic microblogging posts. Mastodon specifically would link to them.
This would make it possible for Hubzilla users to make full use of Hubzilla's post design and formatting features and write them as long as they want without having to worry about how they appear on Mastodon & Co.
The most basic implementation of this would be an automatic switch.
However, at the very least, I'd add a general, channel-wide setting that either opts into or out of this feature for those who want to keep Hubzilla's current behaviour.
A more advanced implementation could additionally have a per-post switch between Note and Article which is always present but greyed out when the title is empty. When the automatic Article object feature is on, this switch is active and on if there's a title; it can be turned off. When this feature is off, and there is a title, the switch is active and off, and it can be turned on.
Now that Hubzilla 9 is out and has introduced a switch for all content whether it always goes out as Note-type or Article-type, I'd like to see this implemented differently. Hence, I'll close this issue and open a new one.
Mario (49d85fe8) at 22 Mar 08:42
Merge branch '9.0RC'
Mario (b83a3ec3) at 21 Mar 21:19
we need to run bbcode again to catch possible unencrypted content. ...
Mario (a42a8ada) at 21 Mar 20:50
fix issue where the second single quote will not be printed if the ...