codingisfun2831t commented

(Migrated from github.com)

I know we arent in release yet but it'll still be good for public beta.

I believe @PPPDUD should be the owner of the extension publishing, but both Firefox and Chrome allow permission sharing so other people can publish version or change info, but I think just PPPDUD is fine.
Note that for now we'll mostly just do Firefox (sorry PPPDUD) but its for a good reason. Chrome requires 5 USD to publish extensions (its a one time fee). Thus we probably shouldn't do that until we're confident, and can find someone who will pay it.

Firefox should be easy however.

I know we arent in release yet but it'll still be good for public beta. I believe @PPPDUD should be the owner of the extension publishing, but both Firefox and Chrome allow permission sharing so other people can publish version or change info, but I think just PPPDUD is fine. Note that for now we'll mostly just do Firefox (sorry PPPDUD) but its for a good reason. Chrome requires 5 USD to publish extensions (its a one time fee). Thus we probably shouldn't do that until we're confident, and can find someone who will pay it. Firefox should be easy however.

PPPDUD commented

2026-06-12 10:28:26 -05:00

(Migrated from github.com)

I don't want to publish on Chrome for the foreseeable future because fees aside, they have strict extension policies that don't always lean in our favor as developers. I would be happy to publish on Microsoft Edge though, because they will let almost anything on their store and they don't charge any fees.

As for Firefox, wouldn't we be supporting a monopoly? Their sideloading model is designed to force extension developers to publish on their store (or at the very least register an account with Mozilla). As an extension developer, I would like to take a stand against these unfair practices by refusing to submit Sparkle.

I don't want to publish on Chrome for the foreseeable future because fees aside, they have strict extension policies that don't always lean in our favor as developers. I would be happy to publish on Microsoft Edge though, because they will let almost anything on their store and they don't charge any fees. As for Firefox, wouldn't we be supporting a monopoly? Their sideloading model is designed to force extension developers to publish on their store (or at the very least register an account with Mozilla). As an extension developer, I would like to take a stand against these unfair practices by refusing to submit Sparkle.

codingisfun2831t commented

2026-06-12 12:31:47 -05:00

(Migrated from github.com)

Yeah for Chrome I agree with you, as we should be able to easily publish on edge.
But for Firefox.. I get it. I'm not exactly a fan of it either, but making the users life harder having to jump through hoops to keep it installed? Not really worth the trouble as I do use Firefox as my main browser and would like to use Sparkle constantly without a bunch of hoops.

Yeah for Chrome I agree with you, as we should be able to easily publish on edge. But for Firefox.. I get it. I'm not exactly a fan of it either, but making the users life harder having to jump through hoops to keep it installed? Not really worth the trouble as I do use Firefox as my main browser and would like to use Sparkle constantly without a bunch of hoops.

PPPDUD commented

2026-06-12 12:56:08 -05:00

(Migrated from github.com)

Yeah for Chrome I agree with you, as we should be able to easily publish on edge. But for Firefox.. I get it. I'm not exactly a fan of it either, but making the users life harder having to jump through hoops to keep it installed? Not really worth the trouble as I do use Firefox as my main browser and would like to use Sparkle constantly without a bunch of hoops.

If Mozilla sees that users are getting annoyed by having to sideload everything each time they open Firefox, then change will happen because Chromium is already eating away at their userbase and they don't need any more users fleeing their software. If we let Mozilla win, then we're becoming part of the problem.

Therefore, I argue that we should not submit Sparkle to their store.

Edit: Also, users on Jameson can already use Sparkle without an extension.

> Yeah for Chrome I agree with you, as we should be able to easily publish on edge. But for Firefox.. I get it. I'm not exactly a fan of it either, but making the users life harder having to jump through hoops to keep it installed? Not really worth the trouble as I do use Firefox as my main browser and would like to use Sparkle constantly without a bunch of hoops. If Mozilla sees that users are getting annoyed by having to sideload everything each time they open Firefox, then change will happen because Chromium is already eating away at their userbase and they don't need any more users fleeing their software. If we let Mozilla win, then we're becoming part of the problem. Therefore, I argue that we should not submit Sparkle to their store. Edit: Also, users on Jameson can already use Sparkle without an extension.

codingisfun2831t commented

2026-06-12 15:03:31 -05:00

(Migrated from github.com)

Sure fine just wait until people just don't use us because they don't want to (understandly) switch browsers or go to a different path just for a extension

codingisfun2831t commented

2026-06-25 17:19:25 -05:00

(Migrated from github.com)

Based upon the #79 survey, most (non joke) answers want it on Chrome (eventually...), Edge, and Firefox (!) so would we please be able to work on that now?

PPPDUD commented

2026-06-25 17:23:15 -05:00

(Migrated from github.com)

Based upon the #79 survey, most (non joke) answers want it on Chrome (eventually...), Edge, and Firefox (!) so would we please be able to work on that now?

*sigh*...

I suppose that we can look into publishing on Edge soon. I don't wish to publish on either Chrome or Firefox for the time being.

> Based upon the [#79](https://github.com/sparkle-devs/sparkle/issues/79) survey, most (non joke) answers want it on Chrome (eventually...), Edge, and Firefox (!) so would we please be able to work on that now? \*sigh*... I suppose that we can look into publishing on Edge soon. I don't wish to publish on either Chrome or Firefox for the time being.

codingisfun2831t commented

2026-06-25 17:28:38 -05:00

(Migrated from github.com)

Sure, fine. Guess I have to use a random Microsoft product, but apparently Microsoft Edge, the browser that's force installed on every modern Windows computer, is better than Firefox. I guess one is less "corrupt" to you and it's, somehow, Edge.

PPPDUD commented

2026-06-25 17:40:39 -05:00

(Migrated from github.com)

Sure, fine. Guess I have to use a random Microsoft product, but apparently Microsoft Edge, the browser that's force installed on every modern Windows computer, is better than Firefox. I guess one is less "corrupt" to you and it's, somehow, Edge.

No. I don't like Microsoft Edge at all, but it's the only one I can find that's well-known, has zero fees, and doesn't engage in behaviors that actively harm new extension developers. If you can find another store that meets these criteria, let me know and I'll consider it.

> Sure, fine. Guess I have to use a random Microsoft product, but apparently Microsoft Edge, the browser that's force installed on every modern Windows computer, is better than Firefox. I guess one is less "corrupt" to you and it's, somehow, Edge. No. I don't like Microsoft Edge at all, but it's the only one I can find that's well-known, has zero fees, and doesn't engage in behaviors that actively harm new extension developers. If you can find another store that meets these criteria, let me know and I'll consider it.

codingisfun2831t commented

2026-06-27 14:01:47 -05:00

(Migrated from github.com)

@codingisfun2831t who are you talkking to?

I was replying to @PPPDUD but their comments got deleted?

> @codingisfun2831t who are you talkking to? I was replying to @PPPDUD but their comments got deleted?

e016 commented

2026-06-28 16:19:05 -05:00

(Migrated from github.com)

@codingisfun2831t who are you talkking to?

I was replying to @PPPDUD but their comments got deleted?

@sparkle-devs/developers IMPORTANT!!!! It seems like @PPPDUD's account has been marked as spammy. Remember when I was marked spammy twice? My account was unavailable for everyone and I had to contact support to get my account back.

> > [@codingisfun2831t](https://github.com/codingisfun2831t) who are you talkking to? > > I was replying to [@PPPDUD](https://github.com/PPPDUD) but their comments got deleted? @sparkle-devs/developers IMPORTANT!!!! It seems like @PPPDUD's account has been **marked as spammy**. Remember when I was marked spammy twice? My account was unavailable for everyone and I had to contact support to get my account back.

supervoidcoder commented

2026-06-28 16:51:33 -05:00

(Migrated from github.com)

github-suspension.html

# @e016 @codingisfun2831t https://mojavesoft.net/newblog/_site/github/2026/06/28/github-suspension.html

supervoidcoder commented

2026-06-28 16:51:46 -05:00

(Migrated from github.com)

just makiing sure you guys read it. i hope he can get unbanned

codingisfun2831t commented

2026-06-28 17:32:44 -05:00

(Migrated from github.com)

i dont wanna manage it

Bubgamer07 commented

2026-07-10 13:36:42 -05:00

(Migrated from github.com)

dead chat

codingisfun2831t commented

2026-07-18 13:54:24 -05:00

(Migrated from github.com)

@sparkle-devs/developers
https://mojavesoft.net/newblog/_site/github/forgejo/2026/07/04/updates-on-forgejo.html

Update: Just as an FYI: the version of Sparkle at my instance has a bunch of changes that don’t exist on the GitHub version; therefore, I would like to request that the Sparkle developers cease making new commits until further notice.

Last week, I wrote about my suspension from GitHub and mentioned an upcoming Forgejo instance.
I am happy to announce that the server is almost ready for public use!
Here’s everything that you’ll need to know once I’ve gotten the instance online. (Note that this information is subject to change at any time.)

We probably shouldn't create any more feature in the mean time! (before that Forgejo thing is up)

@sparkle-devs/developers https://mojavesoft.net/newblog/_site/github/forgejo/2026/07/04/updates-on-forgejo.html > > Update: Just as an FYI: the version of Sparkle at my instance has a bunch of changes that don’t exist on the GitHub version; therefore, I would like to request that the Sparkle developers cease making new commits until further notice. > Last week, I wrote about my suspension from GitHub and mentioned an upcoming Forgejo instance. > I am happy to announce that the server is almost ready for public use! > Here’s everything that you’ll need to know once I’ve gotten the instance online. (Note that this information is subject to change at any time.) We probably shouldn't create any more feature in the mean time! (before that Forgejo thing is up)

supervoidcoder commented

2026-07-28 09:07:33 -05:00

(Migrated from github.com)

Wow @pppdud did they ever tell you what you did "wrong"?

Rows
Columns

Eventual publishing #76

@e016 @codingisfun2831t https://mojavesoft.net/newblog/_site/github/2026/06/28/github-suspension.html