| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
include/Import/refimport.php
include/activities.php
include/attach.php
include/event.php
include/externals.php
include/identity.php
include/items.php
include/notifier.php
include/photos.php
include/taxonomy.php
include/zot.php
mod/channel.php
mod/connedit.php
mod/events.php
mod/item.php
mod/like.php
mod/manage.php
mod/mood.php
mod/ping.php
mod/poke.php
mod/subthread.php
mod/tagger.php
mod/thing.php
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
include/Contact.php
include/ItemObject.php
include/api.php
include/attach.php
include/diaspora.php
include/dir_fns.php
include/enotify.php
include/event.php
include/expire.php
include/items.php
include/notifier.php
include/notify.php
include/photos.php
include/taxonomy.php
include/text.php
include/widgets.php
include/zot.php
mod/admin.php
mod/channel.php
mod/dirsearch.php
mod/display.php
mod/editwebpage.php
mod/events.php
mod/home.php
mod/item.php
mod/manage.php
mod/mood.php
mod/network.php
mod/page.php
mod/photos.php
mod/ping.php
mod/post.php
mod/thing.php
mod/viewsrc.php
view/css/mod_events.css
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Fixed wrong Doxygen syntax and add some of the available FIXME to
Doxygen documentation.
Updated Doxygen configuration to add also all capital letter tags.
Adding some more Doxygen documentation.
|
| |
| |
| |
| | |
downgrade any directory that claims to be a primary directory for RED_GLOBAL.
|
| | |
|
| |
| |
| |
| | |
firehose. Don't let it.
|
| |
| |
| |
| | |
going forward (was 99). This way it can be adjusted down later without requiring you to change all your existing connections upward (since your existing connections are likely all sitting at 99 at the moment). The default setting is also configurable with a pconfig system.new_abook_closeness
|
| |
| |
| |
| | |
successfully connect with a site. This way we can mark hubs dead on non-directory servers; but we have to wait before implementing this until we have a history of site_update being updated.
|
| |
| |
| |
| | |
we're currently talking to.
|
| |
| |
| |
| | |
$hash wasn't defined in this case
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
This reverts commit b57010e3da6c0521121a622c27013c8af7678132.
|
| | | |
|
| |/ |
|
| |
| |
| |
| | |
The issue remains what to do about comments which are already in the DB and have ITEM_ORIGIN incorrectly set. We can't exactly reset them because the "original" context has been lost. (Sorry but couldn't resist an insider pun that none of you will be able to follow anyway). Read the comments.
|
| |
| |
| |
| | |
There are some fields in the actual stored item that may change when we start the second delivery chain so a few plugins may not deal with these items correctly. Since we only source public items these effects will be slight.
|
| | |
|
| | |
|
| |
| |
| |
| | |
nix extra var
|
| | |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | | |
postgres could get real messy.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
mysql has type tinyint(3) which probably turns into a 24-bit value, but
postgres uses 3-digit decimal as its constraint (probably what the mysql
schema was intended to do). either that or mysql silently truncates while
postgres respects the constraint. Either way, bad data gets in unchecked, now
it's checked.
|
| | |
|
| |
| |
| |
| | |
deletions weren't propagating. Hopefully this is the last reason and there aren't more lurking further down the chain.
|
| |
| |
| |
| | |
fix for the problem of receiving a delete notification before we actually get the item which we're supposed to delete.
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
view/css/mod_events.css
view/theme/redbasic/css/style.css
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/ |
|
| |/ |
|
|\|
| |
| |
| |
| | |
Conflicts:
include/zot.php
|
| |
| |
| |
| | |
changes. Split these into seperate set and reset blocks.
|
| |
| |
| |
| | |
weekly doc updates
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
include/group.php
include/text.php
mod/acl.php
mod/channel.php
mod/connections.php
mod/display.php
mod/group.php
mod/item.php
mod/locs.php
mod/network.php
mod/photos.php
mod/ping.php
mod/starred.php
mod/viewsrc.php
|
| | |
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
include/socgraph.php
|
| |
| |
| |
| | |
parent route we have. By definition we aren't going to have permission issues with these things.
|
| | |
|
| |
| |
| |
| | |
route matching and only look at the last hop before it got to us - which is ultimately all we should care about (since that sender controls the thread permissions). Route mismatches seem to occur somewhat frequently from yamkote (for unknown reasons), and the logging has been improved a bit so it should provide some slightly more useful debugging info in case it still happens going forward. Oh, also we'll set the parent on comments when we store the initial post (item_store()) and only go back and set the parent for top-level posts. This should reduce the number of comments with missing parents on shared hosts, but may increase the number of missing threads. Probably worthwhile to do a query occasionally for parent = 0 and see how we're doing and how many have shared host related delivery issues.
|
| | |
|