Research on context and retention

This is very interesting. I want to know if the tool is open source. Where can I see the detailed report of TogetherCrew on the op chain?

The tool is open-source (TogetherCrew Ā· GitHub). However, the report on OP has not been made public (still early-stage research).

We have some standard metrics computed in our dashboard, and you can request access to them from their community lead (we’re not the admin).

Thank you, I’ll go take a look

I’m definitely voting in favor of this one!
TogetherCrew’s solid history with other DAOs and the fact that experienced researchers are on board, it just makes the whole thing even better.
@danielo consider sharing regular updates on your progress so the community stays informed!

1 Like

will do. I’m also hoping we can soon share a bit of the early findings with Optimism. So that could happen even before the Arbitrum ones. But TBC

1 Like

I have to say, I really love this proposal! It aligns with the field I’m currently dedicated to, although my work is not as systematic or well-structured.I’ve only been supporting some new startups within my area of interest.

This proposal aims to help new users entering the Arbitrum ecosystem to understand everything about Arbitrum better and faster. In fact, this not only holds significance for Arbitrum but also for Ethereum and all L2s. Education is always a field that requires long-term investment in any organically growing ecosystem. Moreover, I noticed that this proposal doesn’t require budget, as the team has already funded by other sources.

So, i fully support this proposal. And if there’s any help needed from me or ANDAO in the future, welcome to DM me.

1 Like

I’m not sure if it’s fare to bundle together Discourse, and Discord data, all in the same bucket of publicly accessible data. They are different things.

Discourse data is indeed public, this post I’m writing right now, is public data, in the sense that it can be accessed and indexed without any restrictions, through this link.

Messages on open Discord channels are not public data, in the sense that they can’t be accessed or indexed without a Discord account that is on the Arbitrum Discord server. For example, only Discord users that have accepted Discord’s Privacy Policy and Terms of Service, can see the contents of this message I just sent in the Arbitrum Discord server.

So, I agree with using the Discourse data for this, but not with the Discord data.

Also, I think this proposal should be much more specific of what it is actually asking the DAO.

I believe that this proposal is asking the DAO to consent that the Arbitrum Foundation would give API access to this Discourse data, and also to install this TogetherCrew discord bot, on the Arbitrum Discord server, so that TogetherCrew can read all messages, threads and message reactions in every open channel in that Discord server.

Is this assessment correct @danielo ?

2 Likes

Hey, danielo! I love this proposal, but I’m very concerned about security issues because the Discord of Arbitrum and many other projects have been hacked, causing great harm. You mentioned that the bot requires very low permissions and has done actual security testing. Do you have a detailed security report? Can it be disclosed in this proposal? Thank you!

1 Like

I really appreciate the open-source nature of this proposal and the fact that all the data being analyzed is already public, so there are no privacy concerns. Plus, the fact that they’re not even asking for any budget makes this an easy decision.

I’m voting ā€˜FOR’ this proposal on Snapshot for the reasons already outline above.

1 Like

We support initiatives that improve community access to governance information. This proposal’s focus on analyzing public data to enhance member retention and provide easier access to historical discussions could significantly reduce barriers to participation in Arbitrum’s governance.

1 Like

Voting for.
Identifying patterns in discussion could be quite interesting, even tho I wouldn’t personally want a big focus of the DAO, in future, being on this topic, cause it risks to skew convos too much.
As it is, in favour because also this initiative won’t bear any cost.

1 Like

We support this proposal as it offers valuable insights into community retention and health without requiring any additional funding or compromising privacy. TogetherCrew has a solid track record of contributing to other DAOs, and their collaboration with researchers from UCSB further strengthens this.

For potential concerns, We recommend that the proposal more clearly define how TogetherCrew plans to handle and access data from Discord, especially given its unique privacy conditions. Maybe including more specifics regarding API access and the installation of the TogetherCrew bot on the Arbitrum Discord server to ensure that all necessary privacy and community guidelines are respected.

Overall, this should be a step towards improving community health and transparency and we look forward to seeing the results of this research.

1 Like

I support the proposal with a few suggestions:

:grinning:data privacy and security: although the proposal mentions using only publicly available data, it is recommended that further clarification be provided on exactly how the data will be used, and that the privacy policy be updated regularly to ensure greater transparency.
:grinning:community feedback: after the analysis results are available, it is recommended to provide timely feedback to the community and keep the discussion open so that everyone can clearly understand the progress of the project and the actual results. It is recommended to test the Hivemind functionality on a small scale first to collect feedback.

1 Like

gm, voting FOR.
Looking forward to seeing what insights we can unlock, and if further research can then be conducted to prove/disprove emerging thesis for DAOs (areas of interest, underserved topics, how to reduce friction for new entrants, …).

Also no cost = good

1 Like

Thank you for your work, the proposal is helpful and worth moving forward.
In addition to providing data analytics, the proposal also helps community members understand how to use the tools and increase their engagement, the dynamic reputation NFT sounds like it has potential, it is recommended to understand the community needs first to ensure that people want to use these new features.

1 Like

TogetherCrew should be fascinating and promising in the not so far future. I really like the name of the project and the whole proposal.
The concept of Web3 social networks has been gaining traction, and the Arbitrum community should have been in a prime position to launch such a project. On-chain governance is essentially a social activity, and AI and data privacy are essential components.
I hope TogetherCrew surprises us further.

1 Like

The following reflects the views of the Lampros Labs DAO governance team, composed of @Blueweb, @Euphoria, and Hirangi Pandya (@Nyx), based on our combined research, analysis, and ideation.

We are voting FOR this proposal.

Though the proposal has no associated costs, the potential benefits of the study could be highly valuable. The requested data is publicly available on the forum, and while concerns about Discord’s privacy policy have been noted, we’ve seen many DAOs provide similar access for community-driven projects. The fact that TogetherCrew is already an active member of the DAO gives us confidence that this data will be used for the greater good of the community.

1 Like

Voted For: In terms of security, I think requesting read access is fine as long as the tools are security tested. Insights into our communication channels can bring some interesting info and show how we can improve. Supporting this proposal is a small effort from the DAO and foundation side, with big benefits once the analysis is done.

1 Like

Hey Larva

The only permissions needed are:

  • read messages and read message history
  • send messages permissions (e.g. inside threads, outside threads, etc.)

Anyone can verify this by deploying the bot from our website on a test server.

We’re avoiding Admin, Use Commands, channel management, edit/delete message, manage members, and related permissions which are the ones that can be used to attack a server. As such, even if our bot is hacked, the regular Discord security is in place to prevent our bot from doing anything that’s not reading messages or sending a message (low risk actions). If the Discord security was broken, that would compromise the server but that’s irrespective of using our bot or not. A further precaution is disabling our bot from sending messages on any Announcements channel, so even if we’re compromised and someone can send a spam message, they could only do so in non-official channels. The mods will quickly detect this (as it’s already a regular procedure) and can kick-out or freeze the bot. We’ll coordinate with the foundation for this (which doesn’t require them to implement any new procedures, just operate as usual).

We have optional permissions for attach files on the messages and we’re recommending to the Foundation to NOT give us said permission, as there could be an attack vector of sharing a file with the community that contains malware. (note that the permission to share files is already regularly available for discord users so any individual could carry this attack. We’re avoiding the permission as we don’t need it for Arbitrum and hence prefer to avoid that risk on our shoulders).

Because of these precautions, we have never been required to carry a security audit by a third party security firm. And the team that deployed us have verified the permissions every time, confirming this. The Arbitrum Foundaiton will also have to configure the permissions for us (a 5-10min job, so they’ll once again verify and can hold back if there are any concerns).

2 Likes

We’re Voting For this proposal

  • The data in scope are public already
  • Only the access to API is required so that the bot (open-source) can read the data
  • This bot has already been deployed in 100+ communities, including Optimism, Celo, Aave, Aragon, Shardeum, etc.
  • The permissions are configured to be low-risk (no admin permission, no managing channels, etc. so even if the bot was hacked, the discord and discourse servers wouldn’t be compromised)
  • Research insights will be shared with Arbitrum DAO
  • No budget is required
1 Like