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

	Commit message (Collapse)	Author	Age	Files	Lines
*	doc update, put more telemetry on notifier and try to ensure that private ↵	friendica	2013-09-13	1	-0/+3
\| \| \| \|	posts have recipients.
*	remove some debugging stuff now that the problem they were trying to locate ↵	friendica	2013-09-12	1	-5/+0
\| \| \| \|	down has been solved.
*	make comments work again	friendica	2013-09-10	1	-1/+2
\|
*	well that really stuffed things up...	friendica	2013-09-10	1	-1/+1
\|
*	this should fix the foreign language like notifications (again)	friendica	2013-09-10	1	-2/+4
\|
*	change wording on item_store message so we can find failures fast with grep ↵	friendica	2013-09-10	1	-1/+1
\| \| \| \|	item_store logfile \| grep -v created
*	provide detailed error to remote site for the myriad of things that can go ↵	friendica	2013-09-10	1	-19/+44
\| \| \| \|	wrong inside item_store(), !! this changes the return of item_store !!
*	pages feed	friendica	2013-09-05	1	-15/+29
\|
*	issue #59 - this is a real bugger. Might seem fixed but read the code. This ↵	friendica	2013-09-04	1	-2/+7
\| \| \| \|	could potentially create a security/permissions issue
*	fix private message encryption since the input_filter mangled it	friendica	2013-09-03	1	-2/+2
\|
*	webpage content-type -- needs cleaning up and a security check once all the ↵	friendica	2013-09-02	1	-7/+3
\| \| \| \|	important bits are in place.
*	Sheesh. Three lines of Javascript. All you have to do is find which of the ↵	friendica	2013-09-01	1	-0/+11
\| \| \| \|	three lines is doing something wrong. Or FILE A BUG. Or use a different browser (not try a different browser, use a different browser), or turn off freaking tinymce. But no - let's argue about browsers instead.
*	get rid of ssl_policy - it's implicit in the site url	friendica	2013-08-27	1	-16/+16
\|
*	email attachments (and fix email photos)	friendica	2013-08-19	1	-0/+10
\|
*	item_store logging to discover where object is getting quote mangled.	friendica	2013-08-18	1	-1/+4
\|
*	Another try at issue #61 and #62 - an earlier fix was partially working but ↵	friendica	2013-08-18	1	-9/+14
\| \| \| \|	the issue persisted - this extends it a bit.
*	don't include archived contacts in public posts, unless specifically requested	friendica	2013-08-15	1	-2/+3
\|
*	typo	friendica	2013-08-14	1	-1/+1
\|
*	fix expire so it actually should expire stuff; and mostly the correct stuff ↵	friendica	2013-08-14	1	-11/+17
\| \| \| \|	- though it DOESN'T currently send out notifications to connections
*	important bits we need to allow php executable content. These must be ↵	friendica	2013-08-11	1	-18/+35
\| \| \| \|	explicitly allowed - but only if the account has ACCOUNT_ROLE_ALLOWCODE and only for web pages and profile fields. This content cannot be transmitted to other sites.
*	remove some un-needed code	friendica	2013-08-07	1	-1320/+10
\|
*	convert all stored json calls to json_decode_plus()	friendica	2013-08-06	1	-9/+9
\|
*	add extra logging to tag_deliver	friendica	2013-08-05	1	-2/+6
\|
*	potentially fixes the "federation" bug w/r/t/ tagged forums	friendica	2013-08-01	1	-2/+2
\|
*	pass item by reference so title can be altered	friendica	2013-08-01	1	-12/+20
\|
*	ensure that no unencrypted content leaks through item_store which is private ↵	friendica	2013-08-01	1	-9/+24
\| \| \| \| \| \|	- we typically do this in mod/item, but some functions bypass mod/item to create private posts
*	fix some privacy leakage in logs	friendica	2013-07-31	1	-0/+15
\|
*	better mail obscuring	friendica	2013-07-31	1	-15/+15
\|
*	zot feed - getting cut off too early	friendica	2013-07-29	1	-6/+9
\|
*	ensure conversation is included	friendica	2013-07-29	1	-0/+1
\|
*	fix some weirdness on the zot feed	friendica	2013-07-29	1	-12/+21
\|
*	fix bug #84, make imported messages from your clones show up on your wall	friendica	2013-07-29	1	-0/+5
\|
*	tgroup_check wasn't allowing comments through.	friendica	2013-07-29	1	-2/+9
\|
*	encrypt private messages on disk - there are still a couple of places where ↵	friendica	2013-07-28	1	-2/+10
\| \| \| \|	the text is leaked in the logs during processing.
*	make zot_finger more bulletproof	friendica	2013-07-21	1	-1/+1
\|
*	private mail is just a little more private now. Not encrypted and the ↵	friendica	2013-07-19	1	-5/+20
\| \| \| \| \| \|	obfuscation is easily reversible, but not casually readable by browsing logfiles or mysql dumps. This isn't backward compatible - folks will have to upgrade if they can't read their mail.
*	add channel_name to delivery logs because it is a bit more useful than an ↵	friendica	2013-07-15	1	-1/+2
\| \| \| \|	xchan_hash
*	fix some issues that showed up in the logs.	friendica	2013-07-15	1	-0/+7
\|
*	Add self to recipient lists. Sure we already have a copy but it's possible ↵	friendica	2013-07-14	1	-0/+5
\| \| \| \|	our nomadic channel clones don't.
*	some work on issue #62 (comments collapsing on liveupdate), but still a work ↵	friendica	2013-07-02	1	-3/+0
\| \| \| \| \| \|	in progress some work on photo consolidated "view/edit", but still a work in progress
*	fix some community tagging bugs	friendica	2013-06-30	1	-1/+3
\|
*	add age to directory profile - requires updating on each birthday and that ↵	friendica	2013-06-30	1	-0/+1
\| \| \| \|	part is still missing
*	doc update, plus possible fix to "complex delivery chains" issue. Basically ↵	friendica	2013-06-29	1	-1/+40
\| \| \| \|	when the top-level post creator replies to a thread he sent to a forum via tags, it isn't getting redelivered to the forum members.
*	fix cid query	friendica	2013-06-27	1	-1/+1
\|
*	community tag issues	friendica	2013-06-20	1	-2/+7
\|
*	found it - but I'll do some more testing before undoing the bypass	friendica	2013-06-16	1	-1/+1
\|
*	undefined function	friendica	2013-06-16	1	-1/+1
\|
*	typos	friendica	2013-06-16	1	-2/+2
\|
*	implement 'can_comment_on_post()' which doesn't require a separate DB lookup ↵	friendica	2013-06-16	1	-1/+41
\| \| \| \|	per item.
*	We will need a per item comment policy to be able to determine in advance if ↵	friendica	2013-06-16	1	-3/+12
\| \| \| \|	we have permission to comment on something , and we'll need to send it out with all communications. The current check is not only flawed but also a huge performance hit. Also provide the ability for an item to disable commenting completely - such as for a webpage or wherever you want to prevent comments on one item, without requiring a change to your entire permission scheme. All of this is only partially implemented at the moment but we need the structures in place on several sites in order to finish it without breaking everything.