dip-gto90-remove-links-from-website #7
Replies: 24 comments 36 replies
-
|
Why should all Telegram references be removed? Telegram is one of the most active DigiByte communities. And aren't the Discord server, Alliance and the Awareness Team still operational? Why remove those references also? Why was this cumbersome DIP process ever introduced in the first place? It's already incredibly hard to attract people, let alone developers, to work on DigiByte in the first place. Adding cumbersome paperwork and formalities will only add an extra threshold for them. There was finally a volunteer making minor changes/improvements to the website in the past couple of months. |
Beta Was this translation helpful? Give feedback.
-
|
#The DIP process, which comes from Bitcoin, was designed precisely to elevate these kinds of conversations out of places like Telegram and place them in a more transparent, searchable, and long living medium for the whole world to see and participate in. Telegram, while an active community is not the only place the broader world interested in UTXO blockchains or open-source development lives. Worse, when conversations about proposed changes happens in telegram it's impossible to consume the history of the proposals as they get buried in the threads, conversation goes off topic, or many other negative possibilities. GitHub is a proven platform that solves these problems and massively improves the engagement experience for everyone wanting to participate. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub is centered on developers; in DigiByte's case, there are plenty of non-(core-)developers that may not have the technical know-how to literally understand source code, but are knowledgeable enough about certain matters such as Taproot, the pros and cons of certain algorithms, mining activities, et cetera. In Telegram's case, there have been plenty of very constructive discussions that have taken place there, which are quite easily searchable per channel. Sidelining certain channels where historically many interesting discussions have taken place just feels weird. I'm aware of Bitcoin's DIP process. But that's like comparing apples with oranges. Bitcoin has an enormous developer pool, activity and user base and can afford to be picky. DigiByte really can't, especially if you truly want to be able to attract good Samaritan volunteer developers in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Your points can be satisfied by linking such groups through the wiki and the discussion forum. Furthermore, you do not need to be a developer to participate in GitHub discussion forums or the wiki. GitHub accounts are free and as easily created as Telegram accounts. However, all are required to adhere to the GitHub Community Code of Conduct. Telegram, Discord, Reddit, and all other channels and forums have their place, but they also have a decade's worth of negative past performance, which is demonstrably indefensible. In the aggregate, these forums have been a net negative to push DigiByte forward and grow "developer" adoption. They are great at creating tight nit micro-communities, but by and large, they are not good at maintaining a transparent, searchable, and historical record of conversation or contribution around DigiByte. As everyone is aware, we require a new strategy to elevate the developer experience, and simply continuing on the decade-old path of what has not worked will not suddenly lead to success. The spirit of this DIP is to inspire a conversation around a new approach to growing the engagement of the DigiByte protocol’s economic majority. |
Beta Was this translation helpful? Give feedback.
-
|
This is super weird. Remove links to places to gather and discuss, trusted places. Just leave everyone to fend for themselves and having to claw for groups and platforms to trust? All because what? And removing the self-help tool? Sure, it's not particularly pretty, and could be more user friendly, but where are these people going to find their information? Obviously not on ANY of the social media platforms because they are being removed from the website. Very weird. |
Beta Was this translation helpful? Give feedback.
-
|
I respectfully disagree that everyone views Telegram as a trusted place to communicate about DigiByte. That said, this proposal is about centering DigiByte first contact on DigiByte and not external groups or communities. Guiding them to GitHub where they can find those communities via the Wiki or Discussion forums. This is similar to what Bitcoin.org has done with the main difference being that they burry external links on tertiary pages versus the main pages. |
Beta Was this translation helpful? Give feedback.
-
|
I think you make fair points. I have read your other comments here, also there do I think you make fair points. I don't let myself be too bothered with whether Bitcoin.org or Litecoin did it, I don't think that is necessarily a ruler for anything. That being said, I do see how this would be a good thing for the website and for the project in general. It is unfortunate for all the people who have been trying to build micro communities over the years. Then again, perhaps there doesn't need to be DigiByte centered forums other than Github. There is more than enough social media to go around, that offers far wider horizons that that of Telegram and Discord groups and servers. I would be interested to see this play out. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for participating in the process and this discussion! I absolutely appreciate what you are saying about looking towards Bitcoin or Litecoin as examples all the time but for me personally I think DigiByte could use some of what has worked so well for our peers. We have certainly tried to do things our own way over the past ten years and it just hasn't worked out all that well. As such I think we should consider adopting what has proven to work. All of these communities have a role to play, but I think we should consider guiding everyone through a free and more transparent portal before directing them to external channels. |
Beta Was this translation helpful? Give feedback.
-
|
This is a very bizarre proposal. The website is the one place that makes it easy for community members to find each other. The telegram and discord groups are both in active use and serve as essential tools in how the community communicates with each other. The Matrix group that was intended for communication by the core devs is not even used by the core devs. If it was, perhaps the communication would be less fragmented. Making these groups harder to find is a bad idea. They work. There are where 80% of the discussion has always taken place. |
Beta Was this translation helpful? Give feedback.
-
|
I agree that Matrix, formerly known as Gitter was a failure. The intention of that change was to connect communications directly to the code being discussed. It worked for a short time but as you pointed out, it did not hold. Telegram has the exact same story. Most core maintainers have left Telegram and do not or will not use it. The new developers that do, end up not working directly with the core maintainers that are centered on GitHub. This leads to a splintered development experience which has proven to be ineffective for over seven years now. GitHub is free, it is massively transparent and will center all development participation in the place where open-source development the world over thrives: GitHub Finally, I believe other groups like the Alliance or DGBAT are better positioned to market and promote a broader spectrum of communities and channels. This proposal is about making the first contact for DigiByte about DigiByte and where to go to get involved with its development: GitHub In the end this proposal is a leaner Bitcoin model which has clearly proven to be a more effective model than what DigiByte has had for the ten years of its existence. |
Beta Was this translation helpful? Give feedback.
-
|
I agree that discussion directly related to DigiByte Core should ideally happen in a single place, and that should probably be on GitHub - ie public discourse between digibyte core developers and other interested parties concerning the development and direction of DigiByte Core. By all means choose a place to have this discussion and stick to it. Matrix could have worked well for this (it still could) but none of the core devs have ever embraced it for some unknown reason. Questions went weeks and even months without receiving a response, but this has also sometimes been the case on GitHub as well. What matters is not where the discussion takes place, but more that there is actually an active discussion, with people responding in a timely manner. Much of the discussion moved to discord simply because questions posted in other channels went unanswered. I also still don't see why the links to telegram and discord etc. need to be removed from the DigiByte website. They are actively used for community discussion, and mostly do not concern core development anyway. The website is much more of a community site than being specific to the DigiByte core protocol. Perhaps the current website should be handed off to DGBAT as a community site, (which it basically already is), and DigiByte Core should create its own website solely focused on the core protocol. (Much like Dogecoin have things setup.) Just an idea... I'm thinking like this: https://bitcoincore.org/ |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea of having DGBAT, the Alliance, and similar groups using their websites to take over the non-developer aspects of promoting DigiByte. These groups already have well-established domains, websites, and socials, which are perfect for taking over the social aspects of DigiByte. Other community groups could even fork the existing website repository as it is open source and maintained by DigiByte-Core. Unlike Bitcoin, however, I do not propose creating a DigiByteCore.org domain. The current website and domain are a part of DigiByte-Core, have been well established, and are best suited to steer new developers and adopters to a more authoritative set of resources to get started with DigiByte, the protocol, and blockchain. To be very clear, though, I suggest we move links to these social communities to the wiki and a thread in the discussion forum. I would like to see many more communities that are yet to exist created over time, all of which can be linked in the authoritative wiki and discussion forum. However, digibyte.org should refrain from promoting these groups from the main page. It should be 100% focused only on DigiByte. |
Beta Was this translation helpful? Give feedback.
-
|
I am quite surprised of the proposal to remove some of the key platforms people use to follow what is going on with DigiByte. Telegram and Discord are very active. If we would remove those, why would we not also remove any links to the cesspool that X has become? If official links are removed, I believe more fake platform accounts/groups/servers will be created to scam people, and people will have a more difficult time knowing what is real and what is not. Maybe wording could be changed to try to push more people to GitHub for discussion, but still have an area that has links to the known good social media accounts/groups/servers. Just my thoughts. |
Beta Was this translation helpful? Give feedback.
-
|
First contact for who though? End users? Developers? It seems to me that the former should never need to visit GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
First contact for the DigiByte economic majority and developers is what is behind the spirit of this DIP. I think other groups and communities should consider forking the existing website repository and publish and promote what makes sense for other non-developer groups. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is where I am struggling with this. For development related stuff, I agree this is probably the best place for those discussions to take place. Great points have been made about this. Hopefully GitHub can be a place that all people who wish to discuss development related topics can agree to go to. I know some people will not use Telegram. Some won't use Discord. I personally don't believe X is good for much, especially any real discussion. Will the goal be to push any development discussions from these other platforms to GitHub? If people are to be channeled, they have to be channeled from somewhere to here. I am having a difficult time figuring out where new users, people who want to talk about buying and selling and price, or people wanting support with an old wallet or something like that will figure out where to go. If I were looking at a new project, and if I knew GitHub was focused on development, then that is the last place I would visit to see what people are saying about the project (from a non-development perspective). When I have looked at other coins in the past, I have gone to their websites, found their Telegram and/or Discord links, and then visited those. So if we remove these from the DigiByte site, how will people find them and know that they have not run across a scammer created copy of a Telegram group or Discord server? Please don't take any of this as me being against what is being proposed/discussed. I am trying to wrap my head around what it really means. |
Beta Was this translation helpful? Give feedback.
-
|
@beggsdl , You are absolutely correct that the proposal for the changes to the DigiByte.org website is made to direct folks to GitHub for their first contact for things like:
Each of the above are open to the entire community via the GitHub Discussion link located on the core protocol's repository (which is where these website changes would direct visitors). Anyone can create discussion threads and reply to discussions in a transparent and open way that is searchable and maintained by GitHub (e.g. no need for individuals to operate infrastructure, manage DNS, or individually moderate). That said, all participants would be required to adhere to the GitHub Community Code of Conduct (which is not something we enjoy with Telegram, Discord, Reddit, or X). The biggest advantage, though, is the searchable history of all discussions, which would benefit all future visitors. Telegram and Discord are terrible for this. In terms of how to route visitors to various external community channels, I would prefer to see those moved to the Wiki much like Bitcoin.org buries those in tertiary web pages. Additionally, I would like to see DGBAT or the DigiByte Alliance step into this conversation and consider taking over the more non-developer-related community promotion. |
Beta Was this translation helpful? Give feedback.
-
|
To be fair most people who aren't developers don't search for their coin of choice from a website, rather most use the social media platform. They will easily be able to find all community related handles and expand from there. I love the idea of having a somewhat designated platform purely for the development of digibyte and all the distractions are filtered out. |
Beta Was this translation helpful? Give feedback.
-
|
First of all I understand this is a community discussion for a DigiByte Improvement Proposal (DIP) to remove 3rd party links. Let’s follow the process. I think it important to clarify for anyone reading the comments who might think the proposal changes are set in stone. After thinking about it, When I first started bringing up issues about the website it was because of the mobile wallets. Then started to notice things about the website that needed improvement. IMO, the website was focused on marketing the DigiByte mobile wallet. The landing page image, the videos, mention of the wallet in every section and in the downloads. We have worked to remove most of them, however, some remnant remain. It think the Litecoin website is a good example to emulate, short and to the point. It has 3rd party and social links but the DigiByte website can be modified. I’m open to the idea but my suggestion is if it’s going to remove some 3rd party links, maybe they should all be removed and focus the website on DigiByte the L1. This change also avoids adding and deleting exchanges, wallets and services. We recently cleaned out wallets that were retired, exchanges and services that went out of business. We added DGBCommerce only to remove it a short while later. Here is a link to the Litecoin website as an example. |
Beta Was this translation helpful? Give feedback.
-
|
The spirit of this proposal is to take a leaner Bitcoin model which funnels interested participants to BitcoinTalk. Additionally they bury those links behind tertiary pages so as to focus the visitors attention primarily upon Bitcoin and not in externalities. In this proposal all such links would move to the wiki or a discussion thread. Additionally, I believe third party advocacy groups should take a lead role in advertising these external communities. The DigiByte Alliance and DGBAT are much better equipped than the core protocol developers to maintain the scope and breadth of those channels. This proposal invites all passionate participants to engage with DigiByte through the one platform where open source development thrives: GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
Some very valid points have been made above by many people, thank you all for your input and comments on this dip. I believe in the long term focusing communication on GitHub around the code will greatly benefit DigiByte. For the most part telegram & a lot of social media have turned into a cesspool of misinformation and toxic behavior around DGB. This often poisons, and turns away newcomers wanting to help or build/ integrate on DGB. I lost count of how many times people have reached out to me privately telling me they are distancing themselves from DGB because of all the attacks and toxicity on social media. Prominent YouTubers, leaders of crypto companies, fortune 500 businesses, talented developers, investors and more. None of them wanted their brands or personal reputations tarnished and drug through the mud by toxic members of the DGB community across social media, many being nameless and faceless behind troll accounts. GitHub seems to foster a more professional, balanced discussion around DGB than any other source or medium of communication. Looking back over the past several years many of our issues as a community came from a lack of clear communication & understanding. Often you had people with good intentions who were not technically experienced miss misinterpreting things that quickly turned into toxic FUD across social media. And the discussions to clarify many of those issues never happened anywhere in a publicly neutral forum. Many of them to this day have never been publicly discussed to clarify. They are only used in back channels/social media to spread targeted FUD against DGB. I have had people arrogantly brag to me they have paid for targeted attacks against DGB, myself, and others on social media in order to suppress the price of DGB and buy it up cheaper. This is just the reality of the world we live in. Regardless, as I mentioned publicly I will be leaving DGB publicly, removing myself from the DigiByte-Core as an admin and will have absolutely 0 public control/ input/ or influence on the future of DGB. For many reasons the time has come for me to publicly step away. I detailed this more here: https://twitter.com/jaredctate/status/1803090870553411673 In the end this is all up to the community on where to take things. It is my belief not having a public founder around working on things may help resolve a lot of issues once and for all. If the community focuses on the code, fosters a professional and collaborative discussion system around the code, and provides a neutral place for everyone to come together then DGB will prosper in the long run. No one is saying these other means of communication need to disappear, people are free to do whatever they want, where ever they want & say whatever they want. But what has been happening the last few years is clearly not working to help grow DGB awareness in a positive manner. Funneling new, motivated community members into a cess pool of toxic trolls is very counter productive for growth. They say be the change you want to see in the world, so with that I am removing myself completely from the DGB equation in hopes others will make good changes that will be in the best interest of DGB long term. With that, thank you all for participating in this discussion here on GitHub and caring for/ believing in the future of DigiByte. My previous announcement on publicly leaving DGB posted on X:
FYI we have now mined odo blocks with 8.22 RC4 on main net. So we have mined all 5 v8.22 RC4 algos. I think 8.22 is basically ready for a release outside of a few quick PRs for adjusting seeders people no longer have up, resetting testnet and possibly some TOR settings/ seeds. |
Beta Was this translation helpful? Give feedback.
-
|
Good insights and points brought up. We are a decentralized blockchain and with it comes great benefits and also challenges. In the time I have been with the project, there have been many FUD attacks, constant vitriol and even personal attacks. While everyone has their own to right to believe in what they want, moving discussion to a professional environment like Github will allow us to focus on the items to continue improving and/or showcasing DigiByte. Anyone can still create their own community on the various social platforms, but we need to drive the focus where we can get the highest probability of bringing in more folks into the ecosystem. I can also say that anytime we wanted to deviate in the past, we were hit with hate and doubt. We kept things the same for years and the cycle does not change. I welcome a fresh approach and will be happy to do my part in supporting DGB. |
Beta Was this translation helpful? Give feedback.
-
|
While I am for removing third party references on the DigiByte.org website, I am against removing links to social media sites to DigiByte community forums like telegram, Facebook, discord etc. DigiByte has always prided itself on being a community/volunteer driven grass roots supported public blockchain that only exists today due to the 10 years long support of those volunteer community members. Can those channels be a toxic waste land of negativity regarding DigiByte owing to certain community members who honestly should just move on if they feel the way they do? Yes. However I feel like keeping the benefits of keeping those channels on the website for widespread adoption of DigiByte outweigh the negatives of discussions that may occur. If the devs want dev discussions to happen in Github the website can designate that location for that purpose explicitly. When I first learned of this initiative I was against it and after thinking about it over the past 2 weeks I am still against it. It smells like indirect censorship of the community and will have a chilling effect on those that are DigiByte curious from finding out about us in a natural organic way-through our website and not buried on a secondary wiki page. Not to mention someone new to crypto not having to open a GitHub account to ask a novice question from existing members of the community. Crypto can be daunting at the beginning-do we want to make it more difficult for future community contributors to get answers and have access to resources? For a blockchain that espouses anti censorship principles this effort seems more than ironic. I understand the effort to direct traffic to GitHub for dev purposes but don't think cutting off explicit access to social media channels for a public blockchain supported by volunteers is the way forward. Furthermore, I get the desire to "be like Bitcoin." When we have the adoption rate and legacy system support to justify that approach maybe I could be swayed. For now, I think we need to maintain the social links on the website to keep multiple organic growth pathways open. |
Beta Was this translation helpful? Give feedback.
-
|
I agree with streamlining the links on the website and removing third party entities. I understand wanting to focus on Github for more professional conversations around core upgrades and collaboration. However, the social media links do offer a pathway for the non developers. The channels linked have admins and while nothing is perfect when it comes to communication styles of the participants I have also seen people new to DigiByte and crypto get guidance on avoiding scams and lessons learned when trying to navigate the overall space of crypto. This process of the pull request will take some time and will go through iterations before it would be merged and I am grateful for the discussion being had here in that regard. |
Beta Was this translation helpful? Give feedback.
-
|
I think these proposals are heading in the right direction. Improving transparency, decentralization, and community involvement is key to DigiByte's long-term success. Effective governance helps the project stay resilient and adaptable, which is crucial. On the topic of removing social media links from the community section, it's a bit tricky. While it might reduce distractions and streamline governance, social media is essential for community engagement and communication. It's important to balance governance efficiency with keeping open channels for interaction. If removing the links hurts community engagement, we might need to reconsider or find a middle ground. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you to everyone who has participated in this DIP discussion thus far. I have opened a PR for a revised draft of this DIP, which takes into account the feedback provided to propose a compromise in the search for a rough consensus. This PR has been accepted and merged by a DIP editor and assigned DIP 0002. Please review the draft DIP here and continue the discussion here as we work towards rough consensus. |
Beta Was this translation helpful? Give feedback.
-
|
The dgbwiki has a common creative license, anyone can create an account and contribute. Challenges, admins are no longer in the community or are not available due to personal responsibilities. Some pages are protected and cannot be updated without an admin. I have recently been in contact with Nigel one of the admins and have made him aware of this proposal. Alternative/temporary solutions: add more admins to dgbwiki, remove protected pages. Over the past two years there have been discussions between community members about the wiki, making it an encyclopedia of information about DigiByte without endorsing third party links. I assume the dgbwiki will be taken down and replaced by a new wiki. Oliver a contributor to the community created a new wiki and it is supposed to be the informational DigiByte encyclopedia mentioned above. However, Oliver has resigned his volunteer duties temporarily or permanently. The new wiki is in the DGBAT GitHub organization. One of the challenges with the new wiki is a lack of contributors and contributions, it is a work in progress. Solution: to have the new wiki complete regardless of changes to DigiByte. Org. It is important that all the readers of this discussion and community members be aware of the overall situation regarding the information infrastructure. Recommendation: communication and coordination between the DigiByte developers, dgbwiki admin(s), other supporting entity such as the DGBAT since new wiki is in their GitHub organization. Complete new wiki, decide whether to keep old wiki or take it down, make changes to DigiByte. org. |
Beta Was this translation helpful? Give feedback.
-
|
I really appreciate lifting this conversation about the wiki. The new wiki that I put forward is something I really believe in. It is user friendly, modern, and most and foremost includes ready solutions for versioning integration with Github. Unfortunately, the current "new" wiki will eventually be taken down, but I am not in a rush to do so. As Jose has pointed out; all the content is available on GitHub under the DGBAT organisation. The new wiki runs on the wiki js, a Node JS application. Installation and usage documentation is fairly good, and I am available to assist with installation and setup if necessary. |
Beta Was this translation helpful? Give feedback.
-
|
I think it would be fine to have DGBat maintaining the Wiki for the record. Let me know if that is what the community would prefer and I will update the DIP accordingly. |
Beta Was this translation helpful? Give feedback.
-
|
For what it's worth I agree with the proposal. Community comes and goes, we all die some day. Code and protocol is here to stay. |
Beta Was this translation helpful? Give feedback.
-
|
There have been a lot of great comments on this thread, with some great suggestions. I believe taking some of the feedback into this DIP and arriving at a rough consensus the community agrees on is a win-win for everyone. I also think it is important to look at things from the perspective of what will be easiest to maintain long term. Over the last decade, we have seen many people come and go who have helped provide support infrastructure. For example, I think we are on the 7th version of the DGB website. I think the more open source and easier we can make all supporting infrastructure to access on Github we will not have to worry about "handing" things over to the next people who come along. If everything is accessible on GitHub anyone can simply fork a repo and take over. I think filtering links through the lens of what is absolutely necessary vs what is nice to have for the moment can be helpful. All sorts of exchanges, wallets, services & platforms have come and gone, been shut down, gone under, or been hacked. I don't see this cycle changing anytime soon over the next decade. |
Beta Was this translation helpful? Give feedback.
-
|
@Sbosvk Can the Wiki be hosted from Github pages? |
Beta Was this translation helpful? Give feedback.
-
|
The platform Wiki JS can not, but the markdown files can be hosted as a GitHub wiki, which offers less styling and navigation options, but is for sure possible. |
Beta Was this translation helpful? Give feedback.
-
|
@Sbosvk , I don't know if we need to duplicate that effort if we can't run the Wiki via GitHub pages. I thought we could save individuals from managing servers and related infrastructure, but that wouldn't be possible if WikiPages requires a server to run. However, if you are comfortable with maintaining that for the community, then I can update the DIP to reflect that and any other suggestions related to the Wiki. If maintaining that ever becomes a burden, then we could begin migrating all the MD files into the GitHub wiki and update the landing page to point there instead of the hosted wiki. Let me know and I will update the DIP accordingly. |
Beta Was this translation helpful? Give feedback.
-
|
I have been giving this some fair thought. I have decided not to keep maintaining the new wiki platform. Frankly, I am stepping away completely from DigiByte, and I don't want the cost of running the server or spend time maintaining it. Installing the platform is not hard, and running a server is cheap, and since it's a docker image one would not even have to run a full server but could get away with a droplet, but I will not be doing it. If nobody else wants to then that is just what it is. I have already resigned from DGBAT and have no access to the repo to even keep it maintained. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for replying @Sbosvk ! I completely understand your position and appreciate, as well as respect, all that you have done for DigiByte. Given that you will be taking the wiki down, I will update the DIP to reflect migrating the wiki to GitHub Wiki which will cost nothing and can be maintained by any contributors with a GitHub account. I will work to create a wiki page that has instructions for how to fork the wiki and open pull requests with wiki changes. This will eliminate the need to manage hosting infrastructure for the wiki and will also open up broader OSS community contributions. |
Beta Was this translation helpful? Give feedback.
-
|
About a week ago a couple of community members reported that dgbwiki .com was down (X, T .me), it temporarily came back online, however, it has been down since 08/12. DigiByte .org has a lot of embedded URL’s that direct users to dgbwiki .com (old wiki), when you press the links you’re directed to a blank page. I went to wiki .digibyte .org (new wiki) to see if the same information is on this wiki, however, an error page comes up that the connection is not private. My initial thought was that the embedded links could be updated to redirect to the new wiki, however, as I mentioned the connection is not private. My comment here is to make everyone in this conversation aware and but also to maybe generate momentum to work towards a workable solution. It was my understanding that old wiki would be replaced by the new wiki, mainly to get away from 3rd parties and to make the new wiki the encyclopedia of DigiByte. In my opinion, I think this is a perfect opportunity to move to the new wiki, however, the embedded links on DigiByte .org need to be updated or removed. I think the embedded links should be updated so that people can still access the information, that’s my opinion. Which leads us to the issue of wiki .digibyte .org, @Sbosvk has resigned from his previous volunteer responsibilities, the new wiki is in the DigiByte Core organization, I think the security certificates need to be updated to make it a secure connection for the public. Final thought, to gain and maintain-past, current and new support the DigiByte community needs to present the best version of DigiByte whether that be the Core Wallet or the informational infrastructure.
|
Beta Was this translation helpful? Give feedback.
-
|
I've updated the cert now. |
Beta Was this translation helpful? Give feedback.
-
|
The Wiki will be migrated to here and DigiByte.org links will need to be updated to reflect that. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @Sbosvk for the immediate response. Thank you @ycagel the info you shared helps in understanding how the wiki is being implemented into the DigiByte Core organization. I created an issue on digibyte .org repo for the affected embedded links Old wiki embedded links. If the issue needs to be broken down into smaller issues i can go back and do that. |
Beta Was this translation helpful? Give feedback.
-
|
@Sbosvk My overall intention is to add information to GitHub wiki to have DigiByte .org to link back to. I am indifferent about having Jared’s Biography included or not, however, there is a W Biography link on DigiByte .org. I think this is an appropriate forum to discuss including or removing Jared’s Biography from the wiki. What are the commenters thoughts and opinions on including or excluding Jared’s biography. Read comment below for context. |
Beta Was this translation helpful? Give feedback.
-
|
@DGBNOOB , The Wiki is being moved to GitHub Wiki here using the Markdown files from the digibyte-wiki repository. I do not believe we have Jared's bio in the new Wiki, and I think your PR was appropriate. This would allow the community to comment on and debate their inclusion. I would love to see more community members contribute to the new Wiki now that it has a more accessible and transparent interface. I don't see any harm in including historical knowledge about DigiByte, including its founding contributors, as long as that information is in the Wiki and not promoted on the main website. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your feedback/input on all. @Sbosvk pointed out some discrepancies with some of the files that were in the PR, which might have been due to committing files from digibyte-wiki repo. I was trying to commit only the files I changed and staged on my local repository but all the digibyte-wiki files were pushed. I will clone Github Wiki and try again. |
Beta Was this translation helpful? Give feedback.
-
|
I want to make a recommendation pertaining to GitHub Wiki, which directly relates to DigiByte .org. I want to recommend that the maintainers of the GitHub Wiki add an edit in place feature "the edit pencil" to the GitHub Wiki. For anyone reading along and not familiar with this feature, you can see it on the DigiByte-Core/digibyte README. This feature lowers the barrier for community members to make contributions to the GitHub Wiki. Community members contributions would still require the pull request/review process. Again just a recommendation, would love to hear community feedback since this is a discussion. Attached are two examples of the edit in place "edit pencil". Example 1 README upper right hand corner: Example 2 DigiByte-Wiki repo Terminology file : |
Beta Was this translation helpful? Give feedback.
-
|
I've never used this feature but I'm pretty sure it's always available? You would create the PR via the GUI. |
Beta Was this translation helpful? Give feedback.
-
|
I used the edit in place to add to the terminology file in the digibyte-wiki/terminology.md in the digibyte-wiki repository. The DigiByte-Core/digibyte/wiki only has the option to clone the wiki onto your local machine. When you fork the DigiByte-Core/digibyte repo the wiki doesn't automatically fork into your remote repository, it's a little more complicated and I haven't figured out how to commit my changes from local wiki to remote wiki on my GitHub wiki. With the edit in place feature the changes can be committed as a patch. |
Beta Was this translation helpful? Give feedback.
-
|
Aha, I see. Speaking of the Wiki I had to shut down the server for the wiki.DigiByte.org deployment because of corrupted filesystem, so that is now a dead url until whoever's in charge of the DNS (DGB Alliance I believe) changes it to point to the GitHub wiki. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, @DGBNOOB, GitHub Wiki does not support editing in a place as it does for traditional code files. Alternatively, below the table of contents is a link to clone the wiki: https://github.com/DigiByte-Core/digibyte.wiki.git. After cloning the wiki repository the user can make changes to the wiki by creating new files, editing existing files, and then opening a pull request which will go through the standard review process. While this may seem like a barrier to entry, I personally believe it's easy enough for anyone to learn how to do this and should be encouraged so that community members can gain more appropriate experience engaging with DigiByte development. GitHub provides a number of GUI desktop apps for all platforms that make this easy: https://github.com/apps/desktop |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, |
Beta Was this translation helpful? Give feedback.
-
|
This. We need to learn to execute quickly, especially on non-protocol matters: Don't let perfection be the enemy of progress in matters like these. Continuous improvement loops should be the goal here, with more participation each cycle. Nothing but love and respect for each and every one of you. Have a great day. |
Beta Was this translation helpful? Give feedback.
-
|
I'm involved in several discussions about dip-gto90-remove-links-from-website, both publicly and privately. At this point, to move forward on this DIP discussion, someone has to create the PR with the proposed changes. I'm writing this to share with everyone in this discussion not involved in the different conversations. My recommendation is to gradually make the changes from section to section, as the website is available in 35 different languages. The most contentious removal is the community/social media network card. My recommendation is to make this change last or come to a compromise. I want to remain neutral, impartial, and indifferent in moving forward with the removal of all social media links except X. This is why I recommend coming to a compromise or making this change last to allow for more discussion about this change to the website. Based on the information being shared, one option to make these changes is by creating a GitHub project in the repo and creating tickets for it. I have contacted @DennisPitallano about helping with making the changes, and he responded that he is interested and available. I will help where I can to review; however, I also recommend adding one or two more reviewers in case I have other commitments. I don't want everyone waiting for me, but I will help when available. The removal of social media links, except for X, is a point of friction to work through and has the potential to upset certain DigiByte sub-communities because not everyone will agree with the final decision and end product. This is your opportunity to speak now or forever hold your peace. |
Beta Was this translation helpful? Give feedback.
-
|
If your going to remove social media you should also remove X. In a world where people are rapidly abandoning X it makes more sense to promote distributed open systems like bluesky then closed off old platforms like X. |
Beta Was this translation helpful? Give feedback.
-
|
Considering the point of the DIP is to control the narrative I doubt X will be removed since this is the biggest tool the Core organisation have for controlled narrative. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
All the groups that were linked on the website are being moved to the Wiki. This was agreed upon here. |
Beta Was this translation helpful? Give feedback.
-
|
This will be the first of several issues raised to facilitate, "Proposed Section Changes" in this discussion “Draft DIP to make www.digibyte.org changes”. |
Beta Was this translation helpful? Give feedback.
-
|
@gto90 The first issue was created to start the website changes, and a pull request has also been created to address the issue. For cards that are being removed from the website, some of them are to be relocated to the discussion forum.
I think the forum discussions need to be created first. After a little bit of direction and guidance, we can start the review for website changes and the removal of third-party links. |
Beta Was this translation helpful? Give feedback.
-
|
@DGBNOOB , I replied to the open PR with a few requested changes, but I think it's moving in the right direction. Our current gap is that we need to get all the community links into the new Community Page on the wiki. |
Beta Was this translation helpful? Give feedback.
-
Draft DIP to make www.digibyte.org changes
Preamble
DIP: TBD
Title: Remove Third-Party Links from DigiByte.org
Authors: GTO90, ycagel, JaredTate
Discussions-To: DigiByte GitHub Discussions
Status: Draft
Type: Informational
Created: 2024-06-20
License: BSD-3-Clause, CC0-1.0
Abstract
The purpose of this DigiByte Improvement Proposal (DIP) is to discontinue promoting third-party social networking applications, websites, and advocacy groups on the DigiByte.org website. By removing these external links, we aim to focus community engagement and informational resources within the DigiByte-Core GitHub ecosystem. Visitors of www.digibyte.org seeking more information, especially third-party content, will be directed to the DigiByte-Core/digibyte GitHub Discussions forum and Wiki. This approach will ensure that all discussions, updates, and resources are consolidated in a single authoritative location, promoting transparency, consistency, and better collaboration within the community. This change will also enhance security by reducing the risk of misinformation and reliance on third-party platforms and advocacy groups. Ultimately, this DIP seeks to strengthen the DigiByte development community’s focus on core development and authoritative resources, fostering a more cohesive and informed environment for all protocol stakeholders representing the DigiByte protocol’s economic majority.
Rationale
The primary objective of this DigiByte Improvement Proposal (DIP) is to enhance the integrity and focus of the DigiByte community by consolidating all informational and discussion resources within the DigiByte-Core GitHub ecosystem. Over the past decade, the DigiByte protocol development team has encountered challenges related to the spread of misinformation, unrealistic expectations, and fragmented communications. These issues have often stemmed from the diverse array of third-party social networking applications, websites, and advocacy groups previously mentioned on the DigiByte.org website.
This proposal aims to streamline and unify community engagement by guiding users to a single, trusted platform. This approach will enhance transparency, consistency, and foster better collaboration and information sharing among all stakeholders of the DigiByte protocol. Redirecting visitors to the DigiByte-Core/digibyte GitHub Discussions forum and Wiki ensures that all discussions, updates, and resources are sourced from a dependable and collective repository.
This change is not intended to undermine the value of social media and chat applications but to minimize the risks associated with misinformation and enhance security by reducing reliance on external platforms. By emphasizing core development and trusted resources, we aim to create a more connected and informed environment for developers, users, and enthusiasts alike. This proposal ultimately seeks to strengthen the DigiByte development community’s focus on essential development and reliable resources, fostering a more unified and informed environment for all protocol stakeholders representing the DigiByte protocol’s economic majority.
This strategic shift will significantly benefit the DigiByte developer community, promoting a more robust, transparent, and harmonious ecosystem while also delivering a higher quality of life for contributing developers.
Proposed Section Changes
Page Header
Change:
Remove:
The history of DigiByte
Change:
In this section, the link to the DigiByte Pipeline should be removed. DigiByte does not have a centralized governance structure. Instead, a decentralized group of long-standing contributing developers maintains and steers the protocol code base and related repositories based on the DIP process and contribution guidelines. Given that, there should not be an implied “roadmap” as we are encouraging the community to contribute DIPs to the protocol to propose future changes to the protocol. Therefore, the link in this section should be changed to the following:
“To learn more about proposed changes to the DigiByte protocol, please visit the DIPs repository: DigiByte DIPs Repository
To learn more about how you can contribute to DigiByte development, please visit the GitHub Discussion forum: DigiByte GitHub Discussions”
Not an ICO
Remove:
Getting started with DigiAssets: Need more help?
Remove:
Replace:
DigiID: Frequently Asked Questions
Remove:
Replace:
Community: DigiByte Alliance
Remove:
Replace:
Community: DigiByte Awareness Team
Remove:
Replace:
Community: DigiByte Developers
Remove:
Replace:
Community: Social Media
Remove:
Replace:
Community: Telegram
Remove:
Replace:
Community: Meet the creator of DigiByte
Remove:
Replace:
Community: Social Media Disclaimer
Remove:
Replace:
Contribute to the DigiByte Community
Remove:
Replace:
Debit Cards
Remove:
Replace:
DigiID Apps
Remove:
Replace:
Page Footer
Remove:
Replace:
Page Footer: DigiByte Links
Remove:
Replace:
Page Footer: Resources
Remove:
Replace:
Beta Was this translation helpful? Give feedback.
All reactions