Replies
- Keymaster(BuddyDev Team)Posts: 25260
Hi Alex,
Thank you for the reply.You have raised some real fair questions and concerns and I will address each of them.
1. Future of BuddyPress:-
Since 12.0, BuddyPress development has been going downhills. Fragmented eco-system, lack of developers(active), limited capability, old code base, these are the negatives. Unless the team decides to break away from their legacy/ecosystem, It is going to be really difficult to create positive experience with BuddyPress. BuddyPress was the first software for WordPress that allowed creating social network/community and that’s why it is still being used(the active installs have been falling sharply for last 5 years). Their architecture was good(modular)for that time but it has too many bottlenecks for the current era.BuddyBoss is affected by similar issues + Bulky code base. The good thing abut BuddyBoss is their User experience(UI/UX).
We wanted to avoid the past baggage. That provides us with huge advantage of building something from a new perspective and design the architecture as we see fit for today/future. It also helps us provide better user/developer experience.
We have been focused on low entry barrier/resistance and we hope to achieve that.
2. Why not fork BuddyPress:-
Forking will not help much as we will have the same issues that current BuddyPress/BuddyBoss suffers. Also, we will be stuck with the ecos system and create negative experience. Our goal is to create net positive experience for Site admins/Developers/Users and creating a new system from scratch is the best way to achieve it.3. What happen’s to our BuddyPress/BuddyBoss plugins:-
We will not develop any new plugins but we will keep updating and supporting all our plugins for atleast 3 years from now. After that, we will either put all code on github or let nanother developer/company acquire them.4. Will there be a way to migrate:-
Yes. We will be providing migration from BuddyPress, BuddyBoss a couple other plugins for migrating user/data.Many of the current features form our plugins/BuddyPress eco system are going to be in core. You may not need plugins. Search is part of core(still to be implemented). Most of the features from the current system will have better implementation available as art of core/extension.
It is not going to be a premium only plugin. After initial release and user feedback/updates, we plan to put the core on WordPeress.org and develop via github. It is a freemium model, not a paid only solution(Initial release is for paid users only).Regards
BrajeshPS:- Please open a new topic in future to keep the discussion focused on your actual query/concerns.
- Keymaster(BuddyDev Team)Posts: 25260
Hi George,
Tahnk you for the reply.I don’t think we have a competition here and we need to compare our goals with the project.
I understand your goal is to create a new experience and trust based network(what is trust? different people have different perspective on it and it is not the right forum to discuss it philosophically).We(BuddyDev) are not creating a social network, we are creating a software that allows site admins to create social network. What is that network and how it works is not our concern. We are not here to decide for site admins, our goal is to provide the tools and let the site admins decide what they want to do with it.
As of data ownership, unless your users are storing their data on their own systems, there is no real data ownership. The client server approach(where one or more servers store data) and not all users run their own server is not going to solve data ownership(Mastodon does allow users to run their own server, but users may be part of a server run by someone else too).
There are always going to be legal rules around world(Like EU/Australia’s current rules), and they are dynamic, they will change over time. Our goal is not to incorporate them into our software. Our goal is to enable site admins with tools to make the compliance simpler/easier. For that reason, our identity is not around these compliance, compliance is just one of the many things our system will provide easier tools/integrations.
As of your question:-
What is the architecture of this software
Client/server with partial inspiration from DDD.
Is your plan to use the existing user and security architecture of WordPress? I personally think that lack of granularity of access and trust levels meant BP was never scalable.
Yes, we are and we do not see any issue. WordPress provides granular role/capability based system which can be extended for all use cases. BuddyPress’s problem is not use of WordPress users, It is how they store/fetch data.
But also, WordPress is going to die soon. It’s moving commercial, this is why my ultimate goal is to have my mini servers hosted on peoples own PCs, and not need hosting, not from a hosting provider.
You are entitled to have your opinion. I have full faith in the future of WordPress and we are sticking with it. Also, you have all the rights to decide how you envision your software being used, for us, WordPress suits our requirement pretty well and we have full faith in the future potential of it.
To sum it up, we are creating a modern social network creation tool that will allow users(WordPress admins) to create social communities with various use case. Since our system is modular, It allows future extension without being limited by the current constraints. We are not re-inventing social networking(We believe the existing social networks like FB, X, LinkedIn, Reddit, Instagram etc.) is a good indicator of how a social network should work , we are rebuilding for a better experience and rapid development with WordPress.
Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi George,
Congratulations! The ideation looks fantastic(we are on different path). In our case, we believe site admins(who run the network) should have the control over what they want to do with user data and how much freedom/features they want to give to the users. It is not our job to decide that, our job is to empower site admins/community managers with the tools and let them decide.I wish you all the best and I am looking forward to a better future for community building with WordPress!
- Keymaster(BuddyDev Team)Posts: 25260
Hi George,
Welcome back.Thank you for opening the discussion and thank you for sharing about your network.
What I understand from your reply is:- You are building a federated system like Mastodon where users may run their own server(or may be you are storing it in browser if they don’t need server) and uses heavy encryption.
Our Project Midnight Sun(codename), is not a federated social network system. It is more like how the popular social networks like Facebook/Twitter(X)/Linkedn etc. deal with user and data.
You can think of it as modern software for building community with WordPress. Our main focus has been developer productivity and site admin’s flexibility. We have architected the system in a way to scale. I have been personally working on it for more than a year now, have built custom ORM, form builder, background system and a lot more as the infrastructure layer. Anything that you can do with current available systems, you can do it in 1/10th time if you are a developer.
The project is in heavy development state(I have the infrastructure layer ready, routing, navigations, core API’s working.) I am working on modules and UI and my expectation is to go live in next 20 days. The current system is not something that we can show you as UI is a work in progress. For now, You may need to wait until 20th for the first demo/availability of the software.
PS:- I understand that different us cases have different requirement for data processing. We are more like traditional community in the sense. We are not anonomyzing data at user level but it can be made so at display level as anonymous/incognito is a built in feature for all kind of data.
Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi Avi,
Thank you for the reply.Please Dashboard->Moderation tools->Settings->General and look for “Hide reported content from poster”. Make sure, It is set to “No”. Once you have done it, the post won’t be hidden from the author.
Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi Chris,
Thank you for purchasing the plugin.The default behaviour is to list core tabs only. We can extend it to support custom tabs easily(we did not support earlier as visibility/availability of a tab can cause 404 for groups). Are you using BuddyPress or BuddyBoss platform?
please let me know and I will assist.
Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi Avi,
Thank you for the question.You can check that by calling
bpmts_is_item_hidden( $activity_id, 'bp_activity' )pass the actual activity id.Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi,
Thank you for your patience.
We have issued the refund as requested. Please check your PayPal account for the same.Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi Tosin,
Thank you for the reply.I will share the updated code by Tuesday.
Regards
Brajesh - Keymaster(BuddyDev Team)Posts: 25260
Hi Alex,
Thank you.1. Thank you. I am looking forward to your feedback.
2. The problem is we need to filter members loop(bp_after_has_members_parse_args) and need context. Nouveau lacks the ability to allow passing additional information with their loading/paging.Since there is no active development for BuddyPress currently, It is not feasible to have it fixed upstream.
Regards
Brajesh
