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

	Commit message (Collapse)	Author	Age	Files	Lines
*	rev update and a minor fix (missing param) to force_refresh	friendica	2014-02-14	1	-1/+1
\|
*	very simple scheme	friendica	2014-02-13	1	-1/+1
\|
*	dav issue when listing protected contents from OS interface	friendica	2014-02-12	1	-1/+1
\|
*	implement a forced directory update mode where we unconditionally create a ↵	friendica	2014-02-11	1	-1/+1
\| \| \| \|	directory sync packet. This is needed to ensure that monthly directory pings are propagated to other directory servers so they can each prove for themselves whether or not an account is alive or dead. We do not trust other directories to provide us information beyond "look at this entry and decide for yourself" as doing otherwise would invite rogue directory manipulations. As this scheduled update occurs on all channels across all servers, we should also pick up refresh messages from all existing channel clones and these should also propagate out to all directory servers using the same mechanism (though perhaps not at the same time).
*	don't add bookmark tags to naked links inside code blocks	friendica	2014-02-10	1	-1/+1
\|
*	fix wall photos	friendica	2014-02-09	1	-1/+1
\|
*	create a new "subdued" CSS class for things that shouldn't be in your face ↵	friendica	2014-02-08	1	-1/+1
\| \| \| \|	unless you want them and intentionally hover over them. Typically this would be accomplished via an opacity or colour change, but themes are free to use other methods. Also changed the channel_tabs "chatroom" link to use the subdued class if no rooms have been created rather than a count of chatrooms. Themse should probably create a .subdued and .subdued:hover definition because we'll probably take most of the stuff which is now hardwired to use opacity by id and change it to use the class definition instead.
*	To be listed as a public site, you need to be an https site with a valid ↵	friendica	2014-02-07	1	-1/+1
\| \| \| \|	cert. If you don't make the cut, you will either not be listed as a public site or you will be de-listed. Period. This is non-negotiable.
*	more important things to mention. And this is still only the important stuff.	friendica	2014-02-06	1	-1/+1
\|
*	bookmark debug logging	friendica	2014-02-05	1	-1/+1
\|
*	bookmark permissions	friendica	2014-02-04	1	-1/+1
\|
*	code cleanup - remove some unused functions	friendica	2014-02-03	1	-1/+1
\|
*	add epub mimetype (application/epub+zip)	friendica	2014-02-02	1	-1/+1
\|
*	provide the room name for the room you're in.	friendica	2014-02-01	1	-1/+1
\|
*	provide some interesting new options to channel sources	friendica	2014-01-31	1	-1/+1
\|
*	a bit more ajax work on chat and chatsvc and some fiddling with layouts	friendica	2014-01-30	1	-1/+1
\|
*	basic chatroom management backend	friendica	2014-01-29	1	-1/+1
\|
*	add client field to chatpresence - which will give us a place to put IP ↵	friendica	2014-01-28	1	-1/+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.
*	cleanup include/menu in preparation for the next phase of bookmarking	friendica	2014-01-27	1	-1/+1
\|
*	don't prompt guests for a password if they're accessing an embedded public file.	friendica	2014-01-26	1	-1/+1
\|
*	get rid of bootstrap's blockqote margin css which is just bloody wrong and ↵	friendica	2014-01-25	1	-1/+1
\| \| \| \|	can't easily be over-ridden
*	prettyphoto (js\|css) not found	friendica	2014-01-24	1	-1/+1
\|
*	mod_profperm migrated	friendica	2014-01-23	1	-1/+1
\|
*	simplify chanview authentication and make sure it carries through multiple ↵	friendica	2014-01-22	1	-1/+1
\| \| \| \|	generations
*	move some store things	friendica	2014-01-21	1	-1/+1
\|
*	catch auth exceptions	friendica	2014-01-20	1	-1/+1
\|
*	add the jquery file uploader. Have been suggesting this as a replacement for ↵	friendica	2014-01-19	1	-1/+1
\| \| \| \|	the valum uploaders for quite some time - as there is client resize ability and no license incompatibilities. It still requires integration.
*	some more bookmark infrastructure plus a doc update	friendica	2014-01-18	1	-1/+1
\|
*	prevent zid's from reaching the DAV core code.	friendica	2014-01-16	1	-1/+1
\|
*	dav: throw exception if channel for requested DAV directory is deleted	friendica	2014-01-15	1	-1/+1
\|
*	mod_attach: output stream wasn't working	friendica	2014-01-11	1	-1/+1
\|
*	directory creation error, display localtimes on cloud webpage, doc updates	friendica	2014-01-10	1	-1/+1
\|
*	fix table bbcode	friendica	2014-01-09	1	-1/+1
\|
*	keep the to-do list somewhat current.	friendica	2014-01-08	1	-1/+1
\|
*	make storage limit service classes apply to accounts, not channels. Also ↵	friendica	2014-01-07	1	-2/+1
\| \| \| \|	include a css file that was missing from work yesterday.
*	version update	friendica	2014-01-06	1	-4/+1
\|
*	Merge branch 'master' into movejs	friendica	2014-01-06	1	-0/+4
\|\ \| \| \| \| \| \| \| \|	Conflicts: version.inc
\| *	whitespace	friendica	2014-01-06	1	-1/+1
\| \|
\| *	the web browser interface for DAV has now got zot	friendica	2014-01-05	1	-1/+1
\| \|
* \|	move js files from core	friendica	2014-01-04	1	-1/+1
\|/
*	more dav work	friendica	2014-01-03	1	-1/+1
\|
*	some DAV tweaks before the next round of heavy lifting	friendica	2014-01-02	1	-1/+1
\|
*	return to working on red-dav; This is a bit of a slog at the moment and the ↵	friendica	2014-01-01	1	-1/+1
\| \| \| \|	basic framework isn't even close to working. This does break the working test we did have (which was never connected to the Red backend). Now we're starting to connect Red and DAV together intimately. There will probably be some twists and turns along the way as we get the information we need into all the class objects that need them. But the important part is that the RedDirectory and RedFile classes are loading without throwing white screens and from here we can use logging to figure out what the DAV front end is trying to do and what it is passing to the backend and hopefully figure out what it expects to do with the results. Unless you're a competent developer with a strong background in OOP and are helping develop this code, you should keep it an arm's length away from any production site and don't even think of enabling it. By default it is turned off.
*	basic edit and delete for things	friendica	2013-12-30	1	-1/+1
\|
*	display_thing: it ain't much, but it's implemented.	friendica	2013-12-29	1	-1/+1
\|
*	things can now have (consistent sized) photos - plus I found a couple of ↵	friendica	2013-12-28	1	-1/+1
\| \| \| \|	issues with duplicate notifications and contact photos not getting an album name (it was crossed with filename). The last one doesn't matter as neither is used, but it was wrong so it has been corrected. Oh and thing photos weren't working at all because the form element name was different than what the module was looking for. But that had never been tested as I was waiting to get the import/resize finished. Next up for that module is display and deletion of things; but the priority is pretty low.
*	sslify - remove the redirect fallback - as it gets called occasionally and ↵	friendica	2013-12-27	1	-1/+1
\| \| \| \|	creates mixed content exceptions. Let's see how we go without it. Also a doc update.
*	issue #230 - deletion failure in multiple delivery chains	friendica	2013-12-26	1	-1/+1
\|
*	use colorbox for single photo viewing (replacing prettyPhoto, which may have ↵	friendica	2013-12-25	1	-1/+1
\| \| \| \|	license incompatibilities). Also set maximum size of a directory popup and let it scroll after that in case somebody set their profile keywords to the content of Webster's dictionary.
*	oops	friendica	2013-12-23	1	-1/+1
\|