Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Matt A. Tobin

Member
  • Content Count

    72
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    6

Matt A. Tobin last won the day on January 11

Matt A. Tobin had the most liked content!

Community Reputation

115 Excellent

About Matt A. Tobin

Profile Information

  • OS
    Windows 7 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

1,411 profile views
  1. BTW @roytam1 If you are wondering about shellservice and nsis installer code.. I am gonna be upgrading that modifying the copy from Pale Moon which was modified from Basilisk when Pale Moon was ported to UXP from Tycho. The technical reason is simply this.. The Suite Shellservice is not very appropriate for a standalone web client and over the years the SeaMonkey people have mangled it pretty badly and pieces of it are ancient. Basically getting a fresh copy that is geared to JUST a web client will improve matters greatly. The reason the nsis scripting is involved is because on Windows the shellservice needs to issue commands to an external application that can elevate and Mozilla shared routines in nsis scripting to produce the helper.exe which serves during install as well as commands issued by shellservice. Those two items need to be consistent. But yeah until I get it replaced you can just revert that. However, I suggest once it is replaced and verified you should switch it to that for best results.
  2. My applications aren't Pale Moon. Binary Outcast is NOT Moonchild Productions. There is a difference. It is very unfortunate that I can't trust anyone to look out for my intellectual property. However, more positively the situation is being rectified. Though, I personally believe the situation should not have had to happen at all. All it takes is some work in order to avoid such things. Something I been saying for three years. Thank you for making the changes.. But I wish you had done so when you first started producing builds of software some of which has not been released yet. Especially, when you knew it early on with my projects. Also, may want to change the searchplugins in communicator/searchplugins the ones that are Pale Moon specific. I have permission to use those, you do not. Also kill, other-licenses/7zstub/binoc in your configuration it will use the 7z sfx from platform though you should really reshack your own based on the platform one. In any case, I'll be watching and I will hold you to the letter of the MPL and defend my rights.
  3. And this is why the complete source for covered code must be disclosed. He distributing or otherwise using my copyrighted material and trademarks without permission and I won't have it. I suspected as much but until I forced him to actually comply with the license it was unknown. SO not only was it non-compliance it was incomplete discloser of changes and he was using my materials in order to produce inferior products to damage me.
  4. Unstable branding, the copyright artwork in my extensions, namely ABPrime, ANYTHING that goes to binaryoutcast.com and you may NOT use my proprietary api key for geolocation. In fact, that entire preferences file that you stole is NOT covered under the MPL. It is completely proprietary as well as the UAOverrides preferences file. Additionally, confvars, application.ini? That is unacceptable. You may not call it Borealis. And you may not piggyback on BinOC services and resources.. I thought you understood this crap by now.
  5. Would you mind removing any copyright material from your repo? And while this is not a requirement, you may want to purge unrelated code such as my extensions.
  6. I didn't say a word about the fake Pale Moon build. I said the navigator and mail clients. Since he has the source code up for the fake Pale Moon builds he is in compliance there. Every person who modifies covered code then distributes an executable form must satisfy the MPL. One cannot just give a zip file of patch files of the applications and call it done.. He must disclose the entirety of covered source code INCLUDING making the platform code along with it available by some reasonable means. The easiest way would be to clone binoc-central (preferably with a different repo name) and use a platform submodule so that when cloned you get the complete source code. He could also put up a tarball but that takes a lot of space over time. However, as a code contributor of covered code I am informing him of the breach of the open source license under which his executable forms derived from. If he wishes not to comply then the MPL is terminated. Of course he can take me out of the equation by purging all contributions I have made to covered code but other contributors to covered code will subsequently pursue this matter.
  7. The builds of the navigator and mail client are illegal according to the Mozilla Public License because the source code is not properly disclosed only patch files. I already explained that.
  8. BTW Have I mentioned you are in direct violation of the Mozilla Public License 2.0? Specifically, Section 3.2 which states: The MPL defines Source Code Form as follows: Your patch files are not sufficient. You MUST provide the full source code with your modifications. All software created with covered code I have worked on is currently in breach of the license.
  9. @VistaLover You shouldn't freak out so much whenever you see a commit from me.. As https://bugzilla.mozilla.org/show_bug.cgi?id=711679 CLEARLY states.. versioncheck-bg.amo was done for server load reasons as part of their infra.. I believe stuff at versioncheck-bg.amo was cached results whereas versioncheck.amo are always live results. So assuming you are using AMO for Phoenix 52 and WebExtensions it won't make a bit of functional difference. I did check the history of this before I made the change. These days, I don't even think they are tangibly separate since Mozilla does TONS of cdn s*** now across the board which was NOT the case back in 2012. Least according to their add-ons server software code. However, checking his commits it goes to my infra so it really IS redundant in the current configuration. And as for your preference setting.. This situation is not something that can ALLOW you to have TWO different update servers. update.background.url was used when the Add-ons Manager does an autocheck on a schedule and update.url is used when there is a direct request like checking manually or whenever a new version is detected. Having them go to two different servers creates a LOT of discontinuity.
  10. Even Mozilla now admits in retrospect that a bunch of their initial speed hacks for quantum were dangerous which is why they were reverted over the next 3-5 versions. We told you this as they were doing it, of course.
  11. Why in gods name would I want to do that dude?
  12. I really like that naming scheme except for "RFox" part. BTW, still not dead ;)
  13. I wanted to update you all that I have not abandoned you all. It's just Christmas night I got VERY VERY ill with a hospital-grade superflu I acquired a few days prior while visiting my father when he was in the hospital. I had a very high 104.5F fever that night and was pretty debilitated for days after as such serious flus tend to do. It has taken me a while to get better and get back into the swing of things. I see that discussion has been fairly constructive given the scope of a public forum so I am positive about the prospects of eventually resolving this. Indeed, I am very positive about the prospects the 2020s are offering in general. Oh I know it will be a lot of hard work and struggle but anything worthwhile always is. ANYWAY, this post is technically irrelevant so I will leave it there. Just wanted to let you know that I haven't just abandoned this or all of you as may or may not have been suggested. I look forward to constructive monitoring
×
×
  • Create New...