XMPP Service Operators - 2017-11-11

  1. onepice


  2. onepice

    Bank Transfer Service all country : $500 = $2.000 $1.000 = $4.000 $1.500 = $6.000 $2.000 = $8.000 $2.500 = $10.000 You send me the bank details, you pay 60% of the price of your order, I do the transfer, I send you a screenshot, cash you and you send me the 40% after. I hope to do good business with you. onepice@muenz.net Thank you and have it soon

  3. mike

    Anyone had any experience with Prosody or anything else for a domain aliasing setup? I just realised chinwag.org had become available since I started the project so I grabbed it. I'd like to transition away from the .im domain and I'm trying to come up with a plan that doesn't break hundreds of existing users. :)

  4. SouL

    Congrats for the domain mike :)

  5. mike

    SouL: thanks :) the .org is much more appropriate now I'm doing more than just messaging

  6. Link Mauve

    mike, there is no alias possible, at best you can reply saying the user switched accounts.

  7. Link Mauve

    But my advice would be to keep both of your domains, and only allow new accounts on the new one.

  8. mike

    Link Mauve: yeah that's the plan I'm going for right now, if I can't find a better solution. I kinda want to disallow new registrations with usernames from the old namespace if I do that though

  9. mike

    I guess I could dump all accounts to a massive blacklist

  10. mike

    feels very inelegant

  11. Link Mauve

    If you’re using Prosody, you can just set “allow_registration = false” in the VirtualHost to disallow registration there.

  12. mike

    what I mean is if I have mike@chinwag.im now, I want to allow only registration in chinwag.org domain from now on (that's easy) but also stop anyone from registering mike@chinwag.org

  13. Link Mauve


  14. mike

    so in the future if a domain alias becomes possible I can merge the userbases

  15. mike

    the old domain list will be static, so blacklisting a set of names is possible, but it'll be a huge list

  16. Link Mauve

    As a first step you could create a mike.dat file in the virtual host’s accounts directory, containing an invalid password for everyone.

  17. Link Mauve

    Domain alias is extremely unlikely to ever happen.

  18. mike

    prepopulating the accounts dir is a good idea, actually even cloning the existing one to start with would work, so people would already have access to their "new" alias if they chose to use it

  19. mike

    does ejabberd handle domain aliases? anyone know?

  20. Link Mauve

    It doesn’t, it’s a fundamental protocol “limitation” to consider the bare JID as the identifier for everything.

  21. mike

    hmm yeah thinking it through it would be a pain

  22. mike

    I might just claim the usernames for pre-existing accounts then and let people pick whatever.

  23. Zash

    mike: you could copy all the account files over to the new domain