Criticism of the UNA development team. Addressing Excessive Notifications and Emails

Users with email and push notifications enabled are often overwhelmed by alerts. For example, if a user uploads an album of 50 photos and has 1,000 subscribers, the platform would need to generate 50,000 on-site notifications, 50,000 push notifications, and 50,000 emails—clearly excessive. Now, imagine the numbers for 10,000, 100,000, or even 1,000,000 subscribers. If a subscriber follows 1,000 friends and each friend posts an album of 10 photos, how many notifications will that user receive daily?

UNA profits from selling cloud services, so they may not prioritize optimizing this. They will collect their fees from entrepreneurs. But if you’re planning to use the UNA script to build a community, think carefully about these implications.

1. Do you realize the costs involved?
2. Is this really worth it?
3. How many users will you lose?
4. How many people will you frustrate?
5. What’s the point?
6. Who benefits from this overload? This is very clear, UNA Cloud services!
7. Your website will definitely be banned by any email provider.

Is anyone on the UNA team thinking about this? It appears NOT. Or maybe YES, maybe they did this for more profit. I don't know if they really don't care, or maybe they don't realize the implications, or maybe they did it on purpose. Instead of focusing on simply packaging a product to sell, UNA needs to address the potential risks here. With a billion users, where is this notification model headed? Without careful planning, the volume of notifications would eventually become unsustainable, leading to skyrocketing operational costs and risking platform viability.

Enhancing User Experience with Album-Level Alerts

To improve user experience, especially during large batch uploads, sending a single notification for the entire album rather than individual notifications for each image is far more practical. This issue commonly arises when multiple images are uploaded at once, resulting in an overload of notifications that clutters user feeds.

Recommended Solution: Batch Notifications at the Album Level

The best approach is to implement a notification that summarizes the entire upload. For instance, a single alert could state, “User X uploaded 50 photos to [Album Name],” giving a concise overview without overwhelming the user. This approach offers several advantages:

• Clarity: Users can immediately understand that an album has been updated with multiple pictures, instead of having to sift through hundreds of individual alerts.
• Less Intrusive: A single summary notification reduces notification fatigue, improving the user experience.
• Better Engagement: Users are more likely to engage with an album update when they perceive it as a collective event rather than an endless stream of uploads.

Implementation Options

Consider the following strategies:

1. Batching Notifications: Consolidate notifications at the backend. Once an album upload is complete, the system sends a single, consolidated notification.
2. Frequency Controls: Allow users to toggle notification settings for individual or batch updates, for users who want more granular notifications.

In summary, album-level notifications for large uploads not only reduce the number of notifications and emails but also provide an efficient, streamlined approach that enhances usability and engagement.

Scalability Concerns for Future Growth

If anyone plans to make money with this platform, take a moment to do the financial math. You’ll see that this script is poorly designed and simply burns through money without delivering sustainable value. It appears that the UNA team has learned nothing from Dolphin’s challenges. So, entrepreneurs, take note—UNA is nothing more than a money pit. Investing in this script could lead to nothing but bankruptcy.

The moral of this discussion is that building a successful community requires a focus on user experience and sustainability. While platforms like UNA may offer interesting services, excessive notifications can overwhelm users, increase operational costs, and ultimately harm community engagement. Entrepreneurs should critically assess the implications of their choices and prioritize effective communication strategies, such as batching notifications, to ensure the long-term viability of their platforms. Ignoring these factors could lead to frustration among users and potential financial failure. In essence, thoughtful planning and user-centric design are key to fostering a thriving online community.

Personal thoughts about Boonex.

Would I do business with this script? Yes, I would only sell cloud services to those who aspire to have a social network. There are plenty of dreamers in this world. However, I’m fully aware of how poorly designed it is, so I wouldn’t use it for business purposes. For now, I’m just experimenting and testing it personally to explore its limitations and potential.

• If the UNA team doesn't prioritize building a viable script instead of merely selling cloud services, this script will never evolve. It will only drain people's wallets and frustrate many users. If UNA continues down this path, I genuinely believe it’s evident that this script has no future.
• I haven’t seen any positive changes since the UNA team took over Dolphin. Dolphin support has stopped. The migration script doesn’t work from Dolphin to UNA and many years have already passed ,and UNA is a poorly functioning platform and all modules have become poorer in functions.. It’s like a car that consumes 100 liters per 100 kilometers, creaking at every joint and making noise for no reason and lose parts while driving it on the road.. So where is the evolution?
• If UNA decides to change its name tomorrow and subsequently abandons the UNA platform in favor of another rebranding, similar to what they did with DOLPHIN, all the investments made here will be in vain. Until I have the ability to migrate my sites from DOLPHIN to UNA, I find it difficult to justify further investment in UNA. In my last test, I managed to migrate only users and articles, photos, videos, avatars, and other content are still not migrating.

I have invested over 30,000 euros in the development of my DOLPHIN sites, only to discover that there is now no support available for them. I have purchased licenses and modules without any return, and my expenditures on advertising and time have ultimately been in vain. Given the current chaos surrounding notifications, I find myself quite frustrated; I would much rather enjoy a cup of coffee and watch a good movie.

Does anyone have or know a solution to change the system defauly cover color from native blue to a different color? As seen in attached picture..

The default blue still shows when I change cover, which is ok if I can change the color to my sites design color

I changed it, i think because of that http://busimatch.club is not working as it should.

What is the original _header.html?

<!DOCTYPE html>

<html lang="en">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0" />

<title></title> <base href="" />

<bx_include_css_styles />

<bx_include_css_system />

<bx_include_css />

<bx_include_js_system />

<bx_include_js />

<bx_include_auto:_header_js.html />

<bx_include_auto:_header_js_spinner.html />

<bx_include_auto:_header_js_toolbar.html />

<bx_include_auto:_header_js_custom.html />

</head>

<body class="bx-artificer bx-page-timeline-view bx-def-font bx-def-color-bg-page bx-def-image-bg-page <bx_injection:injection_body_class />" dir="LTR">

<noscript>

<div class="p-4 rounded-sm text-center text-red-600 bg-yellow-500 bg-opacity-50">

__system_js_required__

</div>

</noscript>

</body>

Sorry but: Can someone with skills take my site over... I see everywhere Page was not found now.

I even don't know what i did to become here... Yesterday it worked. I just wanted to add the interchat bot.

I hate it when i have problems like this. here a video to explain.

I chose UNO based on the highly useful modules, whose descriptions I spent all night reading. It all truly looks very promising. I shared the project with partners in three countries, and they expressed hope in the potential to launch projects in multiple countries if I can guarantee what I’ve presented to them.

Waking up one morning to realize that your project, plans, and business have died because one of the crucial project modules is incompatible with a new UNO version or has suddenly stopped receiving updates—that’s not an appealing prospect. Not knowing the license type could also become a critical issue. And this information is not publicly available except for what the dedicated UNO team provides.

Indicating the version of a non-PRO module is good, but for an entrepreneur planning to use a module in their project, it’s essential to know whether this module will be compatible, at least with the next core version of UNO. At the very least, with the next version.

I suggest including this information in the module description, along with the license type (MIT or other) and cost type—one-time or monthly. These are the minimally sufficient details that allow everyone to decide and plan whether to use this module in their project. Seeing the developers' LinkedIn profiles would also inspire much more confidence and encourage purchase and recommendation.

Let’s discuss this. At a minimum, leave a '+' or '-' in the comments if this is important to you or means nothing.

Thank you very much, dear developers. You have truly created and continue to develop an outstanding product. Both the core team and the independent solopreneurs and teams who invest their time and expertise. Creating a great product requires a lot of dedication, and even more so to maintain it.

It takes a lot of time and multiple attempts to find the PRO modules. I suggest placing them in a separate category.

What do you think? Is that possible?

I recently upgraded the mariadb engine to InnoDb as recommended. The strange thing is that suddenly the sys_storage_tokens table has increased to 3gb. Is there a way to empty this table?

Thx

Logo, footer, Web site fonts. How to change it in Spacenook?