d5d6158973
ok heads up - potentially destabilising change. I've tried to sort out all the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table).
...
The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes.
What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected.
With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
2014-11-04 17:11:02 -08:00
fdb9b9d52e
Merge https://github.com/friendica/red into pending_merge
2014-11-03 14:51:28 -08:00
a6d8c3193a
various UI issues related to having an enormous number of entries in the posted_date selector including years/months that had no posts
2014-11-03 14:49:03 -08:00
9984ff37e5
innodb issue
2014-11-03 15:33:59 +00:00
ac858f4bd4
provide example import script
2014-11-03 01:06:02 -08:00
0e4f318b71
php warnings
2014-11-02 19:22:18 -08:00
285d6f61e4
I'm going to try again with the conversation request packets. I've looked this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't *think* this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
2014-11-02 15:28:20 -08:00
4274a2d06c
add some more safety checks before turning the conversation request messages back on
2014-11-02 00:06:52 -07:00
50c16c394f
check that we have valid data
2014-11-01 01:52:27 -07:00
1eacea4037
Merge https://github.com/friendica/red into pending_merge
2014-11-01 00:36:58 -07:00
a659ac8952
disable request message response until we work through this
2014-11-01 00:36:21 -07:00
f294962290
Merge pull request #671 from pafcu/master
...
Fix problem with default birth date
2014-10-31 16:49:48 +01:00
d9f2944565
Fix problem with default birth date
2014-10-31 16:09:48 +01:00
1cb45c30e9
document request packets a bit more
2014-10-31 06:24:14 -07:00
5637d07138
flag notify packets that are sent in response to a message_id request and prevent them from recursing
2014-10-31 04:59:30 -07:00
28a35261db
What this checkin does is catch the case where a comment arrived and there's a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.
2014-10-30 19:15:03 -07:00
fc704d1f2f
if someone does not have permission to chat do not show the chatrooms tab
2014-10-29 14:29:38 +01:00
d9c5823593
the default permissions for new connections when using a custom role is inadequate. Until we can make it configurable start off with something like a public social role. We're typically taking the person straight to the connection editor so they can change it before any privacy damage is done
2014-10-28 19:29:37 -07:00
9cc76cb33d
several unrelated things - auto_follow wasn't working for new accounts, error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
2014-10-27 19:23:40 -07:00
583b445bc0
add "repository" permissions role and make sure we have a sane "accept" default for the custom role.
2014-10-27 16:19:30 -07:00
be8a01618e
turn down the preview logging. Haven't needed that level of detail recently.
2014-10-26 21:56:56 -07:00
655c3e1b47
put privacy role selector in settings page. Change visibility of various permissions items accordingly.
2014-10-26 19:32:12 -07:00
ce8a891682
doh - this needs to be markdown, not bbcode
2014-10-24 14:18:02 -07:00
cf05266b15
should probably check the body since the title is only going to be rarely set.
2014-10-24 14:04:32 -07:00
1845ddc4c3
don't decrypt the message body more than once.
2014-10-24 04:17:48 -07:00
34781433c1
I'm speechless. This is just reckless. Set a context flag in text using a context trigger character which is likely to be present in that text already. Without escaping any previous instances of that character. Grrr.
2014-10-23 21:20:12 -07:00
f524fb1f20
generalise the output format of xchan_fetch so it matches the input format
2014-10-23 19:41:42 -07:00
241bb3b940
API: xchan get/create
2014-10-23 19:33:47 -07:00
1c4bbbd13e
diaspora walltowall comment signature, force update.
2014-10-23 16:08:29 -07:00
f29c5a35f1
Provide comment box for PERMS_AUTHED items. Presently only commentable from owners wall.
2014-10-23 21:50:53 +01:00
0ebfee8f87
wrong permalink on remote events
2014-10-23 01:36:40 -07:00
58c692e389
improved wall-to-wall detection for comments so we can handle Diaspora signing and wall-to-wall attribution correctly.
...
Do it at the point of submission. This also fixes a potential bug in yesterday's wall-to-wall permission setting,
if it was a local comment to a remote post.
2014-10-22 20:39:49 -07:00
902b5c52e5
backtrack on attribution for wall-to-wall comments - triggered too often and unnecessarily.
2014-10-22 18:14:21 -07:00
d7cb5c0436
you've gotta' be on your toes to catch this bug... though it's been here for about 2 1/2 years and even survived a rewrite. Symptoms are that the archive widget only lists one month (the month when you first posted), and only if your first post was written between the 28th and 31st of whatever month that was.
2014-10-22 16:41:06 -07:00
d5edd89dd2
when removing a channel, check to see if there are any valid hublocs remaining before marking the xchan deleted.
...
Issue #657
2014-10-21 17:07:25 -07:00
35be89ad66
Merge https://github.com/friendica/red into pending_merge
2014-10-21 16:34:14 -07:00
ed7712cfbf
private forum issues
2014-10-21 16:33:35 -07:00
1fb2de6d55
Typo
2014-10-21 17:27:13 +01:00
e8a7fb3d01
strip out the Diaspora quoted reshare markers
2014-10-20 21:15:29 -07:00
bcb4356fe0
Merge pull request #652 from beardy-unixer/master
...
Prevent multiple simultaneous pollers.
2014-10-21 13:27:33 +11:00
577d84b883
bb2diaspora wallwall comment - match both bits (ITEM_WALL|ITEM_ORIGIN)
2014-10-20 19:06:02 -07:00
cb15c73dae
move all theme initialisation to one place - just after calling module_init. Revert if there are serious issues, but please note the issues in as much detail as possible so we can work through them.
2014-10-20 16:47:58 -07:00
58431f948e
Screwed up merge - put Mike's stuff back.
2014-10-20 19:35:02 +01:00
48b2eafcaa
Prevent more than one instance of the poller running at a time.
2014-10-20 19:31:47 +01:00
c909b8be06
don't auto-archive connections we can't poll.
2014-10-19 21:41:38 -07:00
8227be0ab0
show true author of wall-to-wall comments to Diaspora viewers just like we did for wall-to-wall posts.
2014-10-19 19:20:25 -07:00
fd492386bf
Tried this once before but had to revert. Basically prevent a comment from being relayed more than once - as it's a huge drain on resources. But last time I tried this, wall-to-wall comments stopped getting relayed. This checkin should do the right thing in both conditions.
2014-10-19 17:31:10 -07:00
bae3029c63
merge madness
2014-10-19 16:12:05 -07:00
e8be2ff8da
wall-e random signature failures
2014-10-19 15:54:20 -07:00
7bbe700f3f
mark signature forgeries
2014-10-16 16:19:19 -07:00
friendica
Thomas Willingham
jeroenpraat
Stefan Parviainen
marijus