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

	Commit message (Collapse)	Author	Age	Files	Lines
*	log why this doesn't get executed	friendica	2014-09-12	1	-0/+2
\|
*	works one way sort of - now to go the other way - which will require fixing ↵	friendica	2014-08-26	1	-3/+3
\| \| \| \|	a whole slew of FIXMEs
*	houston we have liftoff	friendica	2014-08-26	1	-1/+1
\|
*	more diaspora stuff - most of the basic bits are there except queueing and ↵	friendica	2014-08-25	1	-1/+1
\| \| \| \|	physical delivery (I'm keeping delivery turned off until some of the bugs are fixed so we don't cause inifinite loops or network meltdowns) - now it's just a matter of going through and methodically finding all the bugs
*	sort out some anomalies	friendica	2014-08-25	1	-2/+2
\|
*	more diaspora heavy lifting	friendica	2014-08-25	1	-17/+60
\|
*	We really can't do this without a hubloc. I was hoping we could, but ↵	friendica	2014-08-22	1	-1/+1
\| \| \| \|	notifier is setup to take hublocs, not xchans.
*	homepage revisions	friendica	2014-07-06	1	-8/+9
\|
*	make folks from certain other networks feel more at home here	friendica	2014-05-02	1	-0/+8
\|
*	tag anyone	friendica	2014-04-15	1	-17/+3
\|
*	make sure we can find that function	friendica	2014-04-11	1	-0/+1
\|
*	we also need a loop breaker	friendica	2014-04-11	1	-0/+6
\|
*	this should improve queue performance dramatically.	friendica	2014-03-24	1	-2/+4
\|
*	we don't allow forgeries to be received - save some bandwidth by not ↵	friendica	2014-03-21	1	-0/+5
\| \| \| \|	allowing them to be sent. We do have to figure out how some secondary delivery chains are ending up with posts belonging to the original owner instead of the chain owner, but that's for another day.
*	try to reduce the number of simulaneous deliveries of the same post when ↵	friendica	2014-01-22	1	-2/+22
\| \| \| \|	dealing with owner relays that have more than one channel instance. If things melt down in the next few hours and I'm not available please revert this. I've reviewed a few times and think it's OK, but this part of the delivery code is traditionally touchy.
*	this is necessary for any possibility of a federated future.	friendica	2013-11-21	1	-1/+16
\|
*	add aid to notifiy table which we may need to supress duplicate notify ↵	friendica	2013-11-20	1	-4/+8
\| \| \| \| \| \|	emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
*	create update record for accounts on directory server itself during profile ↵	friendica	2013-10-24	1	-1/+1
\| \| \| \|	changes, re-queue failed directory sync packets, fix account_id index in queue creation, be more selective about updating hubloc_connected (only when we're talking to the associated site). But we still need a way to flag dead accounts and these mechanisms won't cut it, because it isn't a requirement that channels communicate with anybody, except for contacting the directory when the account is created. I think we need to make every channel ping the directory once a month. Then we can find those that have not done so (after syncing with other directories). We can't have the directory just flag dead accounts as this would create a way for an anti-social attacker to become a directory server and mark all the accounts dead.
*	preserve the source owner when creating a delivery fork so that we can ↵	friendica	2013-10-13	1	-2/+3
\| \| \| \|	uplink back to them without any ambiguity.
*	Pieces we'll need to tie together chanman and account/channel deletion and ↵	friendica	2013-09-17	1	-5/+30
\| \| \| \| \| \| \| \|	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?
*	doc update, put more telemetry on notifier and try to ensure that private ↵	friendica	2013-09-13	1	-0/+4
\| \| \| \|	posts have recipients.
*	perform a refresh_all when an import has completed so that all your ↵	friendica	2013-09-08	1	-3/+2
\| \| \| \|	connections get a fresh update.
*	Add Comanche layouts to the things that don't go offsite.	friendica	2013-09-01	1	-0/+4
\|
*	most of expire is now ported from friendica, but the protocol bits to push ↵	friendica	2013-08-14	1	-4/+15
\| \| \| \|	out the delete notifications for the entire batch to all recipients of the original post are not complete and will take quite a bit more work. As a consequence, expire has been completely disabled until it is fully implmented since it could result in completely un-removable posts reminiscent of the infamous "Bonnie Nadri" incident at Diaspora which we do not wish to re-live.
*	block content-type (called ITEM_BUILDBLOCK to avoid confusion with content ↵	friendica	2013-08-12	1	-0/+5
\| \| \| \|	that is blocked)
*	yhis should fix the privacy leak - as well as non-private replies to private ↵	friendica	2013-08-01	1	-1/+4
\| \| \| \|	posts
*	privacy leakage	friendica	2013-07-31	1	-1/+1
\|
*	improvements in delivery logging	friendica	2013-07-21	1	-8/+25
\|
*	fix profile update propagation	friendica	2013-06-18	1	-3/+3
\|
*	don't federate webpages ;-)	friendica	2013-06-15	1	-0/+6
\|
*	push refresh messages, performance work on conversations and configs, doc ↵	friendica	2013-06-14	1	-12/+51
\| \| \| \|	updates
*	zidify img links, delay notifier until actually published for time ↵	friendica	2013-05-27	1	-0/+4
\| \| \| \|	travelling posts
*	workarounds for people that re-install and end up polluting everybody's ↵	friendica	2013-05-16	1	-2/+2
\| \| \| \|	databases with stale entries
*	start formatting for Doxygen	friendica	2013-02-25	1	-1/+1
\|
*	delete item should now mostly work	friendica	2013-01-28	1	-1/+5
\|
*	uncomplicate item deletion and fixup all the other linked tables	friendica	2013-01-24	1	-3/+4
\|
*	this should make tag delivery (e.g. forums) work - but not yet fully tested	friendica	2013-01-13	1	-3/+18
\|
*	never enough documentation	friendica	2013-01-04	1	-3/+14
\|
*	This should fix the errant relaying...	friendica	2013-01-04	1	-2/+6
\|
*	fix typo - commited to wrong tree	friendica	2013-01-04	1	-1/+7
\|
*	break delivery loop	friendica	2013-01-04	1	-1/+5
\|
*	verify table needs auto_increment flag	friendica	2013-01-02	1	-2/+2
\|
*	cleanup more obsolete stuff	friendica	2012-12-18	1	-2/+2
\|
*	y'all got mail	friendica	2012-12-05	1	-51/+75
\|
*	Now if you follow somebody it will create an abook entry on the other site ↵	friendica	2012-11-29	1	-1/+3
\| \| \| \|	with blocked,ignored, and pending set. No "friend notifications" yet.
*	got comments going back and forth - we really need local_deliver now since ↵	friendica	2012-11-27	1	-10/+10
\| \| \| \|	even local deliveries are going through zot and that isn't necessary or desirable in the long term
*	tracking through comments	friendica	2012-11-27	1	-3/+9
\|
*	DATABASE: outq additions, delivery now getting the notify across to the ↵	friendica	2012-11-19	1	-2/+5
\| \| \| \|	other side
*	For private messages, use hush-hush ultra top-secret mode by default	friendica	2012-11-18	1	-7/+7
\|
*	Now we are able to get a zot notification packet and the resulting json ↵	friendica	2012-11-18	1	-535/+50
\| \| \| \|	encoded message into the queue, it's still a hard slog, but there's light at the end of the tunnel - "a message is ready and waiting to be delivered".