yamamushi

@NQ-Nyzaltar   I hope you guys are having a great holiday vacation, I know you won't get this until you get back but wanted to post before I forget about it.
 
I've been doing a bunch of research in the community area tonight and I keep having to agree to the privacy and terms pop up on every single page I visit in there even though I click both checkboxes every time.  Not sure if you were aware of it, but it's really hard to do any research in there right now. 
 

I think that it would be prudent to enable 2FA across our Dual Universe profiles. Our game, forum and community site profiles are all one single sign-on, and considering the NDA under effect, I think it would be very useful to allow for 2FA for those of us who want it. 
 
We don't get notifications for when we login to our accounts from new locations, so there's not really an easy way for us to tell if someone has our creds and logs into our accounts. 
 
Please give us 2FA on the websites at least
 
Invision Community even supports it as of January 2017 - https://invisioncommunity.com/news/product-updates/new-two-factor-authentication-r995/ 
 
To clarify: This isn't about forcing people to use 2FA, this is about enabling it so that those of us who want to can use it for extra security on our accounts. It's 2018 and the realities of security on the internet these days necessitate that we have the option. 
 
 

I understand that during the post-Kickstarter phase when Founders packs were available, it was generally discouraged to be gifting backer packages, however now that we have Supporter packs it would be really cool to have a built-in feature to allow us to gift pledges to others.
 
I don't want to go into explaining how I've been able to gift pledges to others, suffice to say that it does not involve sharing passwords. However it's not really a straightforward way, and it's somewhat risky to be doing I'll admit. I did ask NQ whether or not what I was doing was allowed, and they did say that it was. So I know I'm not breaking any rules by doing it.
 
So I suppose I will consider this thread as a request for us to have the native ability to gift pledges directly from the pledge page.
 
 

Hi Yamamushi,
 
Yes the "gift a pack" feature is planned.
However, it won't be before several months (probably not before Alpha 2, at the earliest): there is a significant development time to allocate for such feature and it's not - unfortunately - in the top priorities right now.
 
Best Regards,
Nyzaltar.

I understand that during the post-Kickstarter phase when Founders packs were available, it was generally discouraged to be gifting backer packages, however now that we have Supporter packs it would be really cool to have a built-in feature to allow us to gift pledges to others.
 
I don't want to go into explaining how I've been able to gift pledges to others, suffice to say that it does not involve sharing passwords. However it's not really a straightforward way, and it's somewhat risky to be doing I'll admit. I did ask NQ whether or not what I was doing was allowed, and they did say that it was. So I know I'm not breaking any rules by doing it.
 
So I suppose I will consider this thread as a request for us to have the native ability to gift pledges directly from the pledge page.
 
 

I understand that during the post-Kickstarter phase when Founders packs were available, it was generally discouraged to be gifting backer packages, however now that we have Supporter packs it would be really cool to have a built-in feature to allow us to gift pledges to others.
 
I don't want to go into explaining how I've been able to gift pledges to others, suffice to say that it does not involve sharing passwords. However it's not really a straightforward way, and it's somewhat risky to be doing I'll admit. I did ask NQ whether or not what I was doing was allowed, and they did say that it was. So I know I'm not breaking any rules by doing it.
 
So I suppose I will consider this thread as a request for us to have the native ability to gift pledges directly from the pledge page.
 
 

I believe it will be possible to code on lua some basic navigation for hovers, so they go only on particular route. But that is not 'a train', just a workaround. 

Oh yay another subscription thread - said no one ever

@yamamushi
 
Oh man, what a mess. Surely a setback for him, but he seems popular enough to be able to get out of that okay, or even stronger. I must say he also seems more authentic with his community ties than others, and I think he just has a natural talent for some of those things. This event makes us and me even want to resort to him more. Not that I could complain prior.
 
E: Thanks for the heads-up by the way. Appreciated a lot, I would likely only have noticed way later.

@Warden - Your spokesperson was banned from Fiverr, we should help this guy out : 
 
 

I know that "predefined sounds" is on the "Considered" list on Trello: https://trello.com/c/HVdTjEsH/51-functional-scriptable-speakers-able-to-play-predefined-sounds 
 
While I think that would be cool, I think it would be cooler if we had access to a synth sound module through LUA to build and sequence our own custom sounds. 
 
Writing sound synthesis by hand isn't unheard of in LUA, for example:
 
 
 
And even more, here are some tracks composed entirely with LUA:
https://soundcloud.com/luehi/systemf  https://soundcloud.com/luehi/luacid1 https://soundcloud.com/luehi/early https://soundcloud.com/luehi/selfkitchen https://soundcloud.com/luehi/luaessay5 https://soundcloud.com/luehi/movk  
I think that giving us the flexibility to define our own sounds with such an approach would be incredibly more valuable than choosing from a list of predefined sounds. 
 
In case anyone is wondering, yes I am suggesting this because I want a night club in DU.

Contact support @ https://support.dualthegame.com/hc/en-us , and include all of the relevant info. They usually respond within a day. If you pledged with gold or higher, I don't doubt they'll have you ready for the next testing session. 

All I can say is
 

Well, the way I see it is that it's NQ's game, NQ's data, NQ's website, and now it's NQ's discord.   They should feel free to purchase/use any scripts that they find that they feel necessary to complete their job.  If they find one that is free to serve some time-saving purpose, even better.  More money for the game itself.  They do not need permission to use - or to even tell us - what programming is behind everything they use. 
 
For all we know this very site and forum itself could be using open source that someone else coded.  They might even be DU players too. (gasp!)  IMO it's just not smart to re-create the wheel.  Almost everything I use for my own stuff and for my clients is open source. Lord only knows who originally coded it.  But if something is wrong with it, the community will darn well make it known, asap.  It's the proprietary stuff that no one ever gets to see that should cause issues (if you must have issues, that is.)

I honestly don't know what else I could add to this topic other than making a video describing every line of the bot source code one by one. 
 
The same thing is being rehashed over and over here to the point where it's obvious that no matter what is said that people are going to take issue with it. 
 
If you want links to the source code:
https://github.com/yamamushi/du-discordbot/blob/master/backer.go https://github.com/yamamushi/du-discordbot/blob/master/backer_handler.go  
Otherwise, I really don't know what else I can add to this conversation. I've explained what the bot does, I've explained why it does it, there's simply nothing else for me to cover.
 
The bot has been working for quite some time now and nobody ever complained about it before, it's just that when Discord went official that people started to freak out about it. It's not new, it's been serving its purpose quite well. 
 
If you want NQ to run it, I'm not sure what that is going to change because the bot is still going to be running off the same source code that I wrote, you're effectively just asking NQ to put even more work on themselves to support it going forward. I'm sure they'd do it if enough people demanded it, but it really wouldn't change much other than who owns the server the container runs on.
 
As for the bot collecting data, the bot doesn't collect anything that you don't specifically allow it to. It's not going to go automatically scraping user accounts on Discord, you have to manually run the command and specifically give it your forum profile to gather your backer status (or pre-alpha status if you have that disabled). Anyone can disable their backer public status, the only thing the bot needs to verify is whether or not you have pre-alpha status, which is something that you can't edit on your profile. 
 
The bot isn't just scraping the forums randomly looking for accounts to link up, you have to manually run the verification process, by which you implicitly agree to the collection of your publicly available information in the first place. 
 

I honestly don't know what else I could add to this topic other than making a video describing every line of the bot source code one by one. 
 
The same thing is being rehashed over and over here to the point where it's obvious that no matter what is said that people are going to take issue with it. 
 
If you want links to the source code:
https://github.com/yamamushi/du-discordbot/blob/master/backer.go https://github.com/yamamushi/du-discordbot/blob/master/backer_handler.go  
Otherwise, I really don't know what else I can add to this conversation. I've explained what the bot does, I've explained why it does it, there's simply nothing else for me to cover.
 
The bot has been working for quite some time now and nobody ever complained about it before, it's just that when Discord went official that people started to freak out about it. It's not new, it's been serving its purpose quite well. 
 
If you want NQ to run it, I'm not sure what that is going to change because the bot is still going to be running off the same source code that I wrote, you're effectively just asking NQ to put even more work on themselves to support it going forward. I'm sure they'd do it if enough people demanded it, but it really wouldn't change much other than who owns the server the container runs on.
 
As for the bot collecting data, the bot doesn't collect anything that you don't specifically allow it to. It's not going to go automatically scraping user accounts on Discord, you have to manually run the command and specifically give it your forum profile to gather your backer status (or pre-alpha status if you have that disabled). Anyone can disable their backer public status, the only thing the bot needs to verify is whether or not you have pre-alpha status, which is something that you can't edit on your profile. 
 
The bot isn't just scraping the forums randomly looking for accounts to link up, you have to manually run the verification process, by which you implicitly agree to the collection of your publicly available information in the first place. 
 

When the NDA drops then there won't really be a need to authenticate with it, we can close (or archive) the NDA channels, and nobody will have to use it. If they want to get backer roles for cosmetic purposes they'll still be able to, but otherwise, there won't be a need for it. 
 
As for the data, that is going to stay in the database because it is what ties backer roles to users. Even for non-NDA purposes, such as Iron / Bronze / etc backers, or supporter pack purchasers (non-patron packs), or ATV.
 
The database stores:
Discord user ID Forum profile link Backer Status (Gold/Silver/Ruby/Whatever) ATV member (true or false) Pre-Alpha Access (true or false) Validated successfully (true or false) - This is used to track whether a user has completed the auth process or not  
When the API becomes available, I will adjust the database to only keep the data that the API provides.
 
You don't need to have your backer status made public to be validated either, as many didn't want to have to do that. The forums will show if you have pre-alpha access without needing to display what backer level you have. There are many in Discord who have access to the NDA channels while also hiding their backer level.
 
The bot is used for other things besides authentication, it provides utilities for NDA members which will be useful after the NDA drops too, it provides a live forum feed, a Reddit feed, a news feed for Dual Universe content (Youtube, Twitter, DevBlog, etc), it provides reactions (the Nyzaltar, Nomad, JC, etc reactions), it provides a server status utility and many more things. 
 
I don't see a good reason to remove it completely when the NDA drops. 

I also want to clarify, there are things that I (and others on the Discord Staff) have been aware of in the works that we simply aren't allowed to discuss. Ie, for the Discord server, the process of making it official and handing it over to NQ has been going on for several months, it wasn't an overnight quick decision by any means. We couldn't publicly announce that for many reasons.
 
There were many questions about the auth process that I could have answered with "Well an NQ API is in the works" to assuage some fears, but I didn't want to break any confidentiality by saying that either.
 
I know there are many in the community that really don't like me at all, but I would not be where I am in my career if I made a habit of collecting data for illicit purposes or breaking confidentiality agreements openly. I'm never going to win those people over, but at least I can try to be as transparent as possible to the rest of you to show that I'm acting in good faith here with my contributions. 

I also want to clarify, there are things that I (and others on the Discord Staff) have been aware of in the works that we simply aren't allowed to discuss. Ie, for the Discord server, the process of making it official and handing it over to NQ has been going on for several months, it wasn't an overnight quick decision by any means. We couldn't publicly announce that for many reasons.
 
There were many questions about the auth process that I could have answered with "Well an NQ API is in the works" to assuage some fears, but I didn't want to break any confidentiality by saying that either.
 
I know there are many in the community that really don't like me at all, but I would not be where I am in my career if I made a habit of collecting data for illicit purposes or breaking confidentiality agreements openly. I'm never going to win those people over, but at least I can try to be as transparent as possible to the rest of you to show that I'm acting in good faith here with my contributions. 

When the NDA drops then there won't really be a need to authenticate with it, we can close (or archive) the NDA channels, and nobody will have to use it. If they want to get backer roles for cosmetic purposes they'll still be able to, but otherwise, there won't be a need for it. 
 
As for the data, that is going to stay in the database because it is what ties backer roles to users. Even for non-NDA purposes, such as Iron / Bronze / etc backers, or supporter pack purchasers (non-patron packs), or ATV.
 
The database stores:
Discord user ID Forum profile link Backer Status (Gold/Silver/Ruby/Whatever) ATV member (true or false) Pre-Alpha Access (true or false) Validated successfully (true or false) - This is used to track whether a user has completed the auth process or not  
When the API becomes available, I will adjust the database to only keep the data that the API provides.
 
You don't need to have your backer status made public to be validated either, as many didn't want to have to do that. The forums will show if you have pre-alpha access without needing to display what backer level you have. There are many in Discord who have access to the NDA channels while also hiding their backer level.
 
The bot is used for other things besides authentication, it provides utilities for NDA members which will be useful after the NDA drops too, it provides a live forum feed, a Reddit feed, a news feed for Dual Universe content (Youtube, Twitter, DevBlog, etc), it provides reactions (the Nyzaltar, Nomad, JC, etc reactions), it provides a server status utility and many more things. 
 
I don't see a good reason to remove it completely when the NDA drops. 

Hey, I wouldnt sat I dont like you at all, I only despise 98% of you. 
 
Glad to see while I've been gone you've still been here as dedicated as always. Great work. 
Now if only people use discord for actual voice coms. I get lonely talking to myself. 

I also want to clarify, there are things that I (and others on the Discord Staff) have been aware of in the works that we simply aren't allowed to discuss. Ie, for the Discord server, the process of making it official and handing it over to NQ has been going on for several months, it wasn't an overnight quick decision by any means. We couldn't publicly announce that for many reasons.
 
There were many questions about the auth process that I could have answered with "Well an NQ API is in the works" to assuage some fears, but I didn't want to break any confidentiality by saying that either.
 
I know there are many in the community that really don't like me at all, but I would not be where I am in my career if I made a habit of collecting data for illicit purposes or breaking confidentiality agreements openly. I'm never going to win those people over, but at least I can try to be as transparent as possible to the rest of you to show that I'm acting in good faith here with my contributions. 

We both know there is stuff in the NDA forums that will be fine to use and show once NDA lifts, Lua code for one. A blanket statement like the quote would not hold for that reason. But we're getting off track here.
 
 
Makes two of us but I'm pretty sure that is because some can't separate opinion and well meant but sometimes maybe harsh words from personal feelings. I would not know why I would not like you at all as you seem to be an enthusiast who gives way to much of his time away doing what you hopefully enjoy doing..  For what it's worth I certainly appreciate the work you put into all this as I know the amount of work and time it takes all too well. My feelings on the bot(s) do not in any way relate to any of that.

@NQ-Nomad / @NQ-Nyzaltar: this bug is comming back.
 
@Ryzrix: I suggest you to log a ticket on https://support.dualthegame.com too, you may have a quicker answer.
 
~ Merwyn