Streamlining Notifications for Bulk Image Uploads in Album Module

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.

  • 2630
  • More
Replies (8)
    • Hello @Romulus !

      I have re-checked the notifications of album upload and added the albums with 5 images within. So every subscriber has got only 1 notification about new album only. Only if the album's owner decide to add some images later, it will be counted separately.

      • Wich UNA version?your personal version? I just add an album, latest UNA version.

        • I didn't see any notification at the album level, only on each individual photo.

          • There is no possibility to make this granular setting in the studio regarding this issue.

            • Even if new photos are added to the album it should only be one notification, USER x added one or 10 photos to album y.

              • Problem solved 50% with help, Thanks!


                Resolving Upload Delays Related to ZFS Sync Settings

                When managing photo uploads, users may encounter delays or errors that can disrupt their experience. One common issue stems from the way the ZFS (Zettabyte File System) handles data synchronization, which can significantly impact upload performance. This article explores how adjusting the ZFS sync settings can resolve these upload-related errors.

                Understanding the Problem

                ZFS has a built-in synchronization mechanism that controls how data is written to disk. The default setting is sync=standard, which ensures data integrity by writing data to disk immediately. However, this can introduce latency, especially during bulk uploads, as each file must be fully written before the upload process can complete.

                Symptoms of the Issue:

                • Slow upload times when adding multiple photos to albums.
                • Delayed responses in the application during the upload process.
                • Possible notifications for each individual photo upload, causing notification overload.

                Adjusting ZFS Sync Settings

                To alleviate these issues, adjusting the ZFS sync setting for the relevant dataset can be beneficial. Setting sync=always ensures maximum data integrity but at the cost of performance. Conversely, setting it to sync=disabled allows for faster uploads, but it introduces a risk of data loss in the event of a crash.

                For optimal performance in scenarios where data integrity is not as critical , you can set sync to disabled or standard based on your use case. But in this case it may cause an error (such as during photo uploads where users can re-upload failed photos due to lack of synchronization) so the best option is 'always'. Here's how to do this:

                # Set sync to disabled for better performance during uploads
                zfs set sync=always rpool/USERDATA/user_dataset
                

                where 'user_dataset' is the folder that I want to make sure will be synchronized very quickly. You can have multiple datasets, For more information see the official documentation.https://docs.oracle.com/cd/E19253-01/819-5461/idx/index.html

                There remains the problem of updating albums by adding new photos, which adds notifications for each photo.

                To manage notifications effectively when adding new photos to albums, you can implement a centralized notification system that sends a single notification for the entire upload process rather than individual notifications for each photo. Here’s how you can approach this:

                1. Batch Processing for Uploads

                • Group Uploads: When a user uploads multiple photos at once, treat them as a single batch. You can modify the upload logic to queue the uploads and track the overall progress.

                2. Notification Logic

                • Single Notification: After all photos in the batch have been successfully uploaded, trigger a single notification indicating the total number of photos added.
                • Failure Handling: If there are any failures during the upload, you can still notify the user about the successful uploads and inform them of any issues with specific photos if necessary.

                3. User Interface Feedback

                • Progress Indicator: Consider implementing a progress bar or indicator that shows the overall upload status. This gives users feedback during the upload process without flooding them with notifications.
                • Completion Message: Once all uploads are complete, display a summary of the upload, including how many photos were successfully added.

                4. Backend Adjustments

                • If you’re using a backend service for uploads, ensure it supports batch processing and can handle the logic for grouping notifications before sending them to the frontend.

                By centralizing notifications for album updates, you can enhance the user experience by reducing clutter and providing clearer feedback on the success of photo uploads. This approach can help users stay informed without being overwhelmed by multiple notifications for each individual photo.

                • I have checked too we have people uploaded 100 at a time in to one album and only one notification, when the album is accessed again to upload more then 1 more notification, I have tested by dropping all pictures in from on folder all at once . I monitor my dedicated server all the time I can honestly say it's not creating any issues I have checked out bound mail and nothing to report that I would not expect. Simon

                  • Well this behavior occurs with zfs filesystem, if you follow my comments, I still don't fully understand why, probably every photo in the album is seen by UNA as an update, it's very strange.

                    Login or Join to comment.