Could you share details or screenshots of error, please?

Are you talking about mobile app or Ecency.com website? We can take a look and improve but we need to know where you are experiencing issue, it would help us narrow down the source of problem and fix it.

Are you using latest version? Could you share your device details and android version? We will work on a fix asap

Thanks for reporting/mentioning, we will investigate

Exactly

Yes

Yes, that’s the goal and done already

Promoting content with points always was ok, boosting content with votes were controversial one which is discontinued now. As for delegation, you get 100% back your potential curation reward in liquid

I appreciate the constructive tone. We are comfortable sharing the high-level cost structure and we already publish broader transparency information at also we have page, not all services/servers there

Fair pushback. Costs are choices, and we are not rejecting cost reduction. Thanks for actual suggestions! But the "just move to R2/object storage/CDN" assumption is not automatically cheaper

Thank you for the support. These are difficult tradeoffs, but we think it is better to be transparent now and adjust responsibly.

Agree. Open source does not mean "never make revenue" and depending only on DAO funding forever is not healthy. We already have some revenue from paid onboarding and Points sales, but it is still

We do not disagree with the risk you are pointing at. Reducing to 250 HBD/day is not a full solution. It is a first adjustment toward the current market reality. If liquidity and support keep weakening,

That criticism is fair, and this discussion is exactly why we reduced the proposal direction. The short version: Ecency will keep prioritizing critical infrastructure and open-source maintenance, but with

Thanks for writing this, Igor. Hard read, but fair discussion to have, still catching up with all conversation... We agree with the core point: DHF is not "free money." Every proposal has to

Strictness I was referring to, relates to events where many people might be sharing same IP (WiFi) and since we have 1 signup per IP, it might cause issues.

If you are doing event where new people will be joining lets us know we can create event specific referrals so it won’t have strict checks like we do right now, more smoother experience.

Do let us know your findings, we can learn and improve if there are any gaps or issues during that process 👍

On same side, points about ease of onboarding and less mention of complications of key management is part of our strategy. You can see on our onboarding, you signup get your password and login with it.

Thanks to your feedback, we added explainer to Decks and only showing it to power/logged in users, for non login users we are showing communities. Reworked navigation of main feeds and improved page speed