Encyclosphere Forum - Recent Posts https://encyclosphere.org/forums Encyclosphere Discussion Board en-US Wed, 11 Mar 2026 01:25:59 +0000 wpForo 60 RE: Botipedia https://encyclosphere.org/forums/main-forum/botipedia#post-207 Sun, 23 Jan 2022 19:12:30 +0000 Botipedia is in private Alpha release. Definitely worth checking out! Join our Slack workspace so you can lobby Phil for an Alpha login.

]]> Tim https://encyclosphere.org/forums/main-forum/botipedia#post-207 RE: Testing peer-to-peer (P2P) network for encyclopedic articles https://encyclosphere.org/forums/encyclosphere/testing-peer-to-peer-p2p-network-for-encyclopedic-articles#post-192 Wed, 15 Dec 2021 00:09:44 +0000 Is p2p the only option for network structure? What are the available options, and what is the set of parameters that governs the pros and cons between them?

]]> mason https://encyclosphere.org/forums/encyclosphere/testing-peer-to-peer-p2p-network-for-encyclopedic-articles#post-192 RE: Week 2: The components of the encyclosphere https://encyclosphere.org/forums/seminar-forum/week-2-the-components-of-the-encyclosphere#post-191 Mon, 13 Dec 2021 23:18:02 +0000 What if there was the publishing-sphere, an abstract internet-space where everything published goes, and the reference-publishing-sphere is a specific subsphere (ie encyclosphere) where everything reference-published goes. The publishing-sphere could contain both the blogosphere and the encyclosphere as subspheres, even minifeed (in a way).

Then what if the publishing-sphere is just a sub-sphere of the internet public-sphere. At the public-sphere level, the idea of a user-person arises pretty naturally. I think you should be able to make any amount of user-accounts between the user-person and the public-sphere.

User-accounts would be the main fundamental unit in all of the ‘spheres. In the Encyclosphere, user-accounts can have authorship smoothly attributed to them, and references to their authored work can be tied to user-accounts (or user-persons).

Content on the reference-publishing-sphere would be reference content. Reference content, a subcategory of content, is content composed with reference/citation. User-owners could have their authorship credited on content very easily, and all their work would link to them.

Phrasing it like this has a lot of opportunity for inoperability, but I do not have the expertise to make a formal structural opinion.

Publishing on the encyclosphere involves publishing uploading/connecting to the 'sphere's standard. Publishing software would format your document into the appropriate category so all work can be processed in a standard way by aggregators.

]]> mason https://encyclosphere.org/forums/seminar-forum/week-2-the-components-of-the-encyclosphere#post-191 Testing peer-to-peer (P2P) network for encyclopedic articles https://encyclosphere.org/forums/encyclosphere/testing-peer-to-peer-p2p-network-for-encyclopedic-articles#post-188 Thu, 09 Dec 2021 22:07:45 +0000 Testing of peer-to-peer (P2P) network  for encyclopedic articles has been started. Articles created by the EncycloReader are sent to a P2P network based on the  Hypercore Protocol (supported by the DAT project). Currently, we are testing download/upload speed and other performance characteristics using a limited number of encyclopedias that are supported by the EncycloReader. After the initial assessment of the network performance and missing features, a decision will be made about the final choice of the P2P software.

S.C. (for the KSF)

]]> schekanov https://encyclosphere.org/forums/encyclosphere/testing-peer-to-peer-p2p-network-for-encyclopedic-articles#post-188 RE: EncycloReader version 1.2 is launched https://encyclosphere.org/forums/encyclosphere/encycloreader-version-2-is-launched#post-177 Wed, 24 Nov 2021 16:48:26 +0000 Aack!!!  The Captcha!!!  What happened to our 1+1=2 Captcha?

]]> Betty Wills https://encyclosphere.org/forums/encyclosphere/encycloreader-version-2-is-launched#post-177 EncycloReader version 1.2 is launched https://encyclosphere.org/forums/encyclosphere/encycloreader-version-2-is-launched#post-173 Sun, 21 Nov 2021 17:56:01 +0000 One step closer to EncycloSphere.  The project https://encycloreader.org (EncycloReader) has been upgraded to a faster version (v1.2). Now it uses a "hybrid" search, i.e. a search using an internal database and external databases of online encyclopedias. It makes it much faster compared to the previous versions.

One can also add EncycloReader to the Firefox search bar (see its Help page).

S.C

]]> schekanov https://encyclosphere.org/forums/encyclosphere/encycloreader-version-2-is-launched#post-173 RE: Week 2: The components of the encyclosphere https://encyclosphere.org/forums/seminar-forum/week-2-the-components-of-the-encyclosphere#post-150 Mon, 27 Sep 2021 02:57:10 +0000 Higher-level ready-to-run preexisting open source software should be utilized instead of reinventing the wheel wherever possible. If it is determined that some of the desired functionality is new and not present in existing software, then at that point the first preference would be to fork an existing product's git repository and expand upon it (if allowed), and the second preference would be to create an entirely new product. One of the challenges with expanding a preexisting product is that the software developer needs to first come to understand the design and internal workings of the product, before the developer can add new features to that product. Some developers might opt to start from scratch with creating a new product, one that they come to understand as it is being created, rather than first having to understand what other developers were thinking when they created their preexisting product, before a new feature could be added to that preexisting product. The first option is ideal, but might involve higher overhead level of effort, whereas the second option is more divergent and messy, but might involve lower effort.

]]> ChrisKCMO https://encyclosphere.org/forums/seminar-forum/week-2-the-components-of-the-encyclosphere#post-150 RE: Week 2: how to prevent an encyclosphere network from being taken over https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-149 Mon, 27 Sep 2021 02:29:17 +0000 If this ends up being myriad projects going many directions with many teams using many tools, then it might be wise to implement a couple of additional management and recovery strategies. I'm only referring to the architecting and engineering stage at the moment. First, keeping track of all of the different projects, teams and tools in an organized and clear manner would be helpful. Ideally this catalog, index or menu would be easy to navigate by leaders, engineers and observers, taking one to the appropriate resource for the subcomponents in question. Second, while I would hope that contributors would maintain backups of their own contributions, it might make recovery and reconstitution easier if some sort of disaster recovery plan and business continuity plan (DRP/BCP) were implemented. This of course becomes more of burdensome as more tools are added, as relates to my previous post, but if this effort ends up being a noteworthy contribution to a more resilient and open Internet, then we wouldn't want to be lacking a recovery plan (or redundancies) if an attacker or angry ISP causes all of this work to be taken offline or deleted before it could be more broadly published and implemented.

 

]]> ChrisKCMO https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-149 RE: Week 2: how to prevent an encyclosphere network from being taken over https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-148 Mon, 27 Sep 2021 02:28:56 +0000 It seems that there are a few helpful resources to have open discussions, such as the slack channels, along with the message board (forum) posts. However, this project (really a project of projects) is a major undertaking, and I'm wondering if this needs to be broken out into different branches (which then circle back to ensure proper communications and integration), and if those collaborations might need to involve other project management tools... maybe file systems, calendars, tasks lists, idea boards, git repositories, etc. On the one hand, having a dozen different information collaboration tools might seem like a bad idea, having data going so many different directions and confusing people or getting lost; but, on the other hand, lacking different places and form factors to collaborate and organize data might prevent good ideas from being fully fleshed out in more appropriate processing and sharing environments. The old saying "when all that you have is a hammer, everything looks like a nail" comes to mind when working with a set of tools that might not be flexible enough.

 

]]> ChrisKCMO https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-148 RE: Week 2: how to prevent an encyclosphere network from being taken over https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-147 Mon, 27 Sep 2021 02:28:35 +0000 I just watched your American Thought Leaders interview and thought that it went well. Thank you for all that you're doing to help to course-correct the open Internet. Your discussion of whitelists during the interview raised some highly relevant concerns and challenges, somewhat parallel to recent discussions about DNS manipulation and hijacking concerns. I suspect that these distributed and decentralized whitelists (and meta-lists) will play a significant role in helping to manage and curate the articles that will eventually be cross-referenced in the larger stream, bringing meaningful content without complications to the reader, while simultaneously reducing incidents of co-opting and manipulation by disingenuous entities.

Who would have thought that we would (will) someday have an entire publishing infrastructure (as just one part within the larger infrastructure) focused on lists of trusted reviewers and endorsers of what is one's preferred interpretation of objective truth? This might involve lists of lists, such that one might choose to delegate their determination of trustworthiness to a distributed and decentralized shared list of trusted lists, perhaps similar to earlier web of trust implementations. This new subset of technical standards and protocols would enable one to be able to return articles that align with one's personal beliefs and predispositions. If one or more knowledge experts or endorsers in their chain of trust goes rogue (if that is the user's perception), then they could simply revoke or unsubscribe from that individual, sub-chain or even higher-level chain of trust (depending on just how bad the perceived compromise), and then optionally subscribe to new chains of trust, thereby affecting which curated articles are returned thereafter, based on those newly trusted endorsements (and perhaps other personal preferences and optional filters).

Working out how to manage, share, protect and implement these lists of trusted endorsements is going to be a big challenge, perhaps more so even than our other discussions about ensuring that DNS device resolutions aren't being blocked or poisoned. This also has even broader implications: imagine that this system is open and portable to the point of being leveraged to replace other trust delegation systems, such as (for example) product reviews on Amazon.

]]> ChrisKCMO https://encyclosphere.org/forums/seminar-forum/week-2-how-to-prevent-an-encyclosphere-network-from-being-taken-over#post-147