Three of these are work in progress (NickMem is a release).
What I was thinking I could do with these is wrap them up into a program similar to MessengerDiscovery. This is motivated by a few things:
1. Not wanting to have too many software projects to maintain.
2. Have to think of less names
3. NickMem suffers from buggy Messenger API implentation for MSNMsg.
4. \slap would be a more intuitive command than /xslap I think (the \ is to prevent conflicts with Plus's / commands and MD's ! commands).
5. Much more stuff would be possible (don't worry, I won't duplicate features ).

Of course, this would mean having quite a complex mix of stuff, best represented in a picture:

I'd also have to deal with users that don't have MD or Plus, though users with them may benefit from more features.

Don't worry: I won't be abandining the Plus plugin architecture. I don't think I'll be incorporating my sound plugins into such a proxy (the full download would be massive), and other stuff may be easier as a plugin.

I could also add an API of my own, though that could encourage people to make plugins that require Plus, MD and my own project.

I can see this becoming a big task already... and I'd need to learn how to make an API in VB, including events.

Anyway, after reading all of that, what do you guys think?

And yes, the image was done with Visual Paradigm for UML.

Update: Slapper will not be included in Project RP (working title). Slapper is easier as a plugin.

I like the idea, but you're right it will be a big job

good luck to do it but i think it would be too much... 2 proxies = 5 times the number of connections on your pc (2 (MD) + 2 (yours) + 1 (MSN)). i wouldn't use for simply that reason. plus, if you have a bug, you can't debug it.

All the proxy connections are localhost, so that shouldn't be a problem. Also, if there is a bug, I can debug it: how do you think MD is debugged? And plugins for that matter.

yes of course, but i mean... if someone who uses your app and MD for the first time where is he going to report the error? how cna he debug? it's always possible, but very confusing for a regular user.

btw, localhost connections are annoying too =/
example:

quote:

---

Originally posted by netstat
TCP    localhost:1025      localhost:1254      ESTABLISHED
TCP    localhost:1025      localhost:1471      ESTABLISHED
TCP    localhost:1025      localhost:2130      ESTABLISHED
TCP    localhost:1254      localhost:1025      ESTABLISHED
TCP    localhost:1260      localhost:1025      CLOSE_WAIT
TCP    localhost:1471      localhost:1025      ESTABLISHED
TCP    localhost:2120      localhost:1025      CLOSE_WAIT
TCP    localhost:2130      localhost:1025      ESTABLISHED
TCP    localhost:2254      localhost:2255      ESTABLISHED
TCP    localhost:2255      localhost:2254      ESTABLISHED

---

Any error messages would be titled appropriately, and contact details provided.
And what the hell are you running with all those localhosts?

I like the idea and wish you best of luck with it. Like Dempsey said it is going to be a big job. But good luck with it !