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

	Commit message (Collapse)	Author	Age	Files	Lines
*	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.
*	set default charset of email_header_encode, add ud_flags to indicate which ↵	friendica	2013-09-18	1	-1/+3
\| \| \| \|	(directory sync) updates have been processed in some way.
*	site sellpage links	friendica	2013-09-17	1	-1/+3
\|
*	Fixed error in SQL Statement	ndurchx	2013-09-12	1	-1/+1
\|
*	extends DB in hubloc to maintain hubloc connectivity	Michael Meer	2013-09-10	1	-0/+2
\|
*	change primary key on updates table	friendica	2013-09-09	1	-1/+3
\|
*	public site list (will take a few days to populate, assuming folks have ↵	friendica	2013-09-05	1	-0/+2
\| \| \| \|	updated their site access policy which old sites do not have)
*	This isn't optimal, but on the short term we'll clone the page editor to use ↵	friendica	2013-09-01	1	-2/+2
\| \| \| \|	as a block editor, and probably a layout editor as well. Eventually, these should all probably just be switches onto a single editor instance. Decided to put the layout_mid into the item table directory rather than re-use resource_id, so that we can still have pages attached to different resources like photos and events and stuff. The block editor is far from finished, at this point I've only cloned it and changed the name and type of item it looks for.
*	add a guid to directory update table to avoid recursion	friendica	2013-08-31	1	-0/+2
\|
*	basic structure for premium channel implementation	friendica	2013-08-21	1	-0/+4
\|
*	poll stuff	friendica	2013-08-21	1	-1/+26
\|
*	network-wide poll voting structure	friendica	2013-08-20	1	-18/+28
\|
*	email attachments (and fix email photos)	friendica	2013-08-19	1	-0/+1
\|
*	check these in so I can go back and find out why the stylsheet is horked	friendica	2013-08-11	1	-1/+5
\|
*	basic account removal, but the channel removal which it calls still needs ↵	friendica	2013-08-04	1	-22/+0
\| \| \| \|	(lots of) work. Oh and the intro table is no longer used and won't be - so it's gone.
*	add "xchan_instance_url" for communicating with services that lack nomadic ↵	friendica	2013-08-01	1	-0/+2
\| \| \| \|	identity. This will be set to the url of the Red site that they are connected with. Only the nomadic identity clone at that site can communicate directly with them. Other instances will need to relay through that site - and if it goes down, that connection is stuffed.
*	better mail obscuring	friendica	2013-07-31	1	-1/+1
\|
*	fix bug #84, make imported messages from your clones show up on your wall	friendica	2013-07-29	1	-1/+1
\|
*	add chandesc field to profiles to provide some arbitrary text in the ↵	friendica	2013-07-24	1	-0/+1
\| \| \| \|	directory - such as to inform people what this channel is about before they connect. This will work best with a "channel detail" popup in the directory to provide more info than is available in the micro-profiles (when hovered, or clicked or something). And of course, the first thing is to enable this data to be stored in the directory.