Wedge

I don't want to make you lose your repository if it's at all possible :(

There are a couple of ways to avoid that

1) Let it be a pure plugin (and we're back to square one), now that I think about it, a special "core plugin" isn't a great idea. It's either fully plugin or fully core
2) This is something I'm taking from how Android gets built, that thing is distributed to atleast 50 repositories. Make a separate script that'll automatically fetch external dependencies and compile them into the core build. Notifications and other plugins being some of them. It shouldn't be too hard, I can perhaps do it if everyone's on board the idea. It probably does complicate things a bit (perhaps unnecessarily).

I can't honestly think of a way that'll work for all of us. Perhaps leave it as a plugin for now and re-visit this when Wedge's beta or something? Then we'd have more input, especially from active users

It could be done like, when we are installing wedge, it could ask if we want to install those plugins, something like they do with toolbars when we install some programs :niark:

I'd assume from that smiley that you jest, but if that were implemented (!!), the installer would also ask for FTP access.

Nah, the smiley is related to the whole 'here's a free program, would you like to install some crappy toolbar while you're installing this free program?' Like various of the torrent software trying to foist Ask toolbars on you.

If I were seriously going down that road, I'd actually write a system to prepare builds on the server and let people build packages together if it's optional.

But something like notifications is not something I'd want as an 'optional' feature if that makes sense.

What if the notification core goes into Wedge's core completely and most of the notifiers remain as plugins?

That seems logical, though it might confuse people as to why they aren't getting notifications. At the very least I think replies to posts would need to be a core feature if the notification innards becomes core.

No, some essential ones will also be in the core along with notifications and the subscriptions core. But the less important ones remains as plugins.

Oh, that definitely works for me!

Okay, so how do they go in? I guess the two core plugins will be directly into the sources. Will the essential notifiers also be embedded into sources?

Ideally, they'd go in directly to the sources, including loadSource calls etc. as necessary with direct function calls as and when appropriate.

Well, the problem with stripping the existing subscription stuff is that you're still going to get people who want email notifications of crap >_<

XenForo does the same thing, though in XF's case they call it 'Watched Threads' so while you'd get an 'alert' (or notification) of a reply, if you've watched the thread, you'll also get an email about it.

I left a message with Nao about what to do regarding repo access, but I get the feeling a diff might be easier.