| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
may require tweaking.
|
|
|
|
| |
to do a DB update if the build number is 0. Something else will likely fail and likely in some horrible way, but we shouldn't try and update the DB - something is clearly wrong with it.
|
| |
|
|
|
|
| |
could be a strong selling point.
|
|
|
|
| |
month which means we can find dead channels - because they won't be pinging the directory server once a month.
|
|
|
|
| |
uplink back to them without any ambiguity.
|
| |
|
| |
|
|
|
|
|
|
| |
lowercase title of the block without special chars)
Fix comanche_block() SQL
|
| |
|
|
|
|
|
|
|
|
|
| |
possibly recurse and blow up the matrix. Hard to say. Do you feel lucky? Well do ya' ... punk? Rule #1 - don't mess with anything unless it's blowing up the matrix. If it doesn't blow up the matrix, but doesn't work, just let it go and let's figure out what it is doing and what it isn't doing.
The flow is as follows:
Once a day go out to all the directory servers besides yourself and grab a list of updates. This happens in the poller. If we've never seen them before add them to the updates table. The poller also looks to see if we're a directory server and have updates that haven't yet been processed. It calls onedirsync.php to process each one. If we contact the channel to update and don't find anything (we're just doing a basic zot_finger), set a ud_last timestamp. If this is set we will only try once a day for seven days. Then we stop trying to update.
This will probably cause a spike the first time through because you haven't seen any updates before, but we spread out the load over your delivery interval.
|
| |
|
|
|
|
| |
part of the normal import_xchan sequence - otherwise we get two for every change. Create it normally if we are called with a profile_update message and don't go through the whole import_xchan thing.
|
| |
|
| |
|
|
|
|
| |
the parent xchan is safe or not. Otherwise we'll have tags that lead to nowhere because the directory entry is hidden but the tag isn't. A successful porn site in the matrix could also swamp the directory with x-rated tags, even if the site was playing nice and did everything right to self-censor. Accomplishing this with joins would be horrendously inefficient, though it will take a bit of code re-org to get this flag where it needs to be when it's time to set keywords.
|
|
|
|
| |
adult profile keywords. Eventually the directories will be forced to mark adult profiles and sync this knowledge between them. At the moment there's no way to do an unsafe search, but we really just need a checkbox and pass the value through directory to dirsearch on the back end, and some will want this as a pconfig.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
boot.php
install/database.sql
install/update.php
|
| |
| |
| |
| | |
updates have been processed in some way.
|
| |
| |
| |
| | |
to update table to store the target address since it's possible the mirroring directory won't yet have an xchan or hubloc they can link the ud_hash to and therefore mayn't know how to contact them.
|
|/
|
|
| |
(directory sync) updates have been processed in some way.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
directory sync. Please do not mess with any of this.
Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this.
OK? Understood?
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
for a kind of traffic light to get an overview.
|
|/ |
|
| |
|
| |
|
|
|
|
| |
updated their site access policy which old sites do not have)
|
| |
|
| |
|
| |
|
|\
| |
| | |
More mobile theme fixes
|
| |
| |
| |
| |
| |
| | |
If user is logged in personal settings are used else use admin
settings.
Only show toggle link if there is something to switch between.
|
|/
|
|
| |
as a block editor, and probably a layout editor as well. Eventually, these should all probably just be switches onto a single editor instance. Decided to put the layout_mid into the item table directory rather than re-use resource_id, so that we can still have pages attached to different resources like photos and events and stuff. The block editor is far from finished, at this point I've only cloned it and changed the name and type of item it looks for.
|
| |
|
|
|
|
| |
now. This does not mean it's close to being presentable - far from it.
|
|
|
|
| |
dns name
|
|
|
|
| |
will still work
|
| |
|
|
|
|
| |
warnings
|
| |
|