@muppeth So happy to see you on Hubzilla! So you're thinking about bringing #Hubzilla to #disroot?
Now, thats what i call lag. Yes we are working hard with some folks to make it all looking nice and relatevely easy to start using. I think we will go public in few hopefully short weeks. Feel free to join the effort is you have spare time
Tutorial for Hubzilla Wiki missing?

 Basel última edição: Sat, 07 Apr 2018 11:17:13 -0300  
!Hubzilla Support Forum
I wanted to know how to link to existing wiki pages within a #hubzilla #wiki. For that purpose I searched the hubzilla guide, but I found nothing about it. I finally found an existing public wiki written in markdown syntax, and clicking on source I saw that the syntax is [[page]]. I searched the general markdown syntax documentation, it doesn't say anything about wiki internal linking.
I tried out the same syntax in a new hubzilla wiki written in bbcode syntax on my channel, and it worked. Well, this syntax is the same as in #mediawiki and in #dokuwiki, maybe it's a standard for wikis, I don't know. Maybe there's no need to mention it in the hubzilla #documentation. If yes, does somebody want to do it? It could be that not all hubzilla users have experiences with wikis, or that their experiences with them are too long ago, like for me...
If yes, does somebody want to do it?

Go ahead! Pullrequests are highly appreciated grinning cat face with smiling eyes
You should be able to use the identity aware links too, such as [observer.baseurl]/settings.
Review of Hubzilla 3.0

 Basel última edição: Sat, 07 Apr 2018 12:03:13 -0300  
Sean TilleySean Tilley escreveu a seguinte publicação Tue, 27 Feb 2018 20:40:26 -0300
It took forever to write this, but my #Hubzilla deep-dive has now been published!

The Do-Everything System: An in-depth review of Hubzilla 3.0.

As a platform, Hubzilla holds a tremendous amount of versatility and depth in what it can do. Mike Macgirvin, the platform’s creator, has famously quipped that the system does not have a commercial analogue to draw comparisons to — it’s not just a social network, it’s not just a forum, it’s not just a cloud storage solution, and it’s not just a content management system.

\#decentralization #cloudstorage #federation
Hubzilla UI language doesn't change to safari's default browser user language

@Hubzilla Support Forum+ The #ui (user interface) of a #hubzilla hub automatically switches to the default #language of the #browsers google chrome and firefox, but not of the browser #safari. Why is that?

Tested with (language: brasilian) and (language: english) on safari 11.0.1 with browser's default language german
What *exactly* is the language setting? Hubzilla supports 'de'; (German) but sometimes browsers offer very specific options, such as the specific German dialect of German (de-DE); and Hubzilla doesn't know about this specific language variant so reverts to the default. One can often correct this by adding 'de' after or in addition to 'de-DE' in the browser config.
It seems that one can specify "German (de)" instead of "Germany-German (de-DE)" in Google Chrome and in Mozilla Firefox. It's the default specification for me. I tried to do it also in Safari and in Brave by opening the preferences in the menu. Brave offers only "Germany-German (de-DE)", Safari doesn't show any language options... So at the moment I will stick to Chrome and Firefox.
Fehler "(Person) schrieb den folgenden Beitrag (Dauer) her "

 Basel última edição: Tue, 30 Jan 2018 10:46:32 -0200  
Der Fehler
"(Person) schrieb den folgenden Beitrag (Dauer) #her "
tritt auf #Hubzilla immer dann auf, wenn ein Beitrag weitergesagt wird. Nicht nur, entgegen meiner ursprünglichen Behauptung hier, im Schmalbildschirm-Layout. Nominativ(Ereignis) + Dauer + her + sein ist richtig, Nominativ(Akteur) + Verb + Akkusativ/Dativ(Objekt) + vor + Dauer ist auch richtig, aber nicht diese Vermischung. Ich nehme an, dass der Fehler auf die unreflektierte Übernahme der englischen Wendung mit ago und die Gleichsetzung von ago mit her zurückzuführen ist. Hier im Forum @DE Ãœbersetzungen sind ja #zanata, #transifex und auch die Diskussionsmöglichkeit in Hubzilla selbst erwähnt, jetzt fehlen nur noch die Taten. Mag mir bitte jemand erklären, wo ich diesen Übersetzungsfehler korrigieren und dann die Korrektur in den Quellcode einbinden/hochladen kann?
@DE Ãœbersetzungen @Tobias @Paul Free @neue medienordnung plus @Fraengii
Beispielbild des Fehlers:
@phellmes Dann mal viel Erfolg mit deiner Doku ;-) Lieber Gruss
Leute, der Fehler ist behoben! @phellmes , warst du das Heinzelmännchen? Vielen Dank :-)
Ja, im dev-Zweig habe ich die Funktionalität dafür mit Commit
bereitgestellt. So werden zunächst alle dynamischen Zeitangaben abgedeckt, die über Javascript generiert werden. Die angepasste deutsche Übersetzungsvariante habe ich dann erst mal manuell hinterhergeschoben, damit es gleich richtig funktioniert:
Ich pflege es noch in Transifex ein, bevor die Sachen mit dem nächsten Release in den Master-Zweig wandern.