volse-hubzilla.git - Volse Hubzilla -- soft fork of main Hubzilla core for Volse

	Commit message (Collapse)	Author	Age	Files	Lines
*	Saved searches on the matrix/network page just got a lot more interesting. ↵	friendica	2013-10-01	2	-37/+43
\| \| \| \|	Hint: it's all about autocomplete
*	search_ac is really whacked - help it out a bit, but much more to do	friendica	2013-10-01	1	-17/+17
\|
*	add link to channel source management in settings if channel_sources feature ↵	friendica	2013-09-30	1	-0/+9
\| \| \| \|	is enabled
*	implement republish permission for use in sourced channels	friendica	2013-09-30	1	-18/+22
\|
*	small fixes	friendica	2013-09-30	2	-3/+12
\|
*	directory sync - this will either work, or it won't work, or it will ↵	friendica	2013-09-30	1	-6/+4
\| \| \| \| \| \| \| \| \|	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.
*	there's our directory sync packet (aka transaction log). Now we just have to ↵	friendica	2013-09-29	1	-4/+14
\| \| \| \|	pass them around and act on them.
*	log any attempt to call mod_magic	friendica	2013-09-29	1	-0/+2
\|
*	sources management page	friendica	2013-09-29	1	-0/+140
\|
*	Missing include	Thomas Willingham	2013-09-29	1	-1/+1
\|
*	Issue #158	friendica	2013-09-29	2	-3/+10
\|
*	fix can_comment_on_post when viewing wall-to-wall	friendica	2013-09-28	1	-8/+14
\|
*	structure for channel unions	friendica	2013-09-26	1	-5/+0
\|
*	suppress creating the directory update record for profile updates which are ↵	friendica	2013-09-25	1	-3/+7
\| \| \| \|	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.
*	Fix name of Bleichenbacher	Olaf Conradi	2013-09-24	1	-2/+2
\|
*	Merge https://github.com/friendica/red into zpull	friendica	2013-09-24	1	-0/+20
\|\
\| *	admin hubloc page now with content from all hublocs, in next steps I add ↵	Michael Meer	2013-09-24	1	-0/+20
\| \| \| \| \| \| \| \|	some tests with zping and reduce the content to known problems.
* \|	reduce susceptibility to bleichenberger attack	friendica	2013-09-24	1	-6/+18
\|/
*	oauth settings - clarify text	friendica	2013-09-23	1	-6/+13
\|
*	one more edge case in the public perms - don't match perms = 0 which is ↵	friendica	2013-09-22	2	-4/+4
\| \| \| \|	private, this and prior checkin are for issue #114
*	fixes for display and search privacy enforcement	friendica	2013-09-22	2	-26/+40
\|
*	adult channel setting	friendica	2013-09-22	3	-6/+16
\|
*	clean up app management a bit	friendica	2013-09-20	1	-5/+5
\|
*	hopefully(?) the final word on remote comment permissions	friendica	2013-09-20	1	-0/+3
\|
*	when it's a contentious issue, make it an option.	friendica	2013-09-20	1	-4/+8
\|
*	hopefully this will go over a bit better - check post owner permissions as ↵	friendica	2013-09-20	2	-2/+10
\| \| \| \|	well as local owner permissions for comments during submission, since the comment was being blindly accepted on the local system due to only checking the profile owner. Also change collections query to include only top-level posts by a member of the collection.
*	typo	friendica	2013-09-19	1	-1/+1
\|
*	now bring it to the url	friendica	2013-09-19	1	-0/+2
\|
*	bring safe mode to the client side	friendica	2013-09-19	1	-1/+12
\|
*	use &safe=-1 for unsafe only	friendica	2013-09-19	1	-1/+4
\|
*	Merge https://github.com/friendica/red into zpull	friendica	2013-09-19	1	-1/+4
\|\
\| *	Use get_config	Thomas Willingham	2013-09-20	1	-1/+1
\| \|
\| *	Make $kw configurable.	Thomas Willingham	2013-09-20	1	-1/+4
\| \|
* \|	provide a "safe search" backend and allow for self-censorship using nsfw or ↵	friendica	2013-09-19	1	-2/+6
\|/ \| \| \|	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.
*	Merge https://github.com/friendica/red into zpull	friendica	2013-09-19	1	-1/+2
\|\
\| *	Add tiered access option.	Thomas Willingham	2013-09-19	1	-1/+2
\| \|
* \|	prefill private mail recip from $_REQUEST['to'] if it's there.	friendica	2013-09-19	1	-0/+5
\|/
*	add "tiered" access policy, add tagcloud to directory pages	friendica	2013-09-18	3	-4/+17
\|
*	make collections work again	friendica	2013-09-18	1	-4/+9
\|
*	provide the back-end for a directory tag cloud	friendica	2013-09-17	1	-1/+9
\|
*	site sellpage links	friendica	2013-09-17	3	-2/+3
\|
*	Pieces we'll need to tie together chanman and account/channel deletion and ↵	friendica	2013-09-17	2	-1/+4
\| \| \| \| \| \| \| \|	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?
*	Didn't git add again after fixing typo...	Thomas Willingham	2013-09-18	1	-1/+1
\|
*	Filestorage perms (no ACL), fix nav for browsers that can't handle PCSS, put ↵	Thomas Willingham	2013-09-18	1	-0/+20
\| \| \| \|	content wrapper back now JS is fixed for features page.
*	sync photo permissions with the attached item whenever they change.	friendica	2013-09-17	2	-2/+20
\|
*	Merge pull request #142 from dsp1986/master	friendica	2013-09-17	1	-1/+1
\|\ \| \| \| \| \| \| \| \|	Thanks! fix include paths
\| *	fix include paths	dsp1986	2013-09-17	1	-1/+1
\| \|
* \|	removed logger statement	Michael Meer	2013-09-17	1	-1/+0
\| \|
* \|	extend admin page for hubloc / server key management	Michael Meer	2013-09-17	2	-0/+17
\| \|
* \|	assuming permissions are correct, unobscure photo comments. Should probably ↵	friendica	2013-09-16	1	-1/+2
\| \| \| \| \| \| \| \|	make sure permissions are correct and figure out why some photo comments on public photos are getting stored with privacy. This probably requires that whenever we change photo permissions for linked photos/items we change the item permissions to match. They might be out of sync.