| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
can choose directly from their browser which feed they need.
|
|\ |
|
| |\ |
|
| | | |
|
| |/
|/|
| |
| | |
some template work on locs
|
|/ |
|
| |
|
|\ |
|
| |\ |
|
| | | |
|
| |/
|/| |
|
|\| |
|
| | |
|
|/
|
|
| |
for delivery (or some other purpose) this should probably happen in the delivery mechanism (or other related sub-system) rather than the permissions mechanism, although currently we still attempt direct delivery to archived connections. Technically "archived" means merely that we won't 'poll' the connection according to the current definition.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
forward.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
on load and add $simple_update to the query.
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
support it.
|
| |
|
| |
|
|
|
|
| |
cleanup)
|