Hdev Core (@HdevCore) header
Hdev Core (@HdevCore) profile picture

Building core Hive functionality, tools & apps β€” and onboarding the next wave on-chain. Open-source. Community-driven. #Hive

hivesphere
Joined July 2026
Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)Photo by Hdev Core (@HdevCore)
We're changing how the HivePulse SEO Contest pays, starting with the round that opens today. Under 5 entrants: nobody is paid and the pool rolls into the next round. Here's why we're doing that to ourselves. 🧡
1
2
3
143
And week 14, where we got it wrong ourselves: πŸ₯‡ @itx.wardah πŸ₯ˆ @ahmedabbaci πŸ₯‰ @nursejoe Our judge rounded 99.5 up to 100, invented a tie, and handed 3rd to the wrong person. We fixed it β€” then sent @nabbas_0786 the 50 HIVE anyway πŸ‘‡ actifit.io/hive-177727/@hdev… #hivepulse #hive
7
Second change: ties now SPLIT the prize. Two tied for 1st get 125 each. Four tied get 75 each. For four rounds the podium has been decided by who published first β€” rewarding rushing, punishing revising, in a contest about revising. That race is over.
1
3
So the pool now moves in both directions. 5 entrants β†’ 300 HIVE 10 β†’ 400 15 β†’ 500 20 β†’ 600 Under 5 β†’ nothing paid, and it all rolls into next week. Three of our last four rounds would have paid zero. Doing it anyway.
1
3
In the last four rounds this contest gained ONE new entrant. Weeks 11, 12 and 13 brought in nobody at all. The same five people keep writing excellent posts and splitting the same 300 HIVE. That isn't growth, it's a standing order.
1
4
Week 14 is open, and the pool grows with the field. 300 HIVE under 10 entrants. 400 at ten. 500 at twenty. The hard bar is reachable β€” two people just proved it. Closes 3 Nov, 12:00 UTC. Tag #hivepulse.
11
3rd place missed a perfect score by six words. Concrete detail is a RATIO β€” named people, places, dates, numbers over total words. 2,234 words. 0.0725. Full marks starts at 0.075. Six more names and it's 200/200 πŸ‘‡ actifit.io/@hdev/hivepulse-s…
1
11
πŸ₯‡ @ahmedabbaci β€” 100/100 πŸ₯ˆ @nursejoe β€” 100/100 πŸ₯‰ @nabbas_0786 β€” 100/96 Two question headings. Three definitions. Five sourced figures.
1
15
Week 13 of the HivePulse SEO Contest is settled. Two writers maxed every GEO check we have β€” including the harder bands nobody had cleared before. We said perfect scores should be rare now. They earned them. 🧡
2
1
1
37
πŸ₯‡ @ahmedabbaci β€” 100/100 πŸ₯ˆ @nabbas_0786 β€” 100/100 πŸ₯‰ @DrWardahx β€” 100/100 Reading ease knocked 3rd off the top: 61 vs 60. The other two tied on that too β€” so publication time split them. 13:48 vs 14:43.
1
18
Week 12 of the HivePulse SEO Contest is settled. Every single entry scored a perfect 100. Nobody dropped a point anywhere. So the podium came down to 55 minutes. 350 HIVE went out. 🧡
1
1
1
55
Your GEO score will drop next week. The bar moved up β€” your writing did not get worse. 300 HIVE under 10 entrants. 400 at ten. 500 at twenty. Closes 20 Oct, 12:00 UTC. Tag #hivepulse. #Hive #SEO
36
Week 12 changes the GEO score. 57% of every entry we have ever scored held a perfect GEO 100. A number most people max is not measuring anything. Same checks, higher bar. Perfect falls to about 9%. Details πŸ‘‡ actifit.io/hive-177727/@hdev…
1
29
πŸ₯‡ @nabbas_0786 β€” 100/100 πŸ₯ˆ @DrWardahx β€” 100/100 πŸ₯‰ @ahmedabbaci β€” 100/100 All three on reading ease 60 exactly. So the podium came down to who published first: 6 Oct, 7 Oct, 12 Oct.
1
1
21
Week 11 of the HivePulse SEO Contest is settled. Three entries tied on a perfect score. Then they tied again on the new tiebreak. Our new rule met its limit in its first week. 350 HIVE is going out. 🧡
1
2
1
78
300 HIVE under 10 entrants. 400 at ten. 500 at twenty. +25 for a referral, paid to both of you. 50 HIVE for the best quote-RT of tweet 1 β€” paste your link in your entry comment. Closes 13 Oct, 12:00 UTC. Tag #hivepulse. #Hive #SEO
10
Why this ends it: padding cannot move a ratio. Copy your post seven times β€” reading ease does not change at all. The only way up is to rewrite. Shorter sentences, plainer words. Week 11 is open πŸ‘‡ actifit.io/hive-177727/@hdev…
1
9
So from week 11: if you tie on score, the post closest to Reading Ease 60 wins. It is the number HivePulse has shown you all along β€” the Readability row, "Ease 68/100". 60 is the target, not the starting line.
1
1
8
Here is the problem with word count. Winning post, week 8: 1,730 words. Week 9: 3,217. Week 10: 7,569. We built a length competition by accident. Nobody set out to do that.
1
1
10