Adding a remote script is working great! You mite be interested in adding the site to GreaseMonkey wiki: http://wiki.greasespot.net/User_Script_Hosting
Is there a forum/discussion/blog available were bugs/features can be posted/discussed? This threat is getting long :) On Monday, September 8, 2014 7:59:49 PM UTC+2, Eric Gardner wrote: > > I was actually in the process of making a new tab for adding a remote > script. But time got cut short and I had to get to class. I have about 2 > hours before my databases lecture, so I will see if I can get it working > before then. > > I saw GitHub has a few of its own little modifications that shouldn't be > hard to implement. But first, I want to add some CSS to make the markdown > look a little better (highlight links, better looking bullets, etc...). > > And as for the look of the site, it's just gonna be a gradual change over > time. None of my friends are computer-savvy, and the guy next to me in my > computer class needed help installing java -_- legitimate help....I don't > think most of these kids could spell CSS, let alone use it. So i'm pretty > much on my own to pull inspiration from anywhere I can find it. > > The biggest and most important project I have ahead of me is the > visualization of collected data. Right now I have it restricted to bar > graphs. But i'm working on letting users map specific data points to > various types of graphs. > > - Pie graph of new vs returning users > - Area chart of page load time vs script execution time > - average errors per session per day > - etc... > > But getting all that client -> server interaction to work together safely > is gonna be a pain in the ass. Then converting raw sanitized data into the > requested chart type is gonna be an ungodly amount of js. > > On Monday, September 8, 2014 6:52:13 AM UTC-5, jerone wrote: >> >> Just seen the new sync features and thats great. Syncing the readme file >> is even more then the alternative sites have, great job. >> >> All my readme's are coming from Github, which supports GFM >> <https://help.github.com/articles/github-flavored-markdown>(GitHub >> Flavored Markdown). You mite want to check that out... >> >> I uploaded a few scripts to test all features in the coming days. >> >> As for the design, I'm precisely like you, no skills in design, all >> server-side and client-side programming. I hope you find someone who can >> help you with that. >> >> As for new features; I found adding a new script by uploading a static >> file with the new sync feature a bit redundant. A suggestion beside adding >> a static file, is to add scripts by filling in all sync variables. >> >> >> On Mon, Sep 8, 2014 at 11:20 AM, Eric Gardner <[email protected]> wrote: >> >>> Ok well I just finished adding markdown support, and script/readme >>> syncing options :) . I haven't set up the cron job to do a nightly, >>> site-wide sync; but it works none-the-less. >>> >>> The sync option works for more than just Git projects too. It simply >>> pulls and validates anything the URLs point to. So for your project, just >>> link it to the raw file in your master branch. >>> >>> As for the site's look, i'm not a graphic designer :P I'm pretty >>> terrible at making things look good. >>> >>> I'm more worried about security than anything else, and that's where >>> most of my time goes. Server-side, 70% of the code is sanitizing user >>> inputs and making sure there is no unauthorized SQL commands being >>> executed. Hell, the script search php file is probably 95% sanitation and >>> 5% execution. >>> >>> If you have any other feature requests, let me know. >>> >>> >>> On Thursday, September 4, 2014 12:13:24 PM UTC-5, jerone wrote: >>>> >>>> Got success uploading an userscript today. You can view the result >>>> here: http://myuserjs.org/script/jerone/Github_Pull_Request_From >>>> >>>> Besides the feature request about syncing scripts (from Github), I even >>>> more want to suggest to add the feature Markdown for descriptions. >>>> All other sites (OpenUserJS & GreasyFork & MonkeyGuts) support Markdown >>>> for their script descriptions. >>>> It would save me a lot of time converting my readme.md files from >>>> Github to html or text. >>>> >>>> It's clear that you still have some work to do. Obviously the design is >>>> an issue (standard jQuery UI style :) ), but more it requires some >>>> features >>>> for userscript authors. You want to attract them, otherwise the site stays >>>> empty. >>>> I do like the API features. It's the most feature complete there is >>>> compared to the other sites. >>>> >>>> I hope that you keep up the great work and even make it open source so >>>> other can help out. >>>> >>>> On Tuesday, September 2, 2014 4:35:53 PM UTC+2, Eric Gardner wrote: >>>>> >>>>> Ok I just added every possible mime type for javascript files. Even >>>>> ones that i'm pretty sure dont exist. >>>>> >>>>> On Tuesday, September 2, 2014 7:22:55 AM UTC-5, jerone wrote: >>>>>> >>>>>> The error returns now: Invalid File Type: text/x-js >>>>>> >>>>>> On Tuesday, September 2, 2014 1:32:29 AM UTC+2, Eric Gardner wrote: >>>>>>> >>>>>>> Ok I think I fixed it. It was a file type I had never seen before: >>>>>>> "text/x-userscript-meta". If it's a different type, it should tell you >>>>>>> now. >>>>>>> >>>>>>> On Sunday, August 31, 2014 12:14:00 PM UTC-5, jerone wrote: >>>>>>>> >>>>>>>> Am still getting an error saying "Invalid File Type" when trying >>>>>>>> to upload an userscript. I tried multiple scripts. Even tried from >>>>>>>> github directly: https://github.com/jerone/ >>>>>>>> UserScripts/raw/master/Github_Pull_Request_From/Github_Pull_ >>>>>>>> Request_From.user.js >>>>>>>> >>>>>>>> >>>>>>>> On Wednesday, August 27, 2014 10:10:30 AM UTC+2, Eric Gardner wrote: >>>>>>>>> >>>>>>>>> Yea like I said, I was/am migrating servers. I was using an Amazon >>>>>>>>> EC2 solution because of its fast setup/low hourly price. But in the >>>>>>>>> end, it >>>>>>>>> still wsn't worth it so I upgraded to a quad core vps. but the damn >>>>>>>>> thing >>>>>>>>> came with cpanel, which is a pain in the ass when you aren't >>>>>>>>> reselling. >>>>>>>>> >>>>>>>>> The site is back up for the time being, but I still have to move >>>>>>>>> my SSL certificate to the new server. Additionally, I had a bunch of >>>>>>>>> scripts that would sync with a private git repo to keep everything >>>>>>>>> neat and >>>>>>>>> versioned. I also had a script that would do nightly backups. So I >>>>>>>>> still >>>>>>>>> have a a lot of stuff move/rewrite for the new filesystem. >>>>>>>>> >>>>>>>>> But for the time being, I have Diff Eq and Cal III homework to do >>>>>>>>> before I go to work. So it may be a while before I finish the move, >>>>>>>>> and get >>>>>>>>> back to developing. >>>>>>>>> >>>>>>>>> On Tuesday, August 26, 2014 4:06:55 PM UTC-5, jerone wrote: >>>>>>>>>> >>>>>>>>>> Site down?! >>>>>>>>>> >>>>>>>>>> On Tuesday, August 26, 2014 9:45:54 AM UTC+2, Eric Gardner wrote: >>>>>>>>>>> >>>>>>>>>>> Oh well that's weird. It could be an encoding error. I am having >>>>>>>>>>> problems with my current server, and I am in the progress of >>>>>>>>>>> migrating. I >>>>>>>>>>> went ahead and added a few mime types and updated the validator. >>>>>>>>>>> But I >>>>>>>>>>> really don't know why it would do that. >>>>>>>>>>> >>>>>>>>>>> I actually started writing that in, but I have prioritized core >>>>>>>>>>> functionality. As soon as I have worked out all the bugs, I will >>>>>>>>>>> finish the >>>>>>>>>>> github syncing scripts. >>>>>>>>>>> >>>>>>>>>>> I do not rewrite any meta information (currently). I feel it is >>>>>>>>>>> the author's responsibility/right to maintain meta information. I >>>>>>>>>>> actually >>>>>>>>>>> hate how GreasyFork doesn't let you opt-out of rewriting. I >>>>>>>>>>> understand that >>>>>>>>>>> a script could have an update url that updates the code to >>>>>>>>>>> something >>>>>>>>>>> harmful without the user's knowledge. However, there are easier >>>>>>>>>>> ways to >>>>>>>>>>> screw with your users. You could just write your own interpreter >>>>>>>>>>> and do an >>>>>>>>>>> xmlHttpRequest for malicious code to execute. >>>>>>>>>>> >>>>>>>>>>> Eventually I will update my validator to check for known >>>>>>>>>>> malicious resources and remove them if necessary. But I feel that's >>>>>>>>>>> where a >>>>>>>>>>> host site's power should end. >>>>>>>>>>> >>>>>>>>>>> On Monday, August 25, 2014 5:20:16 AM UTC-5, jerone wrote: >>>>>>>>>>>> >>>>>>>>>>>> Trying to upload a script, am getting error saying "Invalid >>>>>>>>>>>> File Type" while it's a .user.js file. >>>>>>>>>>>> >>>>>>>>>>>> One feature I really miss and other sites (OpenUserJS & >>>>>>>>>>>> GreasyFork) do have implemented is importing and syncing with >>>>>>>>>>>> Github. I >>>>>>>>>>>> don't want to upload my scripts every time to all sites when I >>>>>>>>>>>> make an >>>>>>>>>>>> update on Github. >>>>>>>>>>>> >>>>>>>>>>>> Question: do you rewrite the scripts like GreasyFork does? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sunday, August 24, 2014 8:30:44 AM UTC+2, Eric Gardner wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Oh lol well I didn't think anyone would try to sign up so I >>>>>>>>>>>>> never enabled new user creation. I went ahead and manually >>>>>>>>>>>>> confirmed your >>>>>>>>>>>>> account, Give it a try and let me know how you like it >>>>>>>>>>>>> >>>>>>>>>>>>> On Saturday, August 23, 2014 12:12:19 PM UTC-5, jerone wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Just wanted to try it, but I'm not getting my confirmation >>>>>>>>>>>>>> mail. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Saturday, August 23, 2014 11:21:39 AM UTC+2, Eric Gardner >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So I have been developing a new userscript hosting site and >>>>>>>>>>>>>>> I'm looking for some feedback from other developers. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *http://myuserjs.org <http://myuserjs.org>* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What makes it unique: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - Host resources with your script (text, css, other >>>>>>>>>>>>>>> scripts) >>>>>>>>>>>>>>> - Collect advanced statistics on script behavior (page >>>>>>>>>>>>>>> load time, script execution time, errors, etc...) >>>>>>>>>>>>>>> - Intuitive API for manual update checking, and >>>>>>>>>>>>>>> statistic reporting (and does not require privileged >>>>>>>>>>>>>>> functions like >>>>>>>>>>>>>>> xmlHttpRequest) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The site is not ready to be used by script authors around >>>>>>>>>>>>>>> the world, but I would love it if some of y'all could look >>>>>>>>>>>>>>> around the site >>>>>>>>>>>>>>> and give me some suggestions. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The following is still being worked on: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - Site API is still being worked on. >>>>>>>>>>>>>>> - Statistic viewing engine still needs ability to >>>>>>>>>>>>>>> isolate specific arguments (ex: only view stats submitted >>>>>>>>>>>>>>> when error=1) >>>>>>>>>>>>>>> - Comment section for scripts is still under construction >>>>>>>>>>>>>>> - The overall look and feel needs an update (I'm a >>>>>>>>>>>>>>> programmer, not a graphic designer) >>>>>>>>>>>>>>> - General efficiency updates needed >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> But for the most part, all the core functions of the site >>>>>>>>>>>>>>> work. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Look at this example script >>>>>>>>>>>>>>> <http://myuserjs.org/script/jgjake2/Cracked.com_Enhancer>. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks for your time, >>>>>>>>>>>>>>> Eric >>>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "greasemonkey-users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/greasemonkey-users/rJCzdoRFUY0/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/greasemonkey-users. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
