wonderfulsoftware / webring Goto Github PK

tbw

Suggested by @whs

Hello! 👋

As part of occasional housekeeping, which includes tidying up the webring, I will be removing sites from the webring that no longer has a backlink. This has been scheduled to take place on 2023-11-11.

The following table lists the websites that are missing a backlink:

• If you are on this list and would like to continue your participation on the webring, please make sure your site is accessible and has a backlink by 2023-11-10. I will re-check the websites again by that time. Thank you for your continued support.

• Otherwise, no action is required, and thank you for your participation on this webring project.

Regardless of whether you choose to continue participating or not, your participation helped us grow this webring by a lot, and I appreciated it very much!

@wiennat's site has Prev/Next/List link, we should support that natively

As part of occasional housekeeping, which includes tidying up the webring, I will be removing sites from the webring that no longer has a backlink. This has been scheduled to take place on 2021-11-11.

The following table lists the website that is missing a backlink:

• If you are on this list and would like to continue your participation on the webring, please add a backlink by 2021-11-10. I will re-check the websites again by that time. Thank you for your continued support.

• Otherwise, no action is required, and thank you for your participation on this webring project.

Regardless of whether you choose to continue participating or not, your early participation helped us grow this webring by a lot, and I appreciated it very much!

อยากให้ https://webring.wonderful.software/ มี Link กลับมาที่ GitHub นี้
เพื่อที่เวลาคนที่สนใจเข้าไปที่ Webring แล้วอยากเพิ่ม Website ตัวเองเข้าไป จะได้มาที่ GitHub นี้ถูก

Currently, a lot of people, when linking to this webring from their own sites are adhering to this pattern:

https://somewebsite.com#somewebsite.com

Right now, for all sites that link to here using such patterns, the inbound handling will, instead of highlighting only the website specified after the hash value, also call the next() function and highlights the one after instead.

Examples using random websites from webring:

https://webring.wonderful.software#warat.win
https://webring.wonderful.software#llun.me
https://webring.wonderful.software#suam.wtf

Pick any from the example above and you will see that webring calls the next() function after half a second (you can also see that the next button is clicked), which is exactly what is written in your code ( index.js line 164 )

if (inbound) {
          setTimeout(() => {
            next()
            autoNext.value = true
          }, 500)
        }

However, these (with slashes) are fine:

https://webring.wonderful.software/#/warat.win
https://webring.wonderful.software/#/llun.me
https://webring.wonderful.software/#/suam.wtf

The current implementation of hash handling inserts a slash in between the hash and its value. In such cases, matchLink would always be true, because the id provided is correct, it's just that the pattern is different. Within the same loop, you return true ( index.js line 104)

if (hash.startsWith("#") && !hash.startsWith("#/")) {
          const id = (
            (hash.match(/[a-z0-9\.-]+/i) || [])[0] || ""
          ).toLowerCase()
          location.replace("#/" + id)
          const matchedLink = links.find((l) => l.id === id)
          if (matchedLink) {
            sendBeacon("inbound", matchedLink.id)
            transitionInfo.needsInboundTransition = true
            inboundReferrer = matchedLink.id
            return true
          }
        }
      }

"true" would later be used in the if (inbound) line ( index.js line 157 )

Vue.onMounted(() => {
        const inbound = processInboundLink()
        updateCurrentLink()
        if (!currentLink.value && location.hash !== "#/list") {
          autoRandom.value = true
          random()
        }
        if (inbound) {
          setTimeout(() => {
            next()
            autoNext.value = true
          }, 500)
        }

     // ...

So, the question is:

Do you really need to check for

hash.startsWith("#")

in the if condition in line 104? By removing it, the problem is solved immediately.

I believe this issue should be corrected asap as the pattern above is what is shown in the docs and as mentioned at the beginning, a lot of people are already using this pattern.

//From docs here: https://github.com/wonderfulsoftware/webring
<a href="https://webring.wonderful.software#YOUR.DOMAIN" title="วงแหวนเว็บ">
  <img
    alt="วงแหวนเว็บ"
    width="32"
    height="32"
    src="https://webring.wonderful.software/webring.black.svg"
  />
</a>

I'm not making a pull request because I'm not sure whether this is intentional or not. The docs could just be wrong, and in that case, a simple edit, telling the people to prepend and append the hash with slashes would suffice.

<a href="https://webring.wonderful.software/#/YOUR.DOMAIN" title="วงแหวนเว็บ">

//...

</a>

Note:Some case from mobile phone and pc
How to reproduce:
1.Click webring logo alt
2.webring showed and next button some how unexpectedly press after user enter page and preview didn't show same page as user enter from.

Background

Currently our E2E test is failing.

Check out Cypress dashboard here:
https://dashboard.cypress.io/projects/77zijk/runs/36/test-results/b340ebf6-f409-492d-86d6-847659c02473

Task

• Please fix the failed end-to-end tests.
• Your PR should change a test file that is failing and correct it.
• Please include a screenshot of a Cypress run to verify that the test is fixed.

Hacktoberfest

If you would like to work on this task, please write a comment stating your intent. We will then assign the issue to you. To ensure continuity, the issue will be unassigned after 3 days of inactivity — so please keep us updated.

Currently we have RSS feed support to encourage blogging. It might be useful to add 2 more sections…

📣 To webring members

If you have a “uses” or “brag” pages, please comment with the URL.

• The URL should reside on your domain. You can redirect to other domains like GitHub, Medium, Google Docs.
• If you build your own page, please include the “last updated” time on your webpage. Recommended markup: <time datetime="2011-11-18" class="dt-updated">2011-11-18</time>

Uses

The uses page encourages people to share their setup.

Examples from webring:

• https://garden.narze.live/Uses/
• https://heyfirst.co/uses

Brag

The brag document encourages people to share their accomplishments.

Examples from webring:

• (haven’t seen one yet)

<a href="https://webring.wonderful.software#veer66.wordpress.com" title="วงแหวนเว็บ">
  <img
    alt="วงแหวนเว็บ"
    width="32"
    height="32"
    src="https://webring.wonderful.software/webring.black.svg"
  />
</a>

ควรเอาแปะที่ไหนดีครับ

ระบบมีเมนูในแบบนี้ครับ เพื่อที่จะแปะ link ข้างบนควรเข้าเมนูไหนดีครับ ? หรือว่าแปะทุกครั้งที่โพสต์ ?

Relevant code is in automation/site-fetcher

https://github.com/wonderfulsoftware/webring-site-screenshots/blob/main/heyfirst.co_375w%402x.png

Hello! 👋

As part of occasional housekeeping, which includes tidying up the webring, I will be removing sites from the webring that no longer has a backlink. This has been scheduled to take place on 2022-12-12.

The following table lists the websites that are missing a backlink:

• If you are on this list and would like to continue your participation on the webring, please add a backlink by 2022-12-11. I will re-check the websites again by that time and thank you for your continued support.

• Otherwise, no action is required, and thank you for your participation on this webring project.

Regardless of whether you choose to continue participating or not, your participation helped us grow this webring by a lot, and I appreciated it very much!

Since we have almost half a hundred sites on the ring right now (and I've checked all of them out)
It should be useful if there is some way to know that the site is recently updated.

How can this be done :

• RSS feed (but required action from each websites, not feasible)
• Check their git (Some aren't using git, not feasible)
• Scrape the page, and diff the image or text (I think this is the most possible way)