aboutsummaryrefslogtreecommitdiffstats
path: root/install
Commit message (Collapse)AuthorAgeFilesLines
...
* bookmark permissionsfriendica2014-02-042-1/+11
|
* chat expiration (default 2 hours) - but can be set on a per-chatroom basisfriendica2014-01-302-2/+13
|
* basic chatroom management backendfriendica2014-01-291-1/+1
|
* add client field to chatpresence - which will give us a place to put IP ↵friendica2014-01-282-1/+8
| | | | 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 structuresfriendica2014-01-272-10/+109
|
* move some store thingsfriendica2014-01-211-1/+6
|
* allow menus to have special rolesfriendica2014-01-152-2/+12
|
* only let visitors remove their own files.friendica2014-01-092-1/+12
|
* add store directory write check to install checksfriendica2014-01-081-1/+3
|
* allow objects to have permissionsfriendica2013-12-282-1/+15
|
* db update for directory profiles - and fix broken database.sql from the ↵friendica2013-12-252-14/+29
| | | | sys_perms addition a couple days back
* add account_level, is_foreigner and is_member functions; convert all e2ee ↵friendica2013-12-232-2/+13
| | | | 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 ↵friendica2013-12-222-4/+17
| | | | names. For this round we're getting 'group' and 'desc'. Warning: potentially destabilising as this touches a lot of code.
* Ooops, also update the DBThomas Willingham2013-12-221-0/+8
|
* Some sys chan stuffThomas Willingham2013-12-221-1/+17
|
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-202-2/+13
| | | | | | 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 wellfriendica2013-11-182-11/+8
|
* drop the queue table which we no longer usefriendica2013-11-182-17/+8
|
* DB - allow private messages to expirefriendica2013-11-062-19/+28
|
* INSTALL for dummies - step 1: ensure that we throw an ugly error message in ↵friendica2013-11-051-0/+11
| | | | | | | their face if there's an ugly error when we first try to install. DON'T white screen until after they've got it running.
* Fix missing parenthesis in database.sqlAntoine G2013-11-011-1/+1
| | | This was blocking database creation process
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-302-1/+9
| | | | could be a strong selling point.
* Schema change - add channel_dirdate so we can ping a directory server once a ↵friendica2013-10-272-1/+11
| | | | month which means we can find dead channels - because they won't be pinging the directory server once a month.
* installing sabre is a whole lot more complicated. It also doesn't like ↵friendica2013-10-211-18/+0
| | | | co-existing with other projects in the same web path. This is going to be fun.
* preserve the source owner when creating a delivery fork so that we can ↵friendica2013-10-132-1/+9
| | | | uplink back to them without any ambiguity.
* Add install instructions for cloning WebDAV component (which I think is best ↵friendica2013-10-101-0/+18
| | | | if we make optional). There may be webserver dependencies so let's just call this a plugin of sorts, but different than normal plugins because if it's installed it will be tightly integrated with everything we do. Eventually we may provide a static repository or select a specific sabre-dav version so that we're immune from changes upstream which break stuff we're doing; but for now we'll use the fruux main repository and install using the trunk.
* post signaturesfriendica2013-10-022-2/+9
|
* implement republish permission for use in sourced channelsfriendica2013-09-302-1/+11
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-302-2/+20
| | | | | | | | | 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 unionsfriendica2013-09-262-1/+29
|
* add some text for issue #79friendica2013-09-241-0/+7
|
* add a flag field to xtags so that we can filter tags based on whether or not ↵friendica2013-09-192-2/+11
| | | | 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 ↵friendica2013-09-192-2/+12
| | | | 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 ↵friendica2013-09-182-2/+12
| | | | (directory sync) updates have been processed in some way.
* site sellpage linksfriendica2013-09-172-2/+12
|
* Fixed error in SQL Statementndurchx2013-09-121-1/+1
|
* extends DB in hubloc to maintain hubloc connectivityMichael Meer2013-09-102-1/+10
|
* change primary key on updates tablefriendica2013-09-092-2/+11
|
* public site list (will take a few days to populate, assuming folks have ↵friendica2013-09-052-1/+12
| | | | 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 ↵friendica2013-09-012-3/+10
| | | | 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 recursionfriendica2013-08-312-1/+12
|
* basic structure for premium channel implementationfriendica2013-08-212-1/+13
|
* poll stufffriendica2013-08-212-2/+63
|
* network-wide poll voting structurefriendica2013-08-202-19/+46
|
* email attachments (and fix email photos)friendica2013-08-192-1/+9
|
* we only want to maintain one INSTALL.txt - and it is in the directory ↵friendica2013-08-151-2/+47
| | | | 'install' where it belongs.
* check these in so I can go back and find out why the stylsheet is horkedfriendica2013-08-112-2/+18
|
* basic *account* removal, but the channel removal which it calls still needs ↵friendica2013-08-042-23/+8
| | | | (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 ↵friendica2013-08-012-1/+10
| | | | 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 obscuringfriendica2013-07-312-2/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 06:07:18 +0000