aboutsummaryrefslogtreecommitdiffstats
path: root/version.inc
Commit message (Collapse)AuthorAgeFilesLines
* network & home notification fixesfriendica2013-01-111-1/+1
|
* wrong redirection after followfriendica2013-01-091-1/+1
|
* events are still buggered and aren't anywhere close to working, but not ↵friendica2013-01-071-1/+1
| | | | buggered quite as much as before.
* get sliders working againfriendica2013-01-061-1/+1
|
* fix live update on channel pagefriendica2013-01-051-1/+1
|
* rev updatefriendica2013-01-041-1/+1
|
* import the toggle_mobile stuff to shut up some warningsfriendica2013-01-031-1/+1
|
* zome issues registering new hubsfriendica2013-01-021-1/+1
|
* start building social graphfriendica2013-01-011-1/+1
|
* couple of fixes to follow, prepare for default connection permissionsfriendica2012-12-311-1/+1
|
* more logging, some debugging of group membership pagefriendica2012-12-301-1/+1
|
* no hub - well doh, no wonder; we were looking for array['hub'] and it's ↵friendica2012-12-291-1/+1
| | | | actually array['url'].
* bypass replace_macros and use template processor directly for theme includesfriendica2012-12-281-1/+1
|
* This was bloody hard to sort out.... but now it's sorted and we can move ↵friendica2012-12-271-1/+1
| | | | forward again. Put back xtag for efficient keyword searching, use it in conjunction with xprof['keywords'] to avoid a SQL triple join and group_concat (which simply won't scale on a directory server), figured out how best to work timezone corrected birthdays into the protocol. The directory can even provide an age if one was provided to it. Both of these things need some more work, but we have the mechanisms and a plan how to do it right instead of "how the !@#$ are we going to do pull this off?"
* add important profile fields to zot-info if permitted - for directoryfriendica2012-12-261-1/+1
|
* allow toplevel domain redirects for zot-infofriendica2012-12-251-1/+1
|
* add permission controls to "storage" objects such as attachments or other ↵friendica2012-12-221-1/+1
| | | | stored files
* removing dfrn stufffriendica2012-12-201-1/+1
|
* set_baseurl issue, more cleanupfriendica2012-12-191-1/+1
|
* modularise the notification popupsfriendica2012-12-181-1/+1
|
* some cleanup - Thomas we can put the radius/shadow stuff back later for the ↵friendica2012-12-161-1/+1
| | | | hipster kids, it's quite distracting at the moment and makes it hard to get serious work done. Hmmm. Wonder if we could make radius/shadow configurable like colours.... and maybe even screen transparency.... that could be interesting.
* add live page loading and and endless scroll to home (mod_channel)friendica2012-12-161-1/+1
|
* db query looping without bounds if group table wasn't manually updated to ↵friendica2012-12-141-1/+1
| | | | add the 'hash' column.
* admittedly local magic-auth is easy so that's mostly done. Now it gets hard.friendica2012-12-131-1/+1
|
* So what if Red could do more CMS types of things? And you could add ↵friendica2012-12-121-1/+1
| | | | arbitrary web content pages of your own design to your channel resources? Oh wait...
* alternate wysiwyg bbcode editorfriendica2012-12-101-1/+1
|
* revise auto_update system so as not to conflict with pre-existing Friendica ↵friendica2012-12-091-1/+1
| | | | settings
* make permission quick links workfriendica2012-12-081-1/+1
|
* upstream fixes, revision updated, and mail autocomplete was lost after a ↵friendica2012-12-081-1/+1
| | | | recent change I made
* contact photo issuesfriendica2012-12-061-1/+1
|
* y'all got mailfriendica2012-12-051-1/+1
|
* DB: do the mail table again. Mail almost working onsite, still needs to zot ↵friendica2012-12-041-1/+1
| | | | though
* profile viewer in iframe module, todo - magic authfriendica2012-12-031-1/+1
|
* connection notificationsfriendica2012-12-021-1/+1
|
* auto-friending for forums and stuff is almost trivial now. But we will need ↵friendica2012-12-011-1/+1
| | | | a page to set the permissions on the "self" abook record. These will be the default permissions for anybody we wish to connect with.
* Now if you follow somebody it will create an abook entry on the other site ↵friendica2012-11-291-1/+1
| | | | with blocked,ignored, and pending set. No "friend notifications" yet.
* trace through the threaded conversation spaghetti to bring back a sane ↵friendica2012-11-281-1/+1
| | | | looking network page
* got comments going back and forth - we really need local_deliver now since ↵friendica2012-11-271-1/+1
| | | | even local deliveries are going through zot and that isn't necessary or desirable in the long term
* more heavy lifting on delivery - now we can find all the recipients on the ↵friendica2012-11-261-1/+1
| | | | system who have any acceptable permissions for receiving a post. Next we just need to process edits and deletes, and otherwise store the message - yay. Still a lot of work, but we've come a long way baby.
* more but slow progress on deliveries. The b*tch is trying to match permissionsfriendica2012-11-251-1/+1
|
* DATABASE: outq additions, delivery now getting the notify across to the ↵friendica2012-11-191-1/+1
| | | | other side
* Now we are able to get a zot notification packet and the resulting json ↵friendica2012-11-181-1/+1
| | | | 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".
* little stufffriendica2012-11-161-1/+1
|
* version updatefriendica2012-11-161-1/+1
|
* more progress on notifier cleanup and encoding items for transit.friendica2012-11-151-1/+1
|
* starting the big notifier cleanupfriendica2012-11-141-1/+1
|
* sometimes it gets confusing when using two trees with completely different ↵friendica2012-11-131-1/+1
| | | | structures
* one could say we've sort of got zot - at least there are two-way ↵friendica2012-11-121-1/+1
| | | | communications for channel meta info, don't yet know if it's working
* hush-hush ultra top-secret modefriendica2012-11-111-1/+1
|
* starting to get into the hairy parts of zot - identity, location, and ↵friendica2012-11-101-1/+1
| | | | permission synchronisation. After this, messaging should be a piece of cake.