Jump to content

Matt A. Tobin

  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Matt A. Tobin

  1. Ignorance. Must be nice to be too stupid to even realize how dumb you are. Additionally, I will do as I see fit.
  2. Are you people THIS STUPID. ShellService is in the PROCESS of being REPLACED. It is NOT FULLY FUNCTIONAL YET. I am the one who removed the old shellservice and am in the process of replacing it and adapting the frontend code to work with the NEW ShellService. There is not a god damned thing you can do about it until the work has been completed. It is broken. Until I fix it, it will REMAIN broken. f***in morons, I swear. There is a reason Borealis isn't a released product yet, this is one of them. When will you people learn that all this praise for roytam1 or fedor2 is completely misplaced. They are incapable of doing more than extremely minor modifications of the code and ALL THE s*** you thank them for was done by my self and others who aren't trying to scam you into using old and insecure operating systems and half-assed and corrupt incarnations of code on top of them.
  3. I already told you guys that the shellservice is in the process of being replaced and the front-end needs to be conformed to it. I am working on it. Though this is what you get for using unfinished, unreleased code. Especially when you don't know anything about what you are building and ******** out to unsuspecting users. I am also not happy with these terrible renames happening here that are just plays on my hard considered brands. Are none of you original enough to think of your own names? Well the answer is yes because after HOW MANY YEARS none of you have decided on a proper name for these corruptions of our work. Bnavigator Browser.. really? Why not call it Bnavigator Explorer Browser Client for the Web. Ridiculous.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. @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.
  13. 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.
  14. Why in gods name would I want to do that dude?
  15. I really like that naming scheme except for "RFox" part. BTW, still not dead ;)
  16. 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
  17. The MOZ_APP_NAME would stay the same of course, that's fine. Same with application.ini who's values failing the existence of some alt build configuration dictate the location of the application profile. SAME goes with NSIS generated installer/uninstaller and helper.exe used by both NSIS and shellservice as well as shellservice its self. Unfortunately, this is set in stone and it is too unreasonable to change that stuff now. Maybe two years ago but not now as it would cause too much end-user trouble. Not to mention it would be annoying from a patch porting point of view. So that's fine. So just need to change the name in branding configure.sh, graphical assets, and l10n. Pretty simple once you have the name and logo. Now, I can sort of dig the circles with lines in em and perhaps do something with the concept though they MAY be a bit abstract. However, I hope that modified Firefox logo is not a serious contender because clearly that would not acceptable to Mozilla as it would get the the drones all fired up in a second and of course blame us not you for it. The general problem with the New Moon branding was it was intended to be basically like the Firefox Nightly branding and while yes it pulled double duty as generic branding anyone could use, it is still intrinsically linked to us and despite the feeling from some people here that there is and never has been any confusion, I can tell you there is.. People know that Pale Moon is the older Firefox-based browser with the interface of Firefox 4-28 and that builds are sometimes called New Moon. But with the divergent path of what continues to happen to support Windows XP what is produced isn't even going to be an unbranded Pale Moon for Windows XP as most people see it. Perhaps that is how you see it but as time goes on the differences mount. Let me put it to you another way, what if we had just kept the original non-trademarked Nightly branding for Pale Moon, both Basilisk's, and you also created your other half-dozen Firefox-based builds.. ALL called Nightly because that is what was there. How could you tell them apart then? Is it reasonable to put the burden on us to explain to people that the Windows XP builds you produce aren't the same as someone else producing Windows 7 unbranded builds or unbranded mac builds which also use the New Moon branding because mac isn't at the official level yet. The un-knowledgeable user who doesn't read more than maybe two sentences of a paragraph would assume New Moon == Pale Moon because they look the same and because despite being referred to as generic branding the name is too unique and intrinsically linked with us. This is the result of a decision made six years ago and it turns out to not have been a very good one on our part. Let me also say again, that this happens in the wild. THERE IS CONFUSION because I have specifically gone out of my way to berate and s*** on the confused user because it p***ed me the hell off and does every single time. Should I? No. Do I? Yeah. Should I continue to do so.. Well despite what one may conclude I actually don't know.. I do know that I don't really want to be angry about it anymore. I do know that over the past two years it has accomplished nothing. I also know that roytam1 took the unofficial branding as-is but hasn't been bothered to change it for whatever reason that may be. I do know I am a half-way decent designer and have the technical knowledge to implement it easily for roytam1 to slot into place. I also figured I had nothing to loose by str8 up offering to do it instead of expecting someone else to. A very common situation I find my self in a lot these days actually. I talked, bitched, complained, pleaded with and begged SeaMonkey for almost 10 years to not turn out the way it turned out and it accomplished nothing but in the Pale Moon project and beyond to the Unified XUL Platform, lots of things have gotten done through hard a** work via cooperation, coordination, and discussion and maybe that should be applied elsewhere. Especially to places that have historically annoyed the hell out of me for whatever real or imagined reason. After all, it is a process to better ones self and help make world at large better too. Can't have it all in a day but you can't have anything if you don't try. So I am trying (and yes there is likely a joke in there). Besides, I can't keep calling the paradigm "new" if it is the same old crap, eh?
  18. I'm sorry LoneCrusader but by invoking the bsd-wip github issue you have lost any credibility among any of us over here. I will take responsibility for what I said on the Pale Moon forums and in my channel. I even take responsibility for what I said in that github issue BUT in THAT CASE I was in the right and there is no denying that from any rational mind. Could a word order change have not evoked such a disproportionate response from them? I have asked that question many times since then. I want to say yes but I know those bsd people are batshit insane. They don't respect intellectual property OR software licenses wanting to treat everything as public domain and/or theirs without cause and are at a level of fanaticism that outshines even my self. So no. You don't get to cite that as a valid argument against me to promote blatant anti-Tobinism. I won't stand for it. You're done. Fortunately for the rest of everyone who isn't you, I am not going to let that impact the start of what I hope will be better times. So to everyone else, nothing has been impacted by LoneCrusader's machinations. I stand by what I have offered and suggested.
  19. Thank you. Well I have been awake for about 24 hours. I'll do some thinking and conceptualizing when I next awake.. You guys let me know what you decide on the direction of the all this.
  20. You have to think though.. Names need to be able to be visually represented.. With what I suggest it not only follows a theme for those in the know.. It also stands on its own as basic concepts that can be represented easily. Whistler, a mountain Freestyle, some sort of abstracty glyph Neptune, Blue planet or perhaps the God Neptune's trident and Lonestar some sort of star likely akin to a sherrif's badge.. put it on an envelope or stamp or something.. That is what I was thinking.
  21. The largest the logo icon would be anywhere is 256x256 which is the second largest size. At that resolution it doesn't look as chunky as it does in the 512 size. But let's see..
  22. Edited previous post with a wordmark.. Notice the font THE REAL QUESTION IS.. can I do half as good three more times AND will people LIKE it.. hmmmmmm.
  23. Well.. I created an icon for the Whistler Branding which would be used on Pale Moon... It is based on a public domain photo of the actual whistler mountain.

  • Create New...