Well, my user trust levels allow for 30 different levels of user access. New Admin, for example, start as trainees, at admin level 1, and they progress, based on the agreement of the super-admin/site owner, through five levels of trust, until they can manage everything, should the site admin wish. In addition, the site admin gets to choose which features become manageable, at each level of trust. They have complete control over every nuance of responsibility that they hand over.

In addition, users have 25 levels of trust, and the site admin gets to control everything, from the WordPress side of things, all data stored on their WordPress site, all links, cats, posts, and any other feature they choose to apply a trust setting to, will control exactly what level of knowledge, paid access, whatever, they just get a finer level of granularity to that access control.

AnonNet, however, is a social network, not a user network, not a commercially driven, biases and controlling network. And there, the owner of the data, is the person that owns it, the user. AnonNet is the back-end network to relax and spend time with friends. It also avoids me having to collect proof of age for every site that I run, simply because some content could be classified as too complex for a younger person to understand.

But also, AnonNet, by its architecture, moves like the wind – servers relocating themselves the minute they think they are under attack.

I was wondering what your architecture is going to look like? I mean, as far as I can see, there is no information on it at all. AnonNet may be able to use it. You see, as I said, AnonNet is a back-end, social, gaming and learning network. It is not public, as such, all users have to earn their trust, it can’t be paid for, and that is why it cannot be commercial, in any way. But, you can have your own AnonNet, and you can use it exactly how you like, anyone can. But if it becomes a commercial, then the linkage with the core anonNet would be reduced, directory listings, too, are based on trust. Anyone that walks in the room looking for sales, is not authentic, and is not going to play nice in our network.

The great thing about trust based systems, is that you get to trust your users, and can do things like automatically reduced levels of trust for a user who gets blocked by too many users with a set trust level.

I’ve completed the user trust level manager, It’s actually working on a live site, but only in the background. Part of its functionality is assigning trust levels to bots, and part of that, is that bots also get assigned trust levels, and the less we trust them, the less of our site they get to see.

You see, what I’m interested in, is the idea of having deep conversations online again. Facebook has killed that.

Imagine you had a WordPress site, with a shop or other commercial content. You might be selling training, or anything. You may well have buddypress as part of that, but that social network is a sales grift network, it is not about relaxing and letting your hair down. Where do you go if you want to chat to friends? Do you want all that personal chat recorded and tracked? Shipped off to a third party site for “processing”? Why do you want to know what your users are talking about? I don’t, personally, and I find their personal data to be an issue if I am the one holding it. These privacy laws are designed to kick all of the small sites out of the net, by forcing them to collect identity info.

I’m designing a system that avoids all of that. An open, free system that works side by side with WordPress and any public social network that they may have, and it’s systems and services, could benefit from the resilience and security features that I’m developing. A server with minimal data, can move like the wind, it may run in just a handful of megabytes, but yes, not your bloats WordPress installation, that is far too large to be agile, and that is the point – I’m decoupling the data from the access and control mechanism. The login server is the agile, no user data AnonNet polling server, whose location changes every day, and only you have the history, encoded in shared keys, to prove that you are that person, with that earned trust, on our, or your network.

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.

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. They will be able to make backup agreements with admins that they trust. They would be friends that they met in the network, and had gained a very high level of personal trust with them. That is a trust that working with AnonNet, with its systems, policies and training, is always going to be far higher.

That is a bit of the vision. Better than Crypto network levels of security and resilience, that to a trust model that does not take cash as any sign of trustworthiness. Most of the action is outside of WP, it’s a solution that will ultimately integrate onto any platform, and sit there, side by side, ensuring a coherent application of a much more secure and resilience, yet highly flexible network data sharing architecture.

• This reply was modified 1 week, 5 days ago by Venutius.

I had a full day programming yesterday and made great steps forward in terms of bug fixes and better overall integration and automation. I completed my standalone function to print those extra mmp photo fields, which means the next step is to hook into the uploader shortcode and other photo edit locations those fields.

The first thing I need to do is change the file picker aspect of the uploader shortcode so that only a single file is pickable.

Yes, I’m now fully into v2.0. It seems pretty much rock solid. That issue I had with local storage and the settings page. I’m now pretty sure it was another plugin knocking out my local storage that was the issue. I think it was misbehaving, and completely filling up my local storage, and that sent JS overall into a tailspin. The problem with that error, was I could deactivate the plugin in a group, the problem would go away, but did not come back as soon as the plugin was reactivated, so very difficult to track down.

But yes, this part of the orchestration is about to get a good test, I think. And once I have completed my work on photo galleries, I then want to look at video galleries. I’m planning to write an automatic GDPR compliance plugin for MediaPress. I have just done the same with a youtube plugin, and personally cannot launch video galleries without it.

Things are going very well, Brajesh 🙂 I’ve found almost all of my typos and incorrect assumptions. Lightbox and overloads are now stable.

There is still an issue regarding what happens when you click on the image when viewing it in the lightbox. Currently, this seems to fail to find any template, and falls out to a wordpress last ditch attempt to provide a template for the image. I can manipulate this by changing the code in the wordpress file directly, so I have a temporary fix in place. I think it may well be that I’m not giving the shortcode all the info it needs. The lightbox view is all I need, though, so it’s not a high priority. Having said that, I’m now going to check the shortcode docs.

I can over-ride the lightbox/photo.php

However, it seems that the default photo.php is not being loaded. the image that appears does not have the mpp classes.

This is where we started, but I’m pleased to have the lightbox up and working. Is there any way I can zoom that image?