Mastodawn

Testando replicação do hubzilla para #forte

Vilarejo Pro

Conheça forte, a rede social (apenas ActivityPub) mais rica em recursos. Há uma apresentação de forte aqui:
#^https://text.tchncs.de/5g7uc9lzaz

"Central ao funcionamento de forte e à modulação das relações estabelecidas através desta rede social é o conceito de consentimento. Macgirvin já definiu seu software como “baseado em consentimento” (”consent based”). Na prática, isto significa que, quando você tem um canal na rede forte, todas as formas de interação de outras pessoas com você somente acontecem de acordo com a forma como você previamente consentiu (definiu) que elas pudessem acontecer (e isto podendo ser configurado para contatos específicos). Isto vale para o recebimento de mensagens diretas (DMs), para o recebimento de comentários e likes em seus posts, para a aprovação de comentários em seus posts (quando eles estão condicionados à sua aprovação), para o acesso (visualização) a determinados posts ou arquivos ou fotos. Isto faz com que forte seja uma rede praticamente à prova de spam, assédio e stalking – resolvendo assim inconvenientes que tanto perturbam usuários de redes sociais comerciais (e também de algumas redes não comerciais).
(...)
Privacidade
forte é uma rede social que tem a privacidade e o consentimento na base do seu design. Reunimos aqui tais características e acrescentamos mais uma. Você pode...
1) criptografar o texto das mensagens diretas;
2) estabelecer qualquer data (e horário) para a expiração de um post;
3) desabilitar comentários e likes em posts específicos ou em todos os posts;
4) moderar comentários feitos em seus posts;
5) criar diferentes listas de acesso com suas conexões, para as quais você pode então escrever posts específicos;
6) estabelecer permissões que definem quais pessoas poderão acessar determinados posts, fotos ou arquivos em seu canal;
7) criar múltiplas identidades (canais) em uma conta;
8) usufruir do conceito de post como contêiner de conversa (que possibilita ler todas as participações em uma conversa - participações estas previamente consentidas/definidas por quem fez o post).
9) E, você pode ocultar os seus contatos (o número deles e os nomes) - inclusive, dos seus próprios contatos."

#forte #activitypub #fediverso

forte

_uma rede social não comercial_ _o sistema de comunicação pessoal decentralizado (apenas) ActivityPub mais rico em recursos_ <br> Veja u...

tchncs

Show thread

Jupiter Rowland Jan 17

@silverpill In a hilarious twist of fate, this gives (streams) and Forte an unfair advantage. They're nearly identical, they have the same maintainer, but they're two separate implementations, also seeing as Forte uses ActivityPub for nomadic identity, and (streams) doesn't and still uses its own Nomad protocol for it.

Since Mitra appears to implement (streams)/Forte features one by one and cast them into FEPs, that's three implementations already. Two if nomadic identity via ActivityPub is involved. And if Hubzilla happens to have it, too, we've got up to four implementations.

Yes, ActivityPub is only an optional add-on on Hubzilla and (streams), but an implementation is an implementation. And whatever they do on Nomad that federates has to get out through ActivityPub one way or another.

It'd be even more hilariously skewed, hadn't Mike discontinued the five apps between Hubzilla and (streams) on New Year's Eve 2022.

CC: @slyborg @Evan Prodromou @Connected Places @ArneBab @Alex Chapman

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Hubzilla #Streams #(streams) #Forte #Mitra

Netzgemeinde/Hubzilla

Show thread

Jupiter Rowland Jan 16

@klu9 @Leigh Silvester First of all, Friendica is a Facebook alternative. It was designed as such.

However, it was designed as a better-than-Facebook-itself Facebook alternative with a lot of useful extra features and without a lot of Facebook-typical cruft. And not as an all-out, 1:1 Facebook clone. It was made almost 16 years ago, in a time when a decentralised alternative to something didn't absolutely have to be a nearly identical clone.

Friendica does have groups; there's the official group directory. So does Hubzilla which was made by Friendica's own creator from a fork of a fork of Friendica, so they're similar.

However, groups on Friendica and forums on Hubzilla are a lot different from groups on Facebook, especially if you want to have your own group. On Facebook, groups are a wholly separate feature of their own.

On Friendica, a group is just another account, but configured differently. Likewise, on Hubzilla, a forum is just another channel (on Hubzilla, your identity is not your account and not tied to your login), but, again, configured differently. (streams) and Forte, the two still existing more recent Hubzilla descendants from still the same creator, have groups in much the same fashion as Hubzilla's forums.

Friendica groups are not limited to users on the same Friendica node. In fact, anyone anywhere on Friendica, on Hubzilla, on (streams), on Forte, on Mastodon, Pleroma, Akkoma, Misskey, any of the Forkeys etc. can join Friendica groups and Hubzilla forums and interact with them. Yes, you can join Friendica groups with your existing Mastodon account.

Basically, how they work (within the Friendica/Hubzilla/(streams)/Forte family and with a Mastodon translation) is:

In order to join a group/forum, you request a connection.
(Mastodon: You follow the group account/forum channel.)
Your request is accepted.
(Mastodon: Your follow request is confirmed, and you're followed back.
Now you're a member.
In order to start a new thread, you send a post to the group/forum, but you must mention it in such a way that your post becomes a DM.
(Mastodon: Most of the Fediverse, Mastodon included, doesn't know these special mentions, so Friendica groups and Hubzilla forums accept normal mentions from those server applications that can't direct-mention.)
The Friendica group account/Hubzilla forum channel will automatically be quoted-shared (Friendica)/shared (Hubzilla)/quoted (Mastodon lingo) to all other group/forum members.

If you want to start a new thread in a Friendica group or a Hubzilla forum from Mastodon, which you can, you have to know the order of things, keep it in mind and adhere to it:
Title

@Group mention

Post text

So while Mastodon doesn't officially support titles, at least not when posting, you can give the thread a title by writing it above the mention and the post text below the mention.

A common Mastodon mistake is to first write the post text and then add the mention afterwards. However, if there is exactly one paragraph above the mention, and that paragraph is short enough, Friendica and Hubzilla will treat it as the title. Your start post might end up with a title, but not with a post text.

How exactly groups are handled on Friendica if you're the owner, I can't tell you. The last time I've used Friendica must have been either when Mastodon was still fairly new or even before Mastodon was even made. I've switched to Hubzilla as my preferred daily driver back then and never looked back.

I've read that Friendica has something like secondary accounts which you can attach to your existing account. This way, you can have your personal Friendica account and a group account on the same login, and you can switch between them without having to log out. But that must have been introduced long after I've quit Friendica.

On Hubzilla, something like this has always been possible: If you want to start a group, you simply create another channel on your account and configure it as a forum channel, either by choosing "Community forum" as the channel role or, if you know what you're doing, by choosing "Custom" as the channel role and then activating "Group actor" in the Custom channel role settings. The latter is also the only way to have a private forum.

Friendica lets you appoint additional admins/moderators, but only from the same Friendica node that your group is on.

As Hubzilla has a full implementation of OpenWebAuth magic sign-on, include server-side, you can promote any forum member on Friendica, Hubzilla, (streams), Forte and Mitra as extra forum admins.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #FacebookAlternative #FacebookAlternatives #Friendica #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups

Friendica Directory

Jupiter Rowland Jan 16

So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

#[Hashtag](https://hub.hubzilla.de/search?tag=Hashtag)

Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

#Hashtag

Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

#Hashtag

Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte

Hubzilla.de

Jupiter Rowland Jan 16

So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

#Hashtag

Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

#Hashtag

Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte

Netzgemeinde/Hubzilla

Show thread

Jupiter Rowland Jan 13

@「 Jürgen 」 Daran liegt es noch nicht mal. Mal abgesehen davon, daß das 2014 gestartete Misskey keine Chance haben wird, das 2010 gestartete Friendica von BBcode zu Misskey-Flavored Markdown zu zwingen. Das 2015 gestartete Hubzilla und seine Nachfahren auch nicht, weil gewisse Spezialtags, vor allem betrachterabhängige (sowas gibt's hier, ja), in MFM nicht existieren.

Das mit dem #^ ist eine Hubzilla-"Spezialität", die auf Hubzilla selbst nicht auftritt, von der also die allermeisten Hubzilla-Nutzer nicht wissen. @Der Pepe (Hubzilla) ⁂, @PepeCyBs Welt: Das kommt von der Bookmarks-App. Die erzeugt diese Zeichen, die man auf Hubzilla nicht sieht, sonst aber überall.

Das mit dem kaputten Hashtag liegt daran, daß Friendica und seine Nachfahren Hubzilla, (streams) und Forte bei Hashtags die Raute nicht mit zum Teil des Link machen.

Auf Twitter/𝕏 ist die Raute bei Hashtags Teil des Link: #Fediverse. Mastodon, Misskey, all ihre Forks und viele anderen Microblogging-Anwendungen haben das so übernommen.

Auf Friendica, Hubzilla, (streams) und Forte ist die Raute bei Hashtag nicht Teil des Link: #Fediverse. Der Grund: Friendica ist kein Twitter-Ersatz, sondern eine Facebook-Alternative. Und Friendica ging schon im Mai 2010 an den Start mit genau diesen Hashtags. Das war, bevor Facebook Hashtags hatte, und das war, bevor es en vogue war, Twitter zu klonen.

Hubzilla ist umgebaut worden aus einem Fork eines Forks von Friendica. (streams) ist ein Fork eines Forks dreier Forks eines Forks (eines Forks?) von Hubzilla. Forte ist ein Fork von (streams). Alles von Friendicas eigenem Erfinder aus der Taufe gehoben. Also haben sie alle Friendicas Verhalten geerbt, auch weil es keinerlei Veranlassung gab, das zu ändern.

Das Problem ist nun: Zum einen rechnet Sharkey nicht mit Hashtags, bei denen die Raute davor statt mit drin steht (das tut Mastodon auch nicht, aber Mastodon kann das einigermaßen abfedern, seit da mal jemand einen Issue eingereicht hat). Zum anderen kann Sharkey augenscheinlich auch nicht damit umgehen, daß irgendwelche Inhalte in irgendwas anderem als Misskey-Flavored Markdown formatiert sind.

Auf Hubzilla sind Posts, Kommentare und DMs intern in BBcode formatiert. PubCrawl, das die optionale ActivityPub-Anbindung zur Verfügung stellt, wandelt den BBcode allerdings in standardkonformes Rich Text Format um, das meines Wissens so auch in der offiziellen ActivityPub-Spezifikation empfohlen wird.

Mastodon nimmt das RTF, wandelt es in HTML um, schickt es durch seinen HTML-Sanitiser, der alles Unliebsame rausschmeißt (vor Mastodon 4.0 hat der Sanitiser noch alles rausgeschmissen und nur noch Reintext übriggelassen), und zeigt das Ergebnis dann zuverlässig an.

Sharkey scheint dagegen nur gebaut zu sein gegen sich selbst (sendet wohl MFM), Misskey (sendet wohl auch MFM), eventuell andere Forkeys (senden wohl auch alle MFM) und Mastodon (kann gar keine Textformatierung erzeugen und sendet daher auch keine). Es scheint nicht damit zu rechnen, daß sich irgendwas an die Spec hält und RTF sendet.

Irgendjemand sollte sich also mal mit Fehlermeldungen an die Misskey- und Sharkey-Entwickler wenden.

Hier mal ein Test (dieser Kommentar kommt auch von Hubzilla): Funktioniert das hier?

Stichpunktliste
fett
kursiv
unterstrichen
Code

Sorry, jetzt muß ich selbst eine Zeile Hashtags einbauen, auch, um zuverlässig die Filter, die möglicherweise gerade auf Mastodon viele im Einsatz haben, auslösen zu können.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Misskey #Sharkey #Friendica #Hubzilla #Streams #(streams) #Forte #Textformatierung #MisskeyFlavoredMarkdown #MFM #BBcode

「 Jürgen 」 (@juergen)

#Ü50 l #Ehemann und #Vater l #Technik #Männer #SelfHosting Part of the Fediverse since September 2023.

Jürgens 🦈

Gancio de Roma Jan 13

---> RINVIATA A DATA DA DESTINARSI! <--- presentazione libro & live free jazz: "LA MUSICA importante quanto la tua stessa vita"

CSOA Forte Prenestino, venerdì 23 gennaio alle ore 21:00 CET

---> RINVIATA A DATA DA DESTINARSI! <---

CSOA Forte Prenestino
VENERDÌ 23 GENNAIO 2026
ore 21:00
Forte Infoshop presenta il libro

LA MUSICA
importante quanto la tua stessa vita.
La rivoluzione del Free Jazz e della Black Music
di Val Wilmer (Shake Edizioni 2024)

con
Pino Saulo (autore e conduttore radiofonico)
Ermanno ‘Gomma’ Guarneri (Shake Edizioni)

a seguire live free jazz con
Sandro Satta (sax alto)
Marco Colonna (sax baritono / clarinetto basso)
Ermanno Baron (batteria)

.........
Finalmente in lingua italiana il classico sul free jazz degli anni Sessanta e Settanta della grandissima fotografa e storica del jazz Val Wilmer. Questo però non è un libro fotografico, ma la narrazione dell’avventura della generazione di rivoluzionari che è riuscita a fare della propria arte la vera avanguardia della cultura americana.
John Coltrane, Ornette Coleman, Albert Ayler, McCoy Tyner, Sun Ra, Archie Shepp, Cecil Taylor e molti altri nel loro vero contesto politico, sociale ed esistenziale. Un’epoca di straordinaria innovazione e sperimentazione che continua a ispirare anche i musicisti di oggi.

Il free jazz è sempre stata una musica scomoda. Quando Coltrane trasformò My Favorite Things – una canzone da musical di Broadway – in un urlo di trenta minuti che lacerava ossessivamente le strutture della struttura musicale convenzionale, o quando Albert Ayler ribaltò Summertime di Gershwin alla ricerca di qualcosa di più profondo e con una risonanza emotiva più oscura, la risposta generale fu l’indignazione. A differenza dei molti critici che espressero il loro disgusto e quasi con risentimento, Val Wilmer capì da subito che quei musicisti non erano apostati o eretici, ma gli straordinari innovatori di una importante, nuova fase della black music.
La musica, importante quanto la tua stessa vita è una frase emblematica di McCoy Tyner, che ben rappresenta lo spirito che anima questo libro, il primo e approfondito resoconto che sia mai stato scritto sulla rivoluzione musicale passata alla storia come free jazz. E di quella straordinaria stagione l’Autrice racconta le aspirazioni politiche, umane e musicali, aggregando con sapienza i materiali emersi nelle sue lunghissime interviste con tutti i protagonisti.

Prefazione di Richard Williams che ha suonato la tromba, tra gli altri, con Charles Mingus, Yusef Lateef, Duke Ellington, Gil Evans e inciso per la Blue Note, Impulse!, New Jazz, Riverside e Atlantic.

“Il capolavoro sulla storia del free jazz.” BBC Radio 3

“Il miglior libro sulla black music.” The Guardian

“Questo libro mi ha salvato dall’idea di mollare tutto… i jazzisti di cui Wilmer scrive mi hanno fatto capire come progredire musicalmente.” Viv Albertine (The Slits)

https://shake.it/libri/la-musica-importante-quanto-la-tua-stessa-vita-la-rivoluzione-del-free-jazz-e-della-black-music/
.........
Vieni e fai venire!

CSOA Forte Prenestino
da 40 anni pratichiamo e diffondiamo occupazione & autogestione

https://forteprenestino.net/attivita/infoshop/3522-la-musica-importante-quanto-la-tua-stessa-vita

https://roma.convoca.la/event/presentazione-libro-la-musica-importante-quanto-la-tua-stessa-vita

Show thread

Jupiter Rowland Jan 9

@Jasper Burns

Permissions meet groups

It gets really interesting when the permissions system is applied to groups. As the owner of a Hubzilla forum, you have the following options:

You can control who can see the profile of the forum, i.e. what it is all about. For example, you can only allow confirmed members to see it. Or, in fact, you can only allow certain members to see it by assigning a specific contact role to them. Or you could make it Fediverse-specific: Only those who can be recognised as logged-in Fediverse users can see the profile. Or you can hide it altogether.
You can control who can see the contacts, i.e. the forum members, all the same. Like, for example, only a chosen inner circle may be allowed to see the list of forum members, but Joe Average Forum Member is not.
Likewise, you can control who can see what has already happened in the forum when visiting the group profile.
You can choose to hide the whole forum from the directory, the place where people go to find new contacts (the mastodon.social equivalent is https://mastodon.social/directory), to keep the forum secret altogether by keeping people from finding it accidentally or by searching.

(streams) and Forte have four different types of group channels instead:

Normal: public, group members may upload media to the group's file storage
Limited: public, but group members may not upload media to the group's file storage
Moderated: like Limited, but by default, posts and comments by new group members have to be approved by the admins; members may have their permissions upgraded and post and comment without approval once they've proven themselves worthy
Restricted: private, profile is only visible to group members, stream of posts and comments is only visible to group members, posts and comments are only sent to group members, but group members may upload media to the group's file storage

Whether or not a group is visible in the directory is a separate switch.

As I've already said, you can grant individual permissions to your contacts on your personal channel. But you can grant individual permissions to forum users on a forum channel just the same. You can have regular users. You can have users with certain extra privileges. You can use the permissions system to silence users without kicking and blocking them.

And you can use the permissions system to appoint extra forum admins/mods. You can grant contacts permission to administer your forum. Now, this requires for your channel to recognise visitors and their identities to see what permissions they shall have and to grant them these permissions. And this requires OpenWebAuth. So right now, you can only make forum members from Hubzilla, (streams), Forte, Friendica, Mitra and Tootik additional admins/mods. But you can.

(9/9)

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions #Groups #FediGroups #FediverseGroups #PrivateGroups

Netzgemeinde/Hubzilla

Show thread

Jupiter Rowland Jan 9

@Jasper Burns

Permissions, part 3: At post level

As I've already said, whenever you write a post to start a new thread, you also define the permissions of this post. Of this post and of all replies.

Let's translate this to Mastodon again.

You know the toot visibility button, I guess. Let's assume it looks and works somewhat different. Especially the visibility options.

"Public" still exists. It does what it says on the button: It makes your toot public. Oh, and now, it also makes all replies public. There's no replying to your toot with a DM.

The other three don't exist.

Instead, as the second option, you have "Only me".

Right below, all your lists are listed up. You can pick one of them. You can send your toot to everyone on one specific list of yours and to only those on that list, all without having to mention them. Better yet: Only those on that list are permitted to see your toot. And only those on that list are permitted to see any reply to your toot. Killer feature: They can see each other's replies, and they can reply to each other.

Below that, all groups that you follow are listed up. Again, you can pick one of them. This will have the effect that your toot will go to the group, and it will be forwarded by the group to all its members, but it will not go to your followers unless they're also in that group.

Below that, there's "Custom selection". This opens another window with each one of your lists and each one of your followed accounts, each with a green "Allow" button and a red "Don't allow" button. Here, you can put together a choice of lists and single accounts whom to send your toot to and a choice of lists and single accounts whom not to send your toot to. Again, only those who receive the toot are also permitted to see it, and only them are permitted to see any of the replies, and no-one can ever change these permissions.

What sense this makes?

Imagine you have a list with a certain group of friends in it. One of them will soon celebrate their birthday, and you want to organise a birthday surprise for them. So you send a toot to that list with everyone in it, but without that person who'll soon celebrate their birthday so you won't ruin the surprise for them.

Or: Imagine you have lists according to which languages people speak. Like, you have a German list, and you have an English list. Then you can put together an audience for a German toot from lists and single followed users, but exclude the English list so that those who don't understand German anyway won't receive that toot.

By the way: This also covers DMs. And this means that DMs are actually private.

As Mastodon is right now, you can DM Alice, you can have a conversation with Alice, but Alice could mention Bob and pull him into the conversation. This also gives Bob the opportunity to read the whole thread because he has access to it now. Mastodon only defines to whom a message is sent, but not who is allowed to see it.

In this version of Mastodon, when you DM Alice, you only grant Alice permission to see your toot and everything else in the thread. Now, Alice can mention Bob all she wants, but she can't pull him into the thread. Bob won't even receive the toot with his mention in it. He is not permitted to see it. You have not granted him permission to see the start toot, and thus, you have not granted him permission to see any of the replies, including the one in which Alice mentions him. Alice cannot change any permissions in the thread. Neither can you, by the way. The moment you send the start toot, all permissions are permanently set in stone for the whole thread.

This also makes dogpiling by extra mentions in DMs impossible.

Also, this provides for very effective quote-post control. It isn't allowed to boost posts that aren't public, including replies. It isn't allowed either to Mastodon-style-quote, as in quote-post, posts that aren't public, including replies.

These DMs have another advantage of DMs on Mastodon-as-it-is-now: If you send a DM to Alice and Bob, Bob receives Alice's replies, and Alice receives Bob's replies, and the two can reply to one another.

Oh, by the way, there's another nifty button. A speech bubble. With this button, you can allow or disallow replies to your post. Mind you, again, this only works when you start a thread. You cannot allow or disallow replies to a reply that you post.

Now, how does Mastodon-as-it-is-now handle DMs from Hubzilla, (streams) and Forte? It sees them as Mastodon DMs, and it treats them like Mastodon DMs. The downside is, if I send a restricted-permission post to Alice on Mastodon and Bob on Mastodon, both perceive it as a Mastodon DM. Both can only reply to and converse with me. They can't see each other's replies, and they can't reply to each other.

(8/9)

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions #ReplyControl