neue medienordnung plus
  
Her https://hubzilla.rocks/pubsites is "Registration Policy" for https://start.hubzilla.org open. Is it a bug in Hubzilla code or a bug in hubzilla.rocks installation?

@Hubzilla Development+ @Hubzilla Support Forum+ @h.ear.t | tobias @Andrew Manning
neue medienordnung plus
  
@Andrew Manning Is it correct, that each hub start.hubzilla.org member can generate one invitation code for start.hubzilla.org?
Andrew Manning
  
At the moment I'm not sure. I don't think so. Looking through the code shows that there is support for member-generated invitations, limited by some number set in the service classes, but this does not appear to be fully implemented. Or maybe I'm just not connecting the dots properly.

You're a member on start.hubzilla.org right? Try to generate one at start.hubzilla.org/invite
neue medienordnung plus
  last edited: Sun, 19 Nov 2017 08:12:46 -0500  
I'm member on start.hubzilla.org. And I get this message
You have no more invitations available
if I run start.hubzilla.org/invite . I mean, that hint
you can request from either from an existing hub member
here https://start.hubzilla.org/register is misleading :-|.

Alexandre Hannud Abdo
 Paris, France (43.5995 1.4332) 
@Hubzilla Development+ I will later post the final version and an English translation =)
Comments will be welcome even after the event since this can be a useful resource for the community.

@Raymond Monret je comprends que c'est très dernière minute, mais je te mentionne au cas où par hasard tu trouves le temps de vérifier mon écriture avant les 17h... et merci de toute façon !
Manuel
  
¡Enhorabuena y suerte! :like
Raymond Monret
  
Je vais essayer de le relire ce matin ou en début d'après-midi

Andrew Manning
  
I decided to roll up my sleeves and try to implement some of our ideas for revising the help pages (a.k.a. "doco" if anyone reading this is new to Hubzilla lingo). So far things are going well. As we discussed, we're moving back to a simpler, more modular collection of help files. Some of the goals of this update are to make it as easy as we can for people to contribute translations of the help content and for us to add and reorganize content more efficiently. We want it to be easier for people to contribute and keep the doco current!

I've taken the idea of hierarchical table of contents and simplified it in a way conducive to translations. The doco folder structure looks something like


/doc/en/about/toc.json
/doc/en/about/intro
/doc/en/about/project
/doc/en/admin/toc.json
/doc/en/admin/requirements
/doc/en/admin/deploy
/doc/en/admin/addon/toc.json
/doc/en/admin/addon/recommended
/doc/en/admin/addon/federation
...


where translations simply follow the same file/folder hierarchy but under their two-letter folder as it has been for some time. The table of contents is generated automatically by recursively scanning the /doc folder and using the heading and title information in the toc.json file that must reside in each subfolder. In the example here,


{
    "heading": "Administrator Guide",
    "items": [
        {
            "file": "requirements",
            "title": "Requirements"
        },
        {
            "file": "deploy",
            "title": "Installation"
        },
        {
            "dir": "addon",
            "title": "Addons"
        }
    ]
}


you can see that the TOC section for the "admin" folder will list links to the requirements and deploy page, and then create a sub-menu called "Addons". That submenu will be populated according to the admin/addons/toc.json file.

You configure the order of the files linked in the TOC in the left aside region of the help pages by the order in the toc.json file. The HTML is decoupled completely from the TOC structure. Translators need only translate the "title" and "heading" fields of these toc.json files. File names will need to be consistent for the language selector system to work as I've written it. The individual pages should be shorter and their modularity will ideally help translators do their job more easily.

@Hubzilla Development+
phellmes
  last edited: Sat, 18 Nov 2017 09:06:11 -0500  
@Andrew Manning
I avoid pushing to remotes on isolated branches because I pull & rebase on dev a lot to stay updated and discover possible conflicts early.
Basically I created 5 files for the additional features, 4 parts (composition, filtering, general, posts) and 1 (overview) that has an intro and links to the other 4.
You can add them as empty placeholders in your structure wherever you want them. Their relative structure could be a folder with the overview and a subfolder with the other ones like this

../feature/additional.md
../feature/additional/composition.md
../feature/additional/filtering.md
../feature/additional/general.md
../feature/additional/posts.md

or one folder with all of them together like this

../feature/additional/overview.md
../feature/additional/composition.md
../feature/additional/filtering.md
../feature/additional/general.md
../feature/additional/posts.md

- whatever suits the desired linking structure better.

Tell me as soon as the placeholders are in dev, then I'll pull, make a new branch and copy my content over before continuing to work on it. That way I can make a clean pull request later when the base content is usable (I can already do that with parts of the content and several TODOs still open while working on the remaining parts - if that is wanted).
Andrew Manning
  
Thanks for the explanation. I've incorporated those pages into the new structure. So far things are going well. I'll figure out how to make the help page categories collapsible using the native Bootstrap technique at some point. For now we're focused on content.

One "problem" I already see with the new TOC system, which overall I really like, is that it forces translations to contain an entire mirror of the English folder structure and toc.json files. The actual content files do not necessarily have to be in the folder hierarchy, because we will fall back to the English version if a translation is unavailable as we do now. In a way this might be a good thing in the sense that it will be more obvious which pages remain to be translated in the various translation folders.
Andrew Manning
  
I'm rewriting a lot of stuff. Anyone who wishes to see what I have so far can checkout the "docs" branch in my fork: https://github.com/anaqreon/hubzilla/tree/docs

I think I've recovered and hopefully improved some of the translation functionality. Now it's time to start carving up the existing help pages and redistributing the content to the smaller pages. Then we'll want to improve the content and add more. One of the challenges is incorporating these random single pages at the top level that aren't currently linked anywhere.

neue medienordnung plus
  
If I use mention character, hubzilla offer me in the list after @ character one valide guesttoken name. So:

Image/photo

But if I choose this guesttoken value as mention tag, then make hubzilla this mention tag not to one link. Is it desired behavior of hubzilla, that hubzilla offer me in the list after @ character one guesttoken name? What can I do with guesttoken mention? One guesttoken holder have no email in hubzilla context and cann't notify about mention event.

@Hubzilla Support Forum+ @Hubzilla Development+ #guesttoken #mention #hubzillamention
Mario Vavti
  
This is most probably a bug...
neue medienordnung plus
  
You mean, I can create one bugreport, correct?
Mike Macgirvin
  
You could always just fix it...

neue medienordnung plus
  last edited: Tue, 14 Nov 2017 02:59:07 -0500  
  • I created webpage WPB http://dummy.org/page/wpb on channel B with [observer=1/0] protected content
  • I created Token TCA for channel A zat=tca
  • I open webpage WPB with token for channel A
  • I see protected content in webpage WPB
Hubzilla version 2.8.1

@Mike M. closed the issue https://github.com/redmatrix/hubzilla/issues/909 , but I mean, that is one bug, that Hubzilla display protected content in webpage WPB for visitor with Token TCA, that is legal for channel A. Because I created one token for access to channel A, not to channel B.

Similar to Login on Hubs:
  • one valid Login on hub https://hub.libranet.de/ be no permission for login on hub https://macgirvin.com/
  • I anticipate, that one valid token for https://hub.libranet.de/channel/nmoplus be no permission for https://hub.libranet.de/channel/wallzilla
I mean, The actuelle behavior of token solution is a danger for channel security:
malicious user from channel https://hub.libranet.de/channel/A can make one token TCB and get an access to token protected content on channel https://hub.libranet.de/channel/B

Token managament is located by channel owner A. This fact suggested, that the token from channel A is valide for channel A. I mean, that one average user assume, that the tokenized access to content protected their content. What mean you? Please vote pro or contra of this statement:

Token for channel A give no permission to access to via token accessible content from channel B

#tokenmanagement #token @Hubzilla Support Forum+ @Hubzilla Development+
Mario Vavti
  
@neue medienordnung plus the observer tag has nothing to do with permissions or protection as you call it.

observer=1 content will be visible to any authenticated channel and/or guest token allowed to see the content (in terms of is allowed to view your webpage from the acl).

observer=0 content will be visible to any not authenticated viewer.

observer=0/1 basically only works with public content since we need to be authenticated to see restricted content. So any channel viewing restricted content will always see the content of observer=1.
neue medienordnung plus
  
@Mike Macgirvin: Thank you for the detailed answer. I mean, this hack
All somebody has to do is "view source" and they can see whatever it is you're trying to hide.
is not suitable for viewing of with [observer=0/1][/observer] hided content. Can you see, what I hided in this demopage  https://hub.libranet.de/page/wallzilla/vertrauliche-inhalte-freigeben-demoseite_de :-)?

I mean, that without the opportunity "access control at the paragraph level" is it for developer of hubzilla apps very difficult, attractive (killer) hubzilla app to develop.
neue medienordnung plus
  
OK, is my fallacy. And for advanced serverside access control at the paragraph level need hubzilla developer such tools how AJAX with ACL Support - right?

neue medienordnung plus
  last edited: Tue, 14 Nov 2017 02:08:26 -0500  
  • I created webpage WPB http://dummy.org/page/wpb on channel B with [observer=1/0] protected content
  • WPB contains image ImA, that be accesible only for selected vistor
  • I allowed visibility for ImA for token TImA
  • but image ImA is not visible for token TImA
  •   image ImA be visible for token TImA, if I upload/include image ImA after change of ACL for image ImA
Is this beahavior a bug or a feature? I anticipate, that image ImA be visible for token TImA without new upload image ImA after allowing visibility for ImA for token TImA.

#tokenized #tokenizedcontent #protectedcontent #visibility @Hubzilla Development+ @Hubzilla Support Forum+
 ACL
Haakon Meland Eriksen (Parlementum)
  
Right, you need two folders, one for restricted files and one for public files.

ImageB must be under a restricted folder in Files, e.g. Restricted Files, while ImageA is in a public folder in Files, e.g Public Files.

Add the ZAT for OnlyYouAreWelcome to Restricted Files.

Add the ZAT-link to ImageB to the webpage.

I may have got this wrong.
neue medienordnung plus
  
I assume, that with your solution I must all webpages, where include Restricted Objects also declare to Restricted Webpages. Otherwise see other authenticated user without access to image logo.png this message:

Image/photo
Haakon Meland Eriksen (Parlementum)
  
Well, as described just those with the ZAT-link are allowed in, but you can add other people to the Restricted Files folder. I am going to a meeting now, so good luck! :-)

mrjive
 
Sorry for the silly question, but usually when I have the need of assistance, I click on "Hubzilla Development" item in the Forum list, which is in my /network page, left column. Thus I get a message with Hubzilla Development+ etc. Is it different than coming to the HD channel page and write as I'm doing now? Is it better? Same thing?
thanks
Mario Vavti
 
The first is a forum mention the second a wall to wall post. The only difference is that if posting directly to the forum wall you will not have a copy of the post in your /channel page...
mrjive
  
great, thanks :)
Alexandre Hannud Abdo
  
Well it also affects whether the message gets signed with your private key, displaying the green tick under your name, which won't display on a remote login wall to wall post.
mrjive
 45.05 7.6667 
@Hubzilla Development+
Hi *, thanks for all your hard work for HZ 2.8.1!
After the upgrade, when I click on the comment box I get this:
Image/photo

Am I the only one?
Mario Vavti
  
Are you possibly still using the long time ago deprecated and abandoned 3rd party plugin embedphoto on your site?
mrjive
 
@Mario Vavti oh, I'll go and check this, thanks.
mrjive
 
a-ha! thanks, that was it!

Andrew Manning
  
I updated the Hubzilla Vagrant package to improve the development workflow out of the box. You still get a functioning fresh installation after cloning and executing vagrant up, but now the web root is shared with the host using an NFS mount. This allows you to easily edit the hub files using your favorite development tools, and the modifications are visible instantly in the VM.

I like to use Netbeans, and with the new Vagrant configuration, I can create a "PHP project with existing sources" located at ~/hubzilla-vagrant/sync/var/www/hubzilla.dev/ (with the project files stored elsewhere), where ~/hubzilla-vagrant/ is the directory of the cloned hubzilla-vagrant repo.

If people want to share their exact development hub state, they can use this system to do so. They would

  • Make a new branch in their hubzilla-vagrant clone.
  • Copy the sync/var/www/hubzilla.dev to provision/var/www/hubzilla.dev
  • Export the database using the hub_db_snapshot.sh script (or manually) and copy the hubzilla.sql file to provision/root/snapshots/hubzilla.dev/db/
  • Commit their updates to their new branch, and
  • Push the branch to their fork of hubzilla-vagrant.

If we really wanted to go crazy, there is nothing preventing us from using this to explore decentralized hub-to-hub interactions. All you need to do is add more Apache config files for new hubs like alpha.hub, beta.hub, gamma.hub, etc (appending these names to the /etc/hosts file on the host machine), and then take snapshots of each hub's database and web root. You could test the way, for example, cloning and file synchronization works between two hubs running different Hubzilla versions. If you set something like this up (and it would be time-consuming), you could share it with others so that they could help you solve the problem instead of worrying about the setup.

https://github.com/anaqreon/hubzilla-vagrant

@Hubzilla Development+

Philipp
 
In wikis I create, eveything is underlined and nothing seems to be able to change that. Anybody else recognized this behaviour?
Philipp
  last edited: Sun, 12 Nov 2017 13:41:38 -0500  
Think I found a clue where the problem could be located: The everything-underlined problem is only there if I set the scheme to dark, simple_black_on_white, simple_green_on_black or simple_white_on_black.
The other ones just work fine.
Mario Vavti
  
Thanks @Philipp i found the issue and will push a fix in a minute or so... In general i don't recommend using those schemes at the moment because they are not maintained or rather they are on life support...
Philipp
  
Ok, thank you. Perhaps the fact that they are not recommended should be stated somewhere. Perhaps just a (not maintained) after the name in the selection list?

neue medienordnung plus
  
s. screenshot below:
  • is it correct, that implement of change and delete permissions for selected visitor is possible with a few lines of code?
  • exist a fundamental concerns against implement of wrote and delete/ change - for example upload - permissions for selected visitor?
= German Edition =
Zwei Fragen habe ich zu diesem Screenshot:
  • Stelle ich es mir zu einfach vor oder sind es nur ein Paar Zeilen Code, um zusätzlich zu einem Leserecht auch "Ändern" (bspw. upload) und vollständigkeitshalber auch "Löschen" den ausgewählten Benutzern auf ausgewählte Objekte zu erlauben?
  • gibt es grundsätzliche Sicherheitsbedenken gegen die Realisierung so einer Einstellmöglichkeiten?

Image/photo
@Hubzilla Support Forum+ @Hubzilla Development+ @Deutschsprachige Nutzer+

#Einstellmöglichkeiten

neue medienordnung plus
  last edited: Sun, 12 Nov 2017 05:20:46 -0500  
Mario Vavti
  
@neue medienordnung plus because i forgot to mention the dev forum. Sorry for that...
Haakon Meland Eriksen (Parlementum)
  
@Hubzilla Development+ I synced a bunch of photos and they appear in Files here at Parlementum, but do not display when I try to see the new album in Photos. Is there anything I can do, or is it a bug?
Haakon Meland Eriksen (Parlementum)
  
I uploaded through the web interface and through DAV to the same folder. The one added through the web interface is recognized as a JPEG photo, while the ones added through DAV are not recognized as JPEG photos, so perhaps there is some issue with recognizing MIME types through DAV?
Mike Macgirvin
  
Just did a bunch of work on that section of code. Should work better now.
Haakon Meland Eriksen (Parlementum)
  
Brilliant - thank you! Looking forward to trying it out. :-)

neue medienordnung plus
  
Is it possible "upload my file storage and photos" permission without modify permission for my connections to enable?

#photo @Hubzilla Development+

neue medienordnung plus
  
Is it diffcult, for visitor with token invitation to enable, file/ fotos to upload?

@Hubzilla Development+ #tokeninvitation #invitation
 token
Mike Macgirvin
  
Is it difficult, for visitor with token invitation to enable, file/ fotos to upload?


You can give the token holders any permissions you want when you create the token. You can even let them administer your channel, but this isn't something I would advise.

neue medienordnung plus
  last edited: Sat, 11 Nov 2017 11:20:33 -0500  
Is it very expensive give for token holder only upload permission? Und only for selected upload folder?
Mike Macgirvin
  
Maybe with a plugin.

neue medienordnung plus
  
I visited https://macgirvin.com with the default browser on my smartphone xperia x10 (Android 2.3.3). I can not visit macgirvin.com with smartphone, concerning browser warning:
there are problems with the security certificate for this site. The name of the site does not match the name on the  certificate.

Can other user observe the
https://macgirvin.com
website with your mobile device?

@Hubzilla Development+ @Hubzilla Support Forum+ #xperiax10 #xperia #browserwarning
Mike Macgirvin
  
Gingerbread MR1 (Android 2.2.3) is really old and doesn't understand SNI, which allows shared hosts on the same IP to use different certs. My site uses shared hosting and has a number of different websites (several of my own) on the same IP address.
Einer von Vielen
  
@neue medienordnung plus you are using Android 2.3.3. I guess you miss a lot of measures you could take to give you more privacy.

Please see this hands-on Befreie Dein Android. This manual will be updated as soon as I receive a new phone (was shipped already).

It names some of the problems and gives you a detailed description how to solve them.

neue medienordnung plus
  
I have in my cloud all this folder
Profile Photos, Profilfotos; Cover Foto, Cover Fotos with different content. Is it a bug or feature, this double folder for english and german languages?

#doubleFolder @Hubzilla Development+ #ProfilePhotos #CoverFoto
Mike Macgirvin
  
Suppose it depends what language you were using in the browser when you uploaded the content. If you use one language consistently, the folders *should* be consistent with that language.
neue medienordnung plus
  
ist it a feature, that english and german folder are bot allways visible?
neue medienordnung plus
  
Why have my "Profile Photos(1)" (1) after name-string?
Andrew Manning
  
Jeroen
  
@!Hubzilla Development+ We have the bookmarker plugin to add a pretty font-awesome bookmark icon in front of #^ links. Is this really still needed? Can't we better use the bookmark unicode emoji for that: ? ? This will also make those links prettier in third party projects.

Just a suggestion.
JRandal
  
I vote for the change. My Hubzilla host never installed the plugin, so all I see is the #^.
groovehunter
  
@Hubzilla Development+ Is it possible to provide api extension with an addon ?

Or - related question - can I implement an additional layer on top of the zot api?

After a few weeks after my first hello world addon and a first idea what I want,  there is some spare time to come back on a evolved idea.
I could describe it broadly by: allowing a relation of the user to som entities (similar to items or sort of profile attributes) and automate a way to compare/sync these to other users. Maybe let user initiate that, or confirm the suggestion. If you want the hear what application could use this, think in terms of collaboration on sematical structure, easiest example  would be a folksonomy.

Thanks for any hints!
groovehunter
 
You're sure that it is "myaddon_api_register" ? Because in project twitter_api the function is named "twitter_api_register". ... oh, just came to my mind that project registers api calls for project twitter...

so anyway, at least it does not work so if you have an idea about that, I would be grateful. The error is

{"error":"not implemented"}

2017-11-08T21:56:41Z:LOG_INFO:noo69ub3kne459e83me83el5m3:api.php:95:api_call: API info: api/z/1.0/taxonomy/setmsg type: json
2017-11-08T21:56:41Z:LOG_INFO:noo69ub3kne459e83me83el5m3:api.php:133:api_call: API call not implemented: api/z/1.0/taxonomy/setmsg - Array


function requestdata($k) {
        if(array_key_exists($k,$_REQUEST))
                return $_REQUEST[$k];
        return null;
}

function taxonomy_api_register($x) {
        logger('register taxonomy_setmsg');
    api_register_func('api/taxonomy', 'api_taxonomy_setmsg', false);
}


function api_taxonomy_setmsg($type) {
        logger('taxonomy_setmsg');
        set_pconfig( local_channel(), 'taxonomy', 'some_setting', requestdata('some_setting'));
}
Mike Macgirvin
  last edited: Thu, 09 Nov 2017 03:55:01 -0500  
You might want to have a look at help/en/plugins . Basically you need to register a handler for the 'api_register' event. This is usually done inside the plugin's load function. this is always called {{pluginname}}_load(). Then create an unload function which removes the handler. The handler can be any named function you want, but we traditionally name them after the plugin name and the event we're catching so that we don't collide with any pre-existing function names. Inside this function call api_register_func() to register your API handler. You can register as many API functions as you want (as you can see from looking at the twitter_api plugin).
groovehunter
  
Will figure that out hopefully soon, thanks for the help, Mike!