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

	Commit message (Collapse)	Author	Age	Files	Lines
*	add "any connections" to can_comment_on_post() - was missing	friendica	2014-08-23	1	-0/+1
\|
*	switch everything over to crypto_encapsulate()	friendica	2014-08-23	1	-4/+4
\|
*	issue #573 - this may not fix everything in that issue but should resolve ↵	friendica	2014-08-22	1	-0/+3
\| \| \| \|	some of it.
*	"false" issue	friendica	2014-08-22	1	-4/+9
\|
*	issue #571 - use feed/nickname?top=1	friendica	2014-08-22	1	-1/+6
\|
*	profile edit - missing visibility and drop link on non-default profiles, ↵	friendica	2014-08-21	1	-4/+4
\| \| \| \|	re-arrange order of replacing red#matrix smilie so it works correctly, accept a post with body content of '0' which was interpreted by x() as nothing (was treated as integer).
*	extensible profiles - add the input form elements. Still needs styling and ↵	friendica	2014-08-20	1	-135/+99
\| \| \| \|	we're not yet storing the results. And right now we're ignoring the type and only doing type=string. Oh yeah - and I split off starting the second delivery chain into its own function in tag_deliver since it was largely duplicate code.
*	restructure the author and owner info from feeds	friendica	2014-08-20	1	-85/+58
\|
*	greatly simplify consume_feed() - a lot of this was friendica specific and ↵	friendica	2014-08-20	1	-195/+49
\| \| \| \|	somebody may want to put some of it back in, but we'd be much better off building a zot compatible feed for friendica (hint,hint) - even if it didn't support the other protocol bits. Special purpose feed handlers for things like likes, dislikes, events, and community tags are better handled as zot arrays. We have all those handlers. We just need to pass them a JSON message instead of an XML/Atom message. Handlers for statusnet follow messages are another casualty. That's easy to bring back - but we need to keep driving nails into the XML coffin or the damn zombies will get out.
*	fangs bared	friendica	2014-08-19	1	-1/+23
\|
*	snakebite continued	friendica	2014-08-19	1	-53/+108
\|
*	also reset comment policy on alternate delivery chains	friendica	2014-08-19	1	-2/+4
\|
*	make sure privacy scope is completely reset on second delivery chain - ↵	friendica	2014-08-19	1	-8/+62
\| \| \| \|	revert if there are forum issues, this is subtle and complicated
*	implement max_import_size	friendica	2014-08-09	1	-1/+7
\|
*	booboo	friendica	2014-08-09	1	-1/+2
\|
*	a couple of "not quite public" fixes	friendica	2014-08-08	1	-10/+6
\|
*	cleanup some text where we said "public" or "visible to anybody on the ↵	friendica	2014-08-07	1	-1/+1
\| \| \| \|	internet" when that isn't necessarily true.
*	a bit more cleanup and a bug fix or two for the new private post security model	friendica	2014-08-07	1	-8/+15
\|
*	public scope delivery issues	friendica	2014-08-06	1	-2/+5
\|
*	basic 'notpublic' bits working	friendica	2014-08-06	1	-6/+28
\|
*	first step first - just store the public_policy data, don't do anything with ↵	friendica	2014-08-06	1	-0/+12
\| \| \| \|	it yet.
*	add an encoding type to formatted zot communication structures so that we ↵	friendica	2014-07-24	1	-0/+2
\| \| \| \|	can later add alternate encodings.
*	clean up more code duplication	friendica	2014-07-14	1	-1/+1
\|
*	remove some code duplication	friendica	2014-07-14	1	-18/+4
\|
*	when deleting items, delete linked events and photos during stage1	friendica	2014-07-04	1	-13/+13
\|
*	minor optimisation	friendica	2014-07-01	1	-8/+4
\|
*	notification being sent for comments from blocked connections on same site.	friendica	2014-06-26	1	-0/+1
\|
*	process profile like removals with normal low_level drop_item	friendica	2014-06-23	1	-0/+9
\|
*	Implements a new permission level PERMS_PENDING	Alexandre Hannud Abdo	2014-06-19	1	-6/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	With this a user can allow some action to any user which connects to them, even before they've connected back. Ref. https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com Also some code cleanup and an alternative logic for handling notifications of permission changes in zot.php. This assumes that private posts are still restricted to people in your addressbook. Regardless of your global permissions, a pending channel won't get private posts, even if the post only has a deny clause not matching the pending channel.
*	access control modification functions (item specific - we may need these for ↵	friendica	2014-06-17	1	-0/+35
\| \| \| \|	several data types)
*	issues with editing webpage permissions	friendica	2014-06-15	1	-2/+4
\|
*	webpage permissions weirdness	friendica	2014-06-14	1	-6/+8
\|
*	poke notifications	friendica	2014-06-04	1	-0/+28
\|
*	Make tag delivery work when channel name differs from profile name	Alexandre Hannud Abdo	2014-05-21	1	-5/+5
\|
*	zrlify (turn into zmg) any relevant img tags in a post.	friendica	2014-05-13	1	-0/+25
\|
*	issue #432 permission changes lost editing webpage (and other non-post items)	friendica	2014-05-04	1	-2/+0
\|
*	posted_dates() needs a re-write so we can make a much prettier archive widget	friendica	2014-04-30	1	-1/+41
\|
*	Remove automatic bookmarking - it was a bad idea and just leads to menu ↵	friendica	2014-04-30	1	-21/+0
\| \| \| \|	clutter. Bookmarks can always be saved manually if desired.
*	A useful hook	friendica	2014-04-25	1	-0/+5
\|
*	ability to unset a layout and subthread is probably close to working again.	friendica	2014-04-23	1	-8/+24
\|
*	this should fix mention notification that aren't plus tagged	friendica	2014-04-19	1	-4/+20
\|
*	more optimisations for discovery mode of zotfeed	friendica	2014-04-17	1	-2/+6
\|
*	improve zotfeed for discover channel so it will send updates to posts you've ↵	friendica	2014-04-17	1	-7/+7
\| \| \| \|	already received. Incidentally I discovered why we had the meltdown replying to discover channel items the other day - but can't fix it easily.
*	no this is the way to do it	friendica	2014-04-11	1	-2/+2
\|
*	Use @+ to tag a forum and also restrict the post to the forum, this leaves ↵	friendica	2014-04-11	1	-2/+2
\| \| \| \|	@! tags private - period.
*	move the deleted flag setting to encode_item_flags() where it belongs now ↵	friendica	2014-04-10	1	-4/+3
\| \| \| \|	that we aren't giving deleted posts special treatment.
*	Include the entire original item when notifying other channels of deletions ↵	friendica	2014-04-10	1	-5/+0
\| \| \| \|	as it contains important routing and scope information. Previously we were only sending a couple of critical fields like the message-id, flags, and creation date. The thinking was that it is deleted, let's not resend the deleted contents anywhere. But in order to route this through the same path the original post took we really need the entire original post with all of its baggage attached.
*	wrong var name in add_source_route	friendica	2014-03-31	1	-2/+2
\|
*	crank up logging	friendica	2014-03-31	1	-0/+2
\|
*	community tags don't show up in the tagged posts because we removed the ↵	friendica	2014-03-31	1	-0/+1
\| \| \| \|	displayed list of hashtags at the bottom (which are usually redundant since hashtags are usually present in the message text). This brings them back, but only for tags which aren't currently present in the message body (e.g. community tags)