Give&Receive backlinks with BCH webring

#1

Hello Hello.

It has been some time since I have launched a webring for BCH websites. Any website joining the webring will receive backlinks from other websites in the ring, and also give backlinks to them. Thus, boosting discovery, exploration and potentially SEO for all websites in the ring.

Any website which would like to join, will simply need to put these 3 links in their page(s):

https://bchwebring.com/me/website-name/next -> Next website in the ring
https://bchwebring.com/me/website-name/previous -> Previous website in the ring
https://bchwebring.com/me/website-name/random -> A random website in the ring

The webring is here. Let me know if anyone is interested in joining!

Also see this related idea to boost SEO of BCH websites:

https://bitcoincashresearch.org/t/improving-seo-of-bch-contents-with-related-content/1882/2

#2

Is this a different webring to the one used by https://bchexplorer.cash/? See the bottom of the page. Seems like it is from your list of included sites, which doesn’t have that one.

I would like to join with bitcoincashpodcast.com, but we should all coordinate on one webring instead of having multiple different ones if possible.

1 Like
#3

Yup it’s a different one. Because of reasons Melroy never told me as far as I remember, Melroy started another webring after I started me thing.

2qx from awesome-bitcoincash also said unfortunately he cannot join the webring I launched… However, he did include a link to me in the list.

#4

Oh the previous link is this:

https://bchwebring.com/me/website-slug/prev
#5

Just some thoughts on a webring that could last for decades.

For extreme longevity…

  • DNS registration is often the first thing go on a project
  • The integral of the cost of a backend service with a nominal fixed cost is infinite.
  • Countries can be disconnected from the internet for weeks or months (i.e. Iran)
  • Administrative districts on isolated power grids may experience catastrophic shutdowns. (i.e. Texas)
  • Even a backend service on owned power and hardware with redundant outbound connections would be contingent on the party maintaining it continuing to exist (i.e. 2qx)

One solution to unreliable service model is to instead define a protocol. We have a system for protocols.

For example …

A list of links (and names) that can fit in a 128 commitment lengths can be handled by a contract.

The list “owner” can hold a minting NFT. They could either share mutable tokens with interested sites, or just sell them for a nominal fee.

Anyone could write their record on the commitment and send it to a contract controlled by the minting NFT. If anyone posts malicious links, or a domain is taken over, the list admin can burn the NFT holding the record off the contract.

I believe a contract verifying that the first input is a minting baton is simply:

<authCategory> OP_0 OP_UTXOTOKENCATEGORY OP_SWAP OP_2 OP_CAT OP_EQUAL

Different lists could be created with different CashToken series, by changing the authenticating category. The linking software would just query the unspent transaction outputs off the contract, parse the NFT commitments and then pick a random, next or previous.

The linking software could support multiple federations of rings.

An identifier could be added to give all the webring P2S scripts the same prefix.

<PROTOCOL_IDENTIFIER>
   <authCategory> OP_0 OP_UTXOTOKENCATEGORY OP_SWAP OP_2 OP_CAT OP_EQUAL 
OP_NIP

For the NFT records held by the contract, there could be different kinds of commit records, denoted by shortcode prefix:

<"WM"><LIST_NAME><OWNER><DESCRIPTION>
<"WV"><VERSION>
<"W0"><SITE_NAME><OWNER><SITE_URL>

I’m just thinking out loud here about how to deploy the service we want as a protocol rather than a service.

1 Like
#6

If anyone, including 2qx has such these thoughts, please do share them here! Me mind is gonna go hype! Boom boom!