XenForo 2.0 Discussion
- Thread starter XenForo
- Start date
- Status
I thought they were using EmojiOne on XF2.
As for #2, I tend to agree with this. Having custom reactions rather just a like button would be nice. Giving the end user that sort of freedom only enhances additional interaction between users (be it better or for worse between said users). Allowing users to agree, disagree, love, hate, "like", and so forth is something that should be made worthwhile as a default feature in a future version.
Reactions will be via addon, there's another thread where this is mentioned. Several devs apparently working on it.
https://xenforo.com/community/threads/2-0-suggestions.132544/
https://xenforo.com/community/threads/2-0-suggestions.132544/
The custom reaction stuff is great for those who want to use it, but I'm not a fan. The reddit style thumbs up or down makes it easier to tell how popular a thread has been. Trying to do so with custom reaction graphics is far more difficult, and the latter makes it more difficult to potentially sort threads by active popularity.
Personally, I'd love to see the reddit style of thumbs up/thumbs down, or like/dislike, and the ability to display posts based on popularity.
That's a very good idea. However, I suspect most admins would prefer some flexibility over what they use, rather than just have a single default option in XF.
Some might prefer Likes, some might prefer thumbs, some might prefer reactions - some might prefer a mix of all. Choice would be good.
My feeling is that the "reactions" and reddit-style "best answer" functionality should be achieved via addons.
I personally very much like reactions/ratings vs likes. I wouldn't mind that being in the core as an option as I think it's something most would consider a default thing anymore - i.e. most that are used to S.M. would be surprised not to see it or something like it. Post Ratings does the job already functionally, but presentation wise, the hover or long-press pop up is all that is missing. So this one technically is already available, just not exactly the same.
One of my dislikes about Facebook and Reddit is that other posts get buried. This is a + and a -. I absolutely hate FB in this regard. For a large group where a topic gets 200 comments and sub-comments, then I get an alert for a comment to my sub-comment, clicking the alert doesn't always (never does for me) expand the tree to get me to that reply, it takes me to the OP or some other random place. Having to "click here for more/previous comments" and search for the comment, no thanks. Not to mention the disjointed discussion that is created by that structure. It's horrible. Then people answering the question repeatedly when it's already been answered, inevitably followed by "yeah that's been answered already read the comments" and I'm gone...
Reddit is ever so slightly better in this regard where the top replies and comment trees are brought to the surface. But the issue still remains - any "branching" of discussion buries content that might be relevant to someone on a particular subject, resulting in sub-discussions that criss cross over one another, multiple people answering the same question and not seeing each others' answers...
I get wanting the option for it - some might favor it. But not me. Sounds like an addon, but it would be one that would seemingly change the default structure of threads. I can see it being done via an addon, but I would not want to see this being a default method, no way.
I personally very much like reactions/ratings vs likes. I wouldn't mind that being in the core as an option as I think it's something most would consider a default thing anymore - i.e. most that are used to S.M. would be surprised not to see it or something like it. Post Ratings does the job already functionally, but presentation wise, the hover or long-press pop up is all that is missing. So this one technically is already available, just not exactly the same.
One of my dislikes about Facebook and Reddit is that other posts get buried. This is a + and a -. I absolutely hate FB in this regard. For a large group where a topic gets 200 comments and sub-comments, then I get an alert for a comment to my sub-comment, clicking the alert doesn't always (never does for me) expand the tree to get me to that reply, it takes me to the OP or some other random place. Having to "click here for more/previous comments" and search for the comment, no thanks. Not to mention the disjointed discussion that is created by that structure. It's horrible. Then people answering the question repeatedly when it's already been answered, inevitably followed by "yeah that's been answered already read the comments" and I'm gone...
Reddit is ever so slightly better in this regard where the top replies and comment trees are brought to the surface. But the issue still remains - any "branching" of discussion buries content that might be relevant to someone on a particular subject, resulting in sub-discussions that criss cross over one another, multiple people answering the same question and not seeing each others' answers...
I get wanting the option for it - some might favor it. But not me. Sounds like an addon, but it would be one that would seemingly change the default structure of threads. I can see it being done via an addon, but I would not want to see this being a default method, no way.
TPerry
Well-known member
Honestly doubt that would be seen in 2.1.... and possibly not ever. It really depends on how much they want to expand their ecosystem.
I'd MUCH rather see something similar to IPS Pages than a portal or blog.
We've bumped up the minimum requirements for MySQL to 5.5 but not stretched them far enough to use the native JSON support.
That said, we are generally making more use of JSON albeit encoded/decoded in PHP and still stored in BLOBs in MySQL. We'd recommend that, where practicable, developers use JSON for new fields rather than PHP serialization and if it's sane to do so, update existing fields to store JSON. We haven't routinely done that everywhere, but if you can it will be worth doing.
That said, we are generally making more use of JSON albeit encoded/decoded in PHP and still stored in BLOBs in MySQL. We'd recommend that, where practicable, developers use JSON for new fields rather than PHP serialization and if it's sane to do so, update existing fields to store JSON. We haven't routinely done that everywhere, but if you can it will be worth doing.
MariaDB 10.2.0 (2016/2017 release) only just got native JSON support, and MySQL 5.7.8 (2015 release) is requires for JSON support.
Given XF2 still support php 5.4 (2012 release), I wouldn't hold out for the native json support. Most of the time, just being able to store the blob as json is an important 1st step. As JSON imposes unicode encoding rules, which means binary data in your json is now "interesting".
Given XF2 still support php 5.4 (2012 release), I wouldn't hold out for the native json support. Most of the time, just being able to store the blob as json is an important 1st step. As JSON imposes unicode encoding rules, which means binary data in your json is now "interesting".
I noticed there are a couple places where a user's secret_key is pushed into the cache which causes "fun" with JSON. And changing content_type to varbinary can potential mean it will contain invalid-unicode sequences when developers try to interact with it as a string at various levels.
its admin demo update to XF2?
- Status
