{"action":"created","issue":{"url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/332","labels_url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/332/labels{/name}","comments_url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/332/comments","events_url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/332/events","html_url":"https://github.com/SocialEngine/phpv4-issues/issues/332","id":120256034,"number":332,"title":"What do you most want to see improved in Social Engine?","user":{"login":"Elshara","id":12810222,"avatar_url":"https://avatars.githubusercontent.com/u/12810222?v=3","gravatar_id":"","url":"https://api.github.com/users/Elshara","html_url":"https://github.com/Elshara","followers_url":"https://api.github.com/users/Elshara/followers","following_url":"https://api.github.com/users/Elshara/following{/other_user}","gists_url":"https://api.github.com/users/Elshara/gists{/gist_id}","starred_url":"https://api.github.com/users/Elshara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Elshara/subscriptions","organizations_url":"https://api.github.com/users/Elshara/orgs","repos_url":"https://api.github.com/users/Elshara/repos","events_url":"https://api.github.com/users/Elshara/events{/privacy}","received_events_url":"https://api.github.com/users/Elshara/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-12-03T19:55:58Z","updated_at":"2015-12-18T01:36:51Z","closed_at":null,"body":"We've all contributed a great deal to the improvement of the product so far. Some more popular feedback topics have left us wondering, not if it will be implemented, not even when it will be released, but rather how will it improve our websites when it is built.\r\nI can relate to how you're feeling. Getting our hands on new release code just isn't possible with the current way social engine updates its code. So, I thought I'd start a thread on what improvements you're looking forward using in a practical sense, regardless of whether it is built, upcoming or on the drawing board.\r\nHere are my top 10.\r\n1. A better caching system. Simply put, static content should be cached where as dynamic content should be instant. Better control over what gets cached may be the best thing we have to a practical performance improvement.\r\n2. PHP7 support. If wordpress can update to responsive themes and already has php7 implemented, social engine with its meriad of fans and supporters should consider redefining the code structure to work with modern browsers and modern improvements the internet has to offer. If the developers don't consider this a priority, perhaps wordpress importing of social engine plugins as a free tool would change their minds. We invest readily into this company, we should receive code improvements, not bug fixes.\r\n3. A better way to handle post editing. Simply put, tags need to go. They are rarely used on social engine, and if they are to be used, I think repositioning the word tag to be \"subjects covered\" or \"related phrases\" would be a much better fit. In fact, replacing the tag system with a box to have perhaps a post signature or prologue and adding a summary box to go along with it, would definitely be up to industry standard. In addition, replacing all flash requirements with html5 will ensure services like plupload or uploadify bring us to the forefront of modern developments. Did you know: Facebook has already moved on from php and mysql years ago? If we want to have a modern social network, we ought to look into that as well. It starts with how people post things, if it is modern, others will enjoy it better and it would run faster as well.\r\n4. A better way to handle plugins. We should have most of our page content as post html and compress all other files to one css and javascript file. This way it can reference what it needs and we can do away with things like mootools and other various plugin core requirements so the website looks and loads much faster, cleaner with out all the extension requirements. I mean really, having to not even be able to put spaces in your username, then having to look at profiles that can't even determine one name space from another, isn't that 1990's technology? Doing away with content id and database reliance for a start will definitely take us in the right direction, and one step forward to a modern website. If wordpress can do it, so can we.\r\n5. A better media player. Currently, you have to upload media to three basic modules. Photos, music and videos, rely on separate codecs to handle their respective files. What if however, they could be merged into one, have mass upload enabled through html5, had browsers implement the ability to play the files and download its metadata through javascript and be able to divide files not by file type extension, but by audio, video and photos. A media gallery plugin would take care of this.\r\n6. Merge the polls and forums plugin into one. Polls should be apart of a forum discussion, this is how most modern forum boards do things. Simply put, all user engagement should run through one idea, and having polls as a forum attachment would make this a lot easier.\r\n7. Merge the groups and events plugin into one. All events do is create something that will only be used once. Who needs an event profile when it won't be used regularly. With events as an attachment to a group post, all of this would become clear since you'd have to join a group anyway for it to become an event. Events are bigger groups, so it makes sense to make it apart of the groups plugin.\r\n8. Merge the marketplace plugin into an attachment. This way paid access could be implemented by both admins and members. Allowing someone to advertise in one central location, isn't convenient for people anymore because if they don't find what they're looking for, they'll simply not use it. Having the marketplace as an attachment allows the selling and receiving of an item to be tightly integrated into what ever page someone is currently viewing. It works both as a paid access system with multiple contributors, and also as a sails management system since its primary focus is to get money from one person to another. Attaching it to all forms of posts with its current set up would make this a lot easier for people to sell something and still get their point across if they are interested.\r\n9. Make activity feeds a thing of the past. To be replaced with post specific comments by paragraph. Soundcloud is already doing this and it makes sense because while you're reading a post, you can in parallel, read its relative comments based on the current position. This can be achieved using slideshow and ajax based technology. Activity feeds record items separately, however apart from the main and profile activity feed, if it was integrated into posts where members can click and drag sections to like, dislike and comment on, it would be a lot easier for people to engage and notify each other of where things make the most sense and why they are important.\r\n10. Update email templates on a global scale. I am so tired of social engine using unprofessional emails to communicate activity with the recipients. I mean really, who puts social network administration at the bottom of all emails without a subject line. The default email address is \"email@domain.com\" why bother filling in that field, why not make it apart of the set up process for installing social engine. While I'm at it, just use the site name and language templates to automatically be supported in all email templates in future so members get a lot more detailed emails for their activity. Why should we have to hand code emails just so that it matches what can be supported or is already. And please, include an unsubscribe link at the bottom of all emails and update all email phrases to a global signature.\r\nFeel free to add to this list or make your own out of it. I thought this would help make a clear and concise point across."},"comment":{"url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/comments/165633346","html_url":"https://github.com/SocialEngine/phpv4-issues/issues/332#issuecomment-165633346","issue_url":"https://api.github.com/repos/SocialEngine/phpv4-issues/issues/332","id":165633346,"user":{"login":"Elshara","id":12810222,"avatar_url":"https://avatars.githubusercontent.com/u/12810222?v=3","gravatar_id":"","url":"https://api.github.com/users/Elshara","html_url":"https://github.com/Elshara","followers_url":"https://api.github.com/users/Elshara/followers","following_url":"https://api.github.com/users/Elshara/following{/other_user}","gists_url":"https://api.github.com/users/Elshara/gists{/gist_id}","starred_url":"https://api.github.com/users/Elshara/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Elshara/subscriptions","organizations_url":"https://api.github.com/users/Elshara/orgs","repos_url":"https://api.github.com/users/Elshara/repos","events_url":"https://api.github.com/users/Elshara/events{/privacy}","received_events_url":"https://api.github.com/users/Elshara/received_events","type":"User","site_admin":false},"created_at":"2015-12-18T01:36:51Z","updated_at":"2015-12-18T01:36:51Z","body":"Perhaps it may be possible for all mysql queries to be cached as in\ncache or update current database tables via cron job then if a new one\nhas to be created, it can simply do so in real time independent of\nwhat else has been cached so whatever is cached will be served first\nso long as it is static, which can be everything in and of itself.\n\nOn 17/12/2015, Elshara <sourceminded@gmail.com> wrote:\n> I third you.\n>\n> On 17/12/2015, meetgerry <notifications@github.com> wrote:\n>> I second Eugene!\n>>\n>> ---\n>> Reply to this email directly or view it on GitHub:\n>> https://github.com/SocialEngine/phpv4-issues/issues/332#issuecomment-165630103\n>\n"}}