Hi everyone, it has been a long time since we posted any updates. I think it will be the last update for this year. So here we are with updates.
Before we move to important topics, let us share what we added.
Dev Updates
- Reading time estimation feature added
- Muting (updates and fixes)
- Account info page
- Some nav fixes
- Claim Box in notifications
- Some more fixes
Witness
After the witness changes, our rank was dropped, but still we are running it because we belive in the project. If things don't get back to how they should be, we might have to turn of as well, Just a last push by us.
About the Services
As you all know the updates are done by @tekraze only and were done for the other frontends as well.
He stopped supporting the dev work on latam because of some issues as well the live frontend.
Now we have lost both https://blurtlatam.com as well https://blurt.live, who were providing services like RPC, and Wallet as well. All the services are down because they couldn't get the support they expected from the community.
It's sad to see this when we have a big community and projects like these just dying.
But coming back to blurt.one, we still have all the services running. We also need your support.
As the price of blurt is down and we don't recommend selling, we are looking to alternatives.
So, if anyone wants to support us, they can manually add the beneficiary as @blurt.one
Ads for revenue
As we said the Blurt price is very low, we do not recommend selling. So, we are trying to look other ways, as we have servers with services running, those we need to pay.
Some will say, what we are getting supporting you. We only have this to say, that there are many issues happening at the main domain blurt.blog in recent times, and we have made sure unofficial frontends keep running to have the least downtime.
Now, some will say, if you can keep these running well, then why not the main domain?
It's because it's related to the servers as well as CDN. Those are different for each service, and we can not be sure at which time it will go down. We just make sure, at least we have one working server (in a different location)
So, we are trying to make ads run on our frontend.
We have applied for A-ads as well as Google Adsense
A-Ads
Unfortunately, we did not earn anything from this. It's way worse. Not even a dollar. But still, we are keeping them until we get approval from other sites.
Maybe we get lucky someday, who knows?
Google Ads
We have submitted our domain https://blurt.one to Google AdSense, and we are just waiting for approval from the team. We are not sure if they will approve or not, but we are trying.
We know, most of you people hate google and how they advertise. But still, we ask you all to support us by enabling ads, and clicking on an ad if it really works for you and shows something interesting.
Until the market is back, and we have other ways, it's the best we can do as of now. It's not bad, then selling blurt for pennies, We are sure you all will agree.
This time maybe, we can let web2 help web3, and when we are stable we can be free of that.
Thanks everyone, we hope you will support us.
Vote for witnesses
Official Wallet
Our wallet
https://wallet.blurt.one/~witnesses?highlight=blurt.one
Posted from https://blurt.one
Hope the new ads work better than A-Ads. I have turned off my ad blocker for Blurt.one.
Thanks, yes, these ads are better than A-ads
Best of luck with the project; I tend to bounce around between front ends to help with various other projects. I don't have an issue with using third-party advertising services to help generate some revenue. It's tough right now because of the state of the crypto market; I can understand the need.
Thanks for the support. We are currently testing with different ad networks, as for some reason Google ads are not working for us.