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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Ability to close comments at a certain date/time - needed for loom.io ↵	friendica	2014-08-28	1	-0/+3
\| \| \| \|	emulation (and many other uses)
*	mind numbing drudgery continued...	friendica	2014-08-27	1	-0/+2
\|
*	place to store multiple choice and select items for extensible profiles	friendica	2014-08-26	1	-0/+1
\|
*	more hard work	friendica	2014-08-26	1	-0/+26
\|
*	We really can't do this without a hubloc. I was hoping we could, but ↵	friendica	2014-08-22	1	-0/+2
\| \| \| \|	notifier is setup to take hublocs, not xchans.
*	provide backend storage and declaration of directory realm	friendica	2014-08-16	1	-1/+3
\|
*	item table upgrade for storing post visibility	friendica	2014-08-06	1	-0/+2
\|
*	db tables for extensible profile fields	friendica	2014-08-02	1	-0/+22
\|
*	block channel removal for 48 hours after changing the account password, ↵	friendica	2014-07-29	1	-1/+3
\| \| \| \|	since the password is required to remove a channel. Somebody looking at an open session on somebody else's computer can simply change the password and then proceed to maliciously remove the channel. This change gives the owner 2 days to discover that something is wrong and recover his/her password and potentially save their channel from getting erased by the vandal. This is most likely to happen if a relationship has gone bad, or something incriminating was found in your private messages when you left your computer briefly unattended.
*	provide a specific permission for liking profiles (reuse the obsolete ↵	friendica	2014-07-17	1	-2/+2
\| \| \| \|	bookmark permission), also remove the unused 'unconnected contacts' view for now.
*	ability to like things	friendica	2014-06-23	1	-1/+3
\|
*	honour the admin censored flag in the directory, and some slow progress on ↵	friendica	2014-06-22	1	-1/+3
\| \| \| \|	extended likes
*	likes table for liking things besides posts and comments	friendica	2014-06-22	1	-0/+16
\|
*	implement 'requires' on personal apps	friendica	2014-05-22	1	-0/+1
\|
*	more app backend work	friendica	2014-05-19	1	-1/+1
\|
*	support commerical apps	friendica	2014-05-18	1	-1/+5
\|
*	app DB structure	friendica	2014-05-17	1	-0/+22
\|
*	use parent_mid in the parent query for enotify instead of of the parent id. ↵	friendica	2014-04-06	1	-1/+1
\| \| \| \|	This should fix the issue with encrypted content in the notification messages (for locally posted replies). The fix was a bit harder than anticipated because we store the parent id as an int in the notify table so this had to be modified to char storage as well.
*	more efficient public feed fetching	friendica	2014-04-02	1	-1/+2
\|
*	finish up the source route storage so we can prevent messages from flowing ↵	friendica	2014-03-31	1	-11/+12
\| \| \| \|	upstream in complicated delivery chains
*	Typo in database.sql	Thomas Willingham	2014-03-07	1	-1/+1
\|
*	put bookmarked chatrooms into poco	friendica	2014-02-25	1	-1/+3
\|
*	more chatroom discovery	friendica	2014-02-25	1	-0/+11
\|
*	Also update database.sql	Thomas Willingham	2014-02-25	1	-12/+12
\|
*	set default for account_level in DB	friendica	2014-02-07	1	-1/+1
\|
*	bookmark permissions	friendica	2014-02-04	1	-0/+2
\|
*	chat expiration (default 2 hours) - but can be set on a per-chatroom basis	friendica	2014-01-30	1	-1/+3
\|
*	add client field to chatpresence - which will give us a place to put IP ↵	friendica	2014-01-28	1	-0/+1
\| \| \| \|	addresses for webRTC. Might as well allow for that since we'll (soon) have presence. Then we wouldn't need SIP and folks can "just" p2p each other using any mechanism they wish if they have permission to do so.
*	chat data structures	friendica	2014-01-27	1	-8/+52
\|
*	allow menus to have special roles	friendica	2014-01-15	1	-1/+3
\|
*	only let visitors remove their own files.	friendica	2014-01-09	1	-0/+2
\|
*	allow objects to have permissions	friendica	2013-12-28	1	-0/+4
\|
*	db update for directory profiles - and fix broken database.sql from the ↵	friendica	2013-12-25	1	-13/+18
\| \| \| \|	sys_perms addition a couple days back
*	add account_level, is_foreigner and is_member functions; convert all e2ee ↵	friendica	2013-12-23	1	-1/+3
\| \| \| \|	user input and prompts to hex to avoid javascipt's lame handling of quotes. !!This breaks all prior encrypted posts.!!
*	remove a couple of mysql reserved words from being used as table or row ↵	friendica	2013-12-22	1	-3/+3
\| \| \| \|	names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
*	Ooops, also update the DB	Thomas Willingham	2013-12-22	1	-0/+8
\|
*	add aid to notifiy table which we may need to supress duplicate notify ↵	friendica	2013-11-20	1	-1/+3
\| \| \| \| \| \|	emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
*	remove the challenge table as well	friendica	2013-11-18	1	-10/+0
\|
*	drop the queue table which we no longer use	friendica	2013-11-18	1	-16/+0
\|
*	DB - allow private messages to expire	friendica	2013-11-06	1	-18/+19
\|
*	Fix missing parenthesis in database.sql	Antoine G	2013-11-01	1	-1/+1
\| \| \|	This was blocking database creation process
*	allow zot public providers to list their location, as a non US-based server ↵	friendica	2013-10-30	1	-0/+1
\| \| \| \|	could be a strong selling point.
*	Schema change - add channel_dirdate so we can ping a directory server once a ↵	friendica	2013-10-27	1	-0/+2
\| \| \| \|	month which means we can find dead channels - because they won't be pinging the directory server once a month.
*	preserve the source owner when creating a delivery fork so that we can ↵	friendica	2013-10-13	1	-0/+1
\| \| \| \|	uplink back to them without any ambiguity.
*	post signatures	friendica	2013-10-02	1	-1/+1
\|
*	implement republish permission for use in sourced channels	friendica	2013-09-30	1	-0/+2
\|
*	directory sync - this will either work, or it won't work, or it will ↵	friendica	2013-09-30	1	-1/+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.
*	structure for channel unions	friendica	2013-09-26	1	-0/+12
\|
*	add a flag field to xtags so that we can filter tags based on whether or not ↵	friendica	2013-09-19	1	-1/+3
\| \| \| \|	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.
*	sync item_search with yesterday's network fix for collections. Add ud_addr ↵	friendica	2013-09-19	1	-1/+3
\| \| \| \|	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.