-
Notifications
You must be signed in to change notification settings - Fork 0
How do I??? FAQ
Table of Contents generated with DocToc
-
Some FAQs
- How do I get WebDAV working?
- How do I make a channel that can be edited or adminstered by other people
- How do I filter posts by language
- How do I use huzilla as openid provider
- How do I post to WordPress
- How do I connect to Hubzilla using AndStatus?
- How do I "unfollow" someone?
- How do I reduce disk usage for MySQL database in Hubzilla?
- How do I find the RSS feed URL of my channel?
##How do I get WebDAV working? via waitman at https://hub.zilla.tech/page/waitman/freebsddavclient Installing and using Dav Client on FreeBSD for Hubzilla
Other options are available, here are two. davfs2 does not seem to install on FreeBSD, as it uses inotify, a Linux kernel feature not present in FreeBSD. It may be possible to build davfs2 using ports/devel/libinotify but I have not tested. (also need to change references to error.h to err.h)
It seems that there were ports for davfs2 and wdfs however these have been removed from the ports tree.
- Using Dolphin File Manager (KDE)
Launch Dolphin File Manager and click on "Network" under the "Places" heading on the left panel. Click "Add Network Folder", then select "WebFolder (webdav)" option.
On the "Network Folder Information" page, enter the infomation:
"Name" (which will be displayed in the "Network List") "User" is the username (name of Hubzilla channel connecting to, not your login email address) "Server" is the IP or hostname without http:// or URI path, "Port" should be "443" for SSL sites, otherwise "80" "Folder" is set to /dav/username Check the box "Use encryption" if your hubzilla site is running over SSL, https://
Save & Connect button. When connecting it will prompt for password, which is the login password for the corresponding Hubzilla account.
- use fuse/wdfs
First install the "fuse-kmod" port. (or use pkg)
ports/sysutils/fusefs-kmod
add fusefs_enable="YES" to /etc/rc.conf
Load the kernel module
kldload fuse.ko
(when you reboot it should load automatically)
Install neon port
ports/www/neon (or install pkg)
Get the wdfs source from github and build. https://github.com/waitman/wdfs
cd wdfs
./configure
./make
./make install
Create mount point and connect to Hubzilla dav: (change to your domain)
mkdir /hubzilla
wdfs -f -o allow_root -ac #^https://hub.zilla.tech/dav/CHANNEL /hubzilla
(check options using wdfs -h. Remove the -f switch to run in background.) It will prompt for username and password. The username is the channel name, the password is account login.
##How do I make a channel that can be edited or adminstered by other people
Click on the Gear icon (apps) at the top. Click on Connections Click the person you want, where it says Edit. Click "Individual Permissions" Waaay down at the bottom, it says:
Can administer my channel resources
Extremely advanced. Leave this alone unless you know what you are doing
Well even if you don't know what you're doing, if you want to share a channel with someone else, do this.
Now the other person will see that channel in their Channel Manager, under "Delegated Channels"
If they click on it, they'll be in as a Remote Authentication, which may be confusing, but that's what it is.
Then to get out of that mode, they have to go to the Gears icon (apps) at the top, click Settings, and then click "Logout". Then they can log back in as themselves.
##How do I filter posts by language Settings -> Additional Features -> Network and Stream Filtering -> Connection Filtering
Once that is turned on, Click 'Connections' in the top navigation menu (the person icon next to the exclamation mark). These are the channels you're connected to. Find a channel and click 'Edit'.
On the connection edit page open "Custom Filter" and add the text lang=ru or lang=fr in the appropriate box for what you wish to accomplish (allowing the language or rejecting the language). There are many different ways to use these filters but we'll only concentrate on language for now. Save the changes.
I've mentioned this elsewhere but it isn't very well documented, so I'll tell you everything I know --- the language detector requires a minimum of 128 characters to have any degree of accuracy and we selected a somewhat arbitrary accuracy cutoff. So short posts won't be detected correctly, if at all.The longer the post the better the accuracy of the language detector. And once we've blocked a post you won't see any comments to that post either - no matter what language the comments are in.
If you want to tweak the accuracy settings get back to me and I can tell you how to do that. I chose settings that worked across a random sampling of foreign language posts and gave me "satisfactory" results.
(Source: Mike)
##How do I use huzilla as openid provider
Example
https://grid.reticu.li/id/andrew
(It is the url of your channel home for example https://grid.reticu.li/channel/andrew but the "channel" is replaced by "id".)
Oauth2 is on the to_do list of hubzilla.
It requires that 'can view my channel stream and posts' be "anybody on the internet", which I believe it is since this post is not private in any way. If your permissions setting is "Mostly Public" this should be correct.
The only other check we make is that "Enable WordPress Post Plugin" is "yes" on your feature/addon settings page. If both these conditions are correct the "post to Wordpress" checkbox is added to the permission dialogue box.
Oh and you must be logged in locally. e.g. posting from your channel after logging in to the site.
In pictures: here: https://zot-mor.rhcloud.com/display/456e9d23cf933b8e8824ff634d75c2387a5fc474403aa88f882e7607840d7a42@zot-mor.rhcloud.com
Says Mike
To emulate the Twitter behaviour in the current code for most situations, just "Delete" the connection request. They are still following you but you are not following them. If you have private or custom permissions for your channel this may not work, as modes exist which don't allow anybody to follow you without permission.
'approve later' does nothing. They remain as a pending connection in your notification bar. Their ability to "follow" you in their stream is again dependent on your channel permissions. For public roles they can generally follow you at this point, but they can't interact with you. For more private permission roles, it depends on the role or specific permissions as to what they can see or do while they are in a "pending" state.
Says Mike
We allow you to expire any of these things at whatever time interval you choose. Default retention for dreport is 30 days. Default for stream posts (those posts that are not your own) is forever, but this can and should be
changed in site/admin. I recommend 30-60 days, but it's totally up to you and the needs of your community. If I
recall there's a separate config for expiring purely "public content" that is imported/shared from other sites via /public or the "discover" tab. These I wouldn't keep around for more than about a week. The queue is self-expiring. The physical sizes of the DB files is misleading because in many cases the tables are full of deleted table entries and the space will eventually be reclaimed by newer entries. We once did "optimize table" instructions (like defragmenting a disk) on these dynamic tables but this results in tables crashing quite often or the database becoming unresponsive while being optimized. We eventually removed all of these calls.
You can modify this with
util/config system expire_deliver_reports 14
or disable it all together:
util/config system disable_dreport 1
help/hidden_configs
system.disable_dreport
If '1', don't store or link to delivery reports
The reason this isn't the default is because most site admins cannot or will not read logs when their members encounter delivery issues, forcing somebody like me (who ends up dealing with the issue) to attempt clairvoyance on the server in question. Having a delivery report allows the member to easily ascertain if the message was delivered/queued/permission denied or whatever to a particular recipient and without requiring their hub admin to be useful at anything or even semi-conscious.
As mentioned earlier, this table usually consists of 95% overhead or deleted entries because we expire them somewhat aggressively - for the benefit of sites that are severely disk limited. Anyway, you can turn delivery reports off completely and recreate the table and it should thereafter use 0GB. I just refuse to troubleshoot any delivery issues involving your hub members.
If you need to shrink an already metastasized-to-ridiculous-proportionsl dreport table, you can do this:
mysql -uhubzilla -h127.0.0.1 hubzilla
Enter Password:
>
> delete from dreport;
> optimize table dreport;
It's https://yourhub.com/feed/channelname
Mike adds:
We also use a thing called "feed discovery" which has been a standard for at least the last 10-15 years. Basically it means you can just plug your channel homepage url into most any modern feed reader or feed processing software and you don't have to remember the location of the actual XML generator on your site or put various icons on the page which (if clicked) display pages of scary looking computer code. The feed processing software will just find it.
Mike says
This is a long standing request. We're subject to the "horse out of the barn" problem, in that we cannot take back a public post which has gone out to other networks and made available via feeds. If a post started out private - it would be possible to make a note of the old recipients and the new recipients and send a delete request to any of
the old recipients that are no longer on the list, and send a new copy to any new folks that weren't included
originally. If it's a public post you can only delete it (which may have little or no effect on external sites and networks, as the content would have been visible in public searches and RSS feeds). We've talked about this for
years. This is the only workable solution; and It is merely awaiting a developer to implement.
on admin I have Expiration period in days for imported (matrix/network) content and setting each member have Expire other channel content after this many days
The site expiration has priority. A member can still set the expiration for their own stuff to a period lower than the site expiration.