| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
instead rely on the sync delivery.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
redirect with code 301) - fix issue #1727
|
| |
|
| |
|
| |
|
|
|
|
| |
was a leftover from zot to zot6 transition days
|
|
|
|
| |
This reverts commit da034045cc1bba74287b7c3e83f4a94ff5359150.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
make sure we get the most recent entry when using privacy tags
|
| |
|
|
|
|
| |
networks could lead to unexpected results
|
|
|
|
| |
defaults to 500000 microseconds. No config UI yet.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
otherwise
|
|
|
|
| |
authentication might fail
|
| |
|
|
|
|
| |
query could be slow if an uid has a lot of items. the workaround for hubzilla < 4.0 is not required anymore
|
| |
|
| |
|
| |
|
| |
|