Finallly.................. 😴

1. Witness Details

So finally I reached a new mark today. As I was only able to go up to 9th position from where I dropped to around 12th and 14th position. But now with communities support, I have reached the 7th position as a witness.

I have never asked anyone for witness votes in person (except some 1-2 persons) but I am thankful to all of you. Your support is why I am here today at this blurt and doing things
I will keep fixing things on blurt

2. Blurt.one Frontend announcements

So, to keep up with alternate frontend enhancements a dedicated witness and account was created that would only post updates about blurt. one
Check the post here

https://blurt.one/blurtindia/@blurt.one/blurt-one-frontend-and-witness-announcement
https://blurt.live/blurtindia/@blurt.one/blurt-one-frontend-and-witness-announcement
https://blurtlatam.com/blurtindia/@blurt.one/blurt-one-frontend-and-witness-announcement

I will also post updates related to blurtlatam.com and blurt.live there as I am the one managing all alternative frontends.

3. Curation with #techclub

So, after a long time and have a nice team. I now have started curation for the tech club and you may already have noticed that. We will share some articles, curation reports, and also maybe contests.
Do support with your delegations and votes.

4. Keychain Temporary Fix

Currently, the majority of users are using Whalevault Keychain which allows people to do transactions on blurt.blog without entering passwords.
Currently the RPC linked is the official one https://rpc.blurt.world

So, when the RPCs goes down, you may notice an error like sever_disconnected
This error comes, when RPC does not respond and voting may not work.

So, you need to use direct login to do voting operations.

A temporary fix

For now only, I have tweaked the whalevault to allow people to use different RPCs with blurtlatam and blurtlive.

Below are the links to the keychains

The version using Blurtlatam.com RPC

https://github.com/balvinder294/blurt-whale-wault/releases/tag/blurtlatam

The version using Blurt.live RPC

https://github.com/balvinder294/blurt-whale-wault/releases/tag/blurtlive2

How to use

1. Download Source code either zip or tar

2. Extract to any folder

3. Go to chrome > dot menu > extensions

4. Enable developer mode from the toggle in the right corner

5. Click on load unpacked in the left corner and select the extracted folder for the keychain

6. Now the wallet will be loaded.

Add your keys normally, as you would add for normal whalevault.

Note: This is just a hack and not a permanent fix. Only use if you like, you are not forced to use this.

5. My Dev updates and some Questions answered

Since I have joined, I have been working more here than my own company only so that people can enjoy blurt freely without any issues. But look like not all are happy with this, that's fine. I am going back to work more in my company than here.

But I am not leaving, not now and not later. Because blurt is now like a family to me. We all can take breaks but not permanently break bonds.

Also, there were some questions that I thought would be better if answered here

Questions anwered

1. Blurt.blog was down when my Blurt.one was up

So, the official frontend is used by thousands of users (and more not tracked by google) whereas my frontend-only have traffic of merely 50 users a day.
No bots, platforms, exchanges are using my RPC but official RPC.
Official RPC lately has increased load because of user outbreak + tools and exchanges.
Plus there is one unidentified operation happening, provably from some developer, which is causing the RPC to crash, which we are still trying to isolate by encouraging DApps to run their own RPC

2. If I am still working with the foundation or not

Basically, first of all, I never asked for a position in the team, but I was given because of my dev work and community support. I still say I don't care if I stay in the foundation or not. I will still be doing what I am currently, the same in the future as well.
Also, I don't care what some users say to me or have issues, I am here because megadrive asked me and not the ones complaining.

Also, the frontend support I am providing to other frontends is without any conditions and with my own will, I have no obligation towards them, but only to the foundation. So I can stop supporting them any time

Also there is no money being earned by other frontends. As some users may have doubts about that. It is just a service to you all, and not a right that you can ask for.

So, the question is obviously work with the foundation, but as it's a team plus official frontend is used by all. I have some limitations that I can do here, but not in alternate frontends. So, I may be seen doing more work there, but in the end, all important fixes as well features, are added to the official blog too. There is just a benefit of testing on alternate frontends, without breaking the official frontend.

3. No communications on chain

Some users have a complaint that there is no proper communication. So, whatever I do I post all the updates here. But sometimes, there are very small fixes that need not be added to a blog and pinned. So I only try to post important updates here.

Note: I can do post all updates, whether a small change and pin, then earn a lot from votes. But again, some users may have issues with me pinning all the time, so I will not do that. Just important updates, I will do.

4. Witness Votes to each other witnesses

Oh yeah, the important points, the witness votes from one witness to another witness. It is not a necessity that one witness should vote all 30 witnesses, and not a necessity that he retains their votes forever.
Witnesses are like political bodies, and votes are a way to keep a check on them.
So votes can be given as well taken. And if you are a witness don't worry. These just keep on happening, and if you are voted and unvoted often, be happy to know that people are active and carefully monitoring their witnesses.

5. If you vote a witness, you should get votes on posts

Every day new users come on board, and because of that, we may interact with many users. But at a point, it's not possible to vote for all the people who voted for one's witness.
So, please don't just vote a witness, if you expect him to follow you back or give you big votes.
You may get sometimes votes though but not all the time.

Make sure to check before voting a witness

• If you like his contributions to blurt
• If He posts nice publications and helps people
• If he supports the community

Just an idea of how to do it.

6. Why not discuss everything with the community

As I said before, the frontend even the blurt.blog is a service by the foundation to the community. So, we may not discuss everything, as it does not make sense. This includes the frontend work only, not like the chain.

If something is related to the working of chain, then we will surely discuss

But if anything we do that affects the chain, then we will surely discuss it before implementing anything.

7. Devs work is not easy

Everyone here thinks like devs do some kind of magic, but we are still the humans as you do with some additional knowledge.
So, if anything breaks, do have patience before crying and complaining.
We do not break anything intentionally, it happens automatically and sometimes we do not have control over it.

We all devs are part-time here and working with our wills and not forced by anyone. We do have our full-time jobs, but we still get some time to work on the blurt to make it better.

You may not know, how many nights saboin, eastmael have to work, to just be on time so users can do use blurt without any errors. I am just new in comparison to them yet. So, I will not say anything for me

Please, just show some respect for your devs. They deserve that.

---

I hope I have covered everyone's questions. If still, anyone have a question, they can ask me in the comments.

Well, it's already late night here and 2:26AM for me. So everyone good night.

---

😎Thanks all. this is, for now, see you soon🤬

---

@tekraze Witness Projects

---

Blurt Alternative Frontend - https://blurt.one
Blurt Wallet Alternative Frontend - https://wallet.blurt.one
Blurt RPC - https://rpc.blurt.one
Blurt witness Node - @tekraze
Blurt.one Witness Node @blurt.one
Techclub curation - @techclub
Blurt Dapps page
Blurt Recovery tool - https://recovery.blurtwallet.com
Blurtlatam Frontend - https://blurtlatam.com
Blurtlive Frontend - https://blurt.live
Serey Witness - Announcement
Digchain Validator - Validator Explorer Link

---

​You can support me by giving a vote to my Blurt Witness as I am doing dev work, Hosting an RPC, and now frontend.
If you really want me to be here on this platform, only your witness vote can help me, so feel free to do this by clicking on the below link

Witness Voting Link

---

Follow me on my social networks

---

Tekraze Blog
Instagram Personal
Instagram Blog account
Instagram Gaming Account
Youtube Gaming
DTube
Tekraze on Medium
Dehazelabs on Medium
Dev.to
Hashnode
Noise
Hive
Steemit
Serey

---

_{Posted from https://blurt.one}