From the last full Q&A round:
Status: Setting up a Devcon community in Status would act a bit like a Discord server where we would have a set of “channels” per topic. Another nice feature can be Devcon designed stickers to be used in the channels - we can launch a competition for this in partnership with SuperRare and ArtProject Decentralised in the run up to the event also…
EF team: Devcon stickers could be cool! We also have a number of Devcon assets designed in-house.
EF team: We (or Status or the community) creates channels for the conference of different topics, but try to avoid channel overload. Not sure we need a channel for every room…maybe. But things like: social/fiesta, food, local tips, etc -
Status: Creating channels within the community is exactly how communities will run. You can choose what channels to create and name them. Sponsors could also create their own channels and create engagement pieces within the channels - anything from token incentivised actions to collecting questions for their talks or encouraging attendees to join their meetups/events/get exclusive swag etc. The community feature will be available on both mobile and desktop.
EF team: Re announcement management. From our end, we want to be able to make announcements easily, ideally by posting to one platform only. For attendees though, we want to make sure that announcement is seen regardless of the attendee uses. Initially I think this could look something like posting to Twitter and having it replicate on Status, the website ‘Updates’ page, and possibly TG/Discord.
Status: Bridging Status with TG and Discord can both be done - a few communities do this as do the Status team for certain channels. Ideally, we would use the decentralised tool to disseminate them so encourage posting them in Status for a one to many dynamic as the message can then be shared in Status with bridges to Discord and Telegram. Twitter messages may need to be shared as links in the channels but will investigate if any alternative is possible.
Status team will provide any tech support needed and provide a degree of moderation. The Devcon team will monitor channels for Devcon-specific questions and problems!
Status will be responsible for printing handouts given at check-in - Perhaps a small, thin, ideally eco-friendly paper slip that maybe A) on one side describes Status communication app and QR code link to devcon channel, and B) on the other side explains the keycard they are receiving and how to use it.
EF Team: Will app be user friendly enough for general public? If not, maybe in best interest for both status and Devcon to postpone using app until it is ready for primetime.
Status: Yes! One of the things we already support is deeplinks to specific chats so an invite to the Devcon Community will lead users to download the app and take them directly to the community. Users who already have the app can easily navigate to the community or search for it to join. The whole idea with communities is to create spaces that enable easy communication, in line with chat apps in use today, but also coupled with a wallet and browser for easy access to the ecosystem all in one.