Mbin: A kbin fork that promises to never review PRs before merging them

Somebody who was previously active on the kbin codeberg repo has left that to make a fork of kbin called mbin.

repo: https://github.com/MbinOrg/mbin

In the readme it says:

Important: Mbin is focused on what the community wants, pull requests can be merged by any repo member. Discussions take place on Matrix then consensus has to be reached by the community. If approved by the community, no additional reviews are required on the PR. It's built entirely on trust.

As a person who hangs around in repos but isn't a developer that sounds totally insane. Couldn't someone easily slip malicious, or just bad, code in? Like you could just describe one cool feature but make a PR of something totally different. Obviously that could happen to any project at any time but my understanding of "code review" is to at least have some due diligence.

I don't think I would want to use any kind of software with a dev structure like this. Is it a normal way of doing stuff?

Is there something I'm missing that explains how this is not wildly irresponsible?

As for "consensus" every generation must read the classic The Tyranny of Stuctureless. Written about the feminist movement but its wisdom applies to all movements with libertarian (in the positive sense) tendencies. Those who do not are condemned to a life of drama, not liberation.

melroy,
@melroy@kbin.melroy.org avatar

Thanks for your feedback.

We do have code reviews in GitHub and discussions on Matrix. We updated the README that reflect our latest way of working. As stated in the comment section we are also working on it in PR: https://github.com/MbinOrg/mbin/pull/34. Feel free to comment on that.

TheAgeOfSuperboredom,

Sounds like it’ll be a disaster

TheOneCurly,

I agree, this is a wild reactionary shift to the issues they’ve seen with kbin. Unless the community “consensus” includes people actually reviewing and testing this is just going to put the repo admins in a tough situation when they have to merge in some broken commit the community voted on.

TheVillageGuy,

If the community were to do that, the community would have failed. Why would a sane community want to merge a broken commit? Or is that your interpretation of how Ernest's 'mistake' got merged? Mistakes happen, even when verified by a community. At least on our end it was an actual mistake and we're honest about whether it was or wasn't.

The great thing is that we can, as a community, learn from things like this. And we have. I'll leave it to your interpretation what we've learnt.

TheVillageGuy,

As a person who hangs around in repos but isn't a developer that sounds totally insane.

Why do you hang around there then? So you can write articles like this in an attempt to stir the shit? What is there to gain from that, for the fediverse?

I'd also like to know how you hang out there then, as I can't seem to find a person called Density hanging around? I might not be looking in the right place, of course

SamXavia,
@SamXavia@kbin.run avatar

I do love Mbin, I just wish we had an area instead of Matrix to talk about things that we want and stuff.

density,
density avatar

they don't use github issues?

SamXavia,
@SamXavia@kbin.run avatar

They do but it would be nice to have a place to talk about it in a Magazine instead of having to go to external sites

density,
density avatar

Can't make a magazine? https://kbin.run/newMagazine

SamXavia,
@SamXavia@kbin.run avatar

It's not that I can't make a magazine, it's just it won't be looked at or be used as an official one. So it would be worthless creating one

density,
density avatar

How do you know the future?

If you are correct, it is very strange. Why would people who are so passionate about creating a social media platform refuse to use it?

melroy,
@melroy@kbin.melroy.org avatar

That is correct, we do not have an "official" instance or an "official" magazine. What follows now is MY OWN opinion, other community members might think differently.

Mbin is aiming for a federated and decentralized social network, I think the whole point of the fediverse is that there shouldn't be one main instance, right? Feel free to create a magazine where ever you want! Isn't that the beauty of activitypub? Maybe the idea takes some getting used to.

density,
density avatar

here we all are talking about it on fediverse@kbin.social which certainly isn't Official Fediverse comm.

melroy,
@melroy@kbin.melroy.org avatar

kbin.social is the official instance of kbin ;)

density,
density avatar

Your community members ("I do love Mbin") are expressing that they are unhappy with the mediums available for discussion and feel excluded. What is done about it?

melroy,
@melroy@kbin.melroy.org avatar

I feel a bit of negativity from you. This will be my last reply in this thread. She has resolved it herself by creating a magazine by herself on Mbin for Mbin: https://kbin.run/m/Mdev

density,
density avatar

@melroy great!

@SamXavia

ripcord,
ripcord avatar

I'm still not getting the point of mbin. I mean, options are nice, but what's the value it brings over kbin?

SamXavia,
@SamXavia@kbin.run avatar

It brings updates faster, more community control as it's done via community wants / needs (so if there is an update to Kbin that people don't like it can be reversed) as well as you can give your feedback for possible features.

conorrr,

It brings updates faster

I just compared two repositories, and that's not true. Mbin is lacking the latest most important features.

control as it's done via community wants / needs

Who specifically? Because it seems to me that I've been seeing this on kbin recently.

density,
density avatar

It seems to me that when these devs say "community" they are talking about their own group. Not the userbase of threadiverse/kbin as a whole. Which, tbh, is what virtually anyone speaking on behalf of "the community" in any context, usually means. Unless there has been a literal vote in a highly engaged population. As we have no mechanism for this sort of process, nobody can be claiming to speak for "the community" in a legitimate way.

Hopefully they will eventually (if not already---this is an old thread) develop enough confidence to speak on their own behalf and own their opinions instead of attributing them to a sort of everyone. I think what they mean to say is along the lines of "This fork is the way we like it." Which like would be fine afaik.

cacheson,
cacheson avatar

It looks like they're still working out what they want their process to be:

https://github.com/MbinOrg/mbin/pull/34

Seems like your concern is addressed there:

Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).

The mbin fork happened when kbin development was looking a lot less active. In any case, it's not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.

density,
density avatar

I cant follow the convo to tell if this is the actual state of things or just something thst was being discussed but:

16 Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, (c) engaging with the Contributor on improving their patch quality.

What an idea.

cacheson,
cacheson avatar

From the PR comments:

Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, (c) engaging with the Contributor on improving their patch quality.

I asked around and asked in the C4 specification matrix room.
And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren't forever it's only a github/gitlab thing).

So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.

melroy,
@melroy@kbin.melroy.org avatar

So we have proof now ;P

radek,

It seems to automatically pull all changes from kbin anyway so I don't know about this consensus approach.

https://karab.in/m/karabin/p/340377/Usterka-z-crosspostami-nie-zawsze-sa-przyporzadkowane-odpowiedniemu-watkowi-matce-at-ernest

cacheson,
cacheson avatar

Hmm, that seems like not such a good look from Ernest. According to google translate:

I know, honestly it was on purpose. I noticed that forks sync changes immediately with /kbin. I wanted to check how they deal with this much-announced community-based qualitative code review. Answer: they can't cope. Quite an obvious bug was accepted in PR and domerged into the main branch :P It now works properly on the rifle ;)

Hopefully everyone can play nice and work together productively.

density,
density avatar

seems like you are saying ernest put thru an intentionally malicious PR to see what would happen? And what happened was exactly what is described? I mean, ya, thats what people will do.

ernest,
ernest avatar

It wasn't entirely intentional, it was actually my mistake. But I held off on pushing the hotfix for a while. It was a development branch, so these kinds of bugs were permissible - in this case, it just changed the order of related posts, nothing serious. It was quite easy to spot and fix. Slow and cautious acceptance of pull requests, something I spent a lot of time on, was the main accusation from the creators of forks. Hastily accepting them was a problem for me. I personally considered a consensus similar to that, but now I see it doesn't make sense. Someone needs to take responsibility. Personally, I believe that forks are the best thing that could have happened to the project.

melroy,
@melroy@kbin.melroy.org avatar

It is good to really see your true nature now. I'm also think the fork is the best thing that could have happened for the community. It's a pity that you never started a conversation, but instead you still try to do mean things like this.

melroy,
@melroy@kbin.melroy.org avatar

Ow.. it was 100% intentional. You said it yourself: "Wiem, szczerze mówiąc było to celowe. Zauważyłem, że forki synchronizują od razu zmiany z /kbin.". https://karab.in/m/karabin/p/340377/Usterka-z-crosspostami-nie-zawsze-sa-przyporzadkowane-odpowiedniemu-watkowi-matce-at-ernest#post-comment-510980

ernest,
ernest avatar

Yep, in Polish we call it skrót myślowy.

melroy,
@melroy@kbin.melroy.org avatar

występujący również pod nazwą Kontekst potoczny ;)

density,
density avatar

@melroy I don't think you can really be upset about anyone putting through bad code. According to the philosophy as I understand it, bad code (intentionally so or otherwise) is a useful contribution and you are basically soliciting it. You supposedly have some way other than code review to ensure nothing harmful gets through and it has to do with the reputation of the contributor. Since you already knew @ernest and clearly have a bad opinion of him, how did it happen?

I did not and could not review the PRs themselves. So I am just going on the information as presented here. Sounds like @ernest put through some code (either into kbin or mbin not clear on that) which he knew was not 100% highest quality but which error was not critical or devastating. And that it could easily be found and fixed. Partially he did this to learn more about this governance model. A model which has apparently been developed in direct opposition to his own. Is it approximately accurate?

If so, sounds a bit mischievous at the worst.

I really can't recommend Tyranny of Structurelessness highly enough.

melroy,
@melroy@kbin.melroy.org avatar

Well I don't have a bad opinion about him (those are your assumptions), we just didn't agree on how a community project would/can work.

If however he did introduce intentionally a bug in kbin, just because of Mbin that's downright childish. The Mbin community does try to test all the incoming PRs (not just kbin sync PRs) on various instances apart from unit-tests, etc. We just do not want to depend on a single maintainer, hence a different way of working in the project.

He saying Mbin can't handle the kbin changes that is just not true (Odpowiedź: nie radzą sobie), at least we try to keep in sync (eg. for API comparability for upcoming mobile clients). But I'll leave it this, I'm not going to waste any more energy. I hope you understand.

Thanks for your recommendation.

HeartyBeast,
HeartyBeast avatar

“True nature” in this case appears to be slow and cautious. Shocking stuff!

melroy,
@melroy@kbin.melroy.org avatar

No I think you misunderstood, in this particular case it was malicious. But it's fine, we are all over it now.

ernest,
ernest avatar

Oh c'mon, don't be mad. It's just a wrong sorting of posts, it's in an edge case, and seriously it wasn't intentional. I just wanted to check how such management looks in practice, how many merge accepts are needed, etc. I didn't mean to do anything wrong that could cause harm. I even push the same code to my instance to facilitate your tests ;)

But you're right - that's just my nature. I approach PR with very limited trust, whether they're mine or from others.

melroy,
@melroy@kbin.melroy.org avatar

I know your approach on PRs. Hence the main reason of the fork. The community does believe in their people and the good in mankind. Only 1 approval is required from another maintainer for now. We are using C4 way of working.

ernest,
ernest avatar

I assure you that I didn't intentionally push incorrect code into the repository. These were my first lines of code in a really long time. I simply got involved in other things that I wanted to finish first, and I noticed the edge case in the meantime, but it wasn't a priority. I saw that you were syncing and I was hoping to benefit a bit from it once you fixed it. I didn't expect the review to happen so quickly. By the way, I was genuinely curious about how this project management method works because, you know, I've always avoided such an approach. Merloy, you know how much I owe you, and I appreciate what you've done for the project, as well as the other Mbin contributors. Our overall visions haven't always been the same, and I think it's great that kbin has been forked. You see for yourself how my work looks until the release - there are many things I'll be refining over time. That's why I've put a hold on all other PRs, and now I want to focus on this.

BaldProphet,
BaldProphet avatar

@ernest @melroy
lol this whole conversation is a microcosm of the open source community. I agree with ernest that forks are great and would add that they show that the open source system is working as intended.

TheVillageGuy,

You are right. But was the whole debacle that lead to this fork being made worth it? Wouldn't it have been much better if Ernest had just sorted out all himself and we'd all be working on the same project together now instead of introducing mistakes into forks too see what happens? What a complete waste of time, especially under the current circumstances.

TheVillageGuy,

In hindsight maybe we should have responded by saying we merged your mistake intentionally to see how you'd respond.

i am not being serious of course, as that's not our community's nature. Even though it's allowed to gather proof, we (I am quite sure I can speak on behalf of the community here) would never intentionally introduce bad code into software which is being actively used.

Ernest, you have seen me before, pleading for you to change your ways, on all fronts. This, sadly, degrades the faith I have in your project being suitable for being used in production, from a pragmatic point of view. Kbin may be reliable, but you are not.

BaldProphet,
BaldProphet avatar

Ernest said he didn't introduce bad code on purpose:

I assure you that I didn't intentionally push incorrect code into the repository. These were my first lines of code in a really long time. I simply got involved in other things that I wanted to finish first, and I noticed the edge case in the meantime, but it wasn't a priority.

TheVillageGuy,

Ernest has said many things in the past and many times has not lived up to his promises. So I doubt this words now. Also he's already contradicted himself on this matter.

ernest,
ernest avatar

Yeah, that's true. Real-life stuff was kinda more important for me at the moment than managing the project.

For me, it's straightforward: I pushed some dev code that wasn't even a complete feature, and it got approved in your pull request. That's why I was advocating for everyone to only merged their own PRs in the /kbin repository – so that each person could take responsibility for their own work. I won't go on about this any further.

TheVillageGuy,

Real-life stuff was kinda more important for me at the moment than managing the project.

As it should be, always, for everybody, you won't ever hear me judge you on that, so please don't try to make me look bad by implicitly suggesting I am.

What you failed to do however is delegate, even temporarily, your responsibilities to people you trust. Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill. It seems keeping them on a leash was kinda more important to you than securing the future of kbin.

I won't go on about this any further.

I hope I'll never have to mention this again, so you'll never have to. Which would imply that you'll have come to terms and lived up to your promises, both recent ones and from the past.

HeartyBeast,
HeartyBeast avatar

What you failed to do however is delegate, even temporarily, your responsibilities to people you trust.

Possibly becausE - you kkkw, urgent real-life stuff got in the way

fr0g,

Instead you left people who trusted you dangling, only sporadically feeding them promises you would never fulfill.

Now, you see, this is the part that I as an uninvolved observer who's just now catching up on the happenings do not get. Promises that were never fullfilled?
How long has or hasn't this actually been an issue? Because from what I can see looking at the codeberg commits, it seems like development stalled for how long, like a month or so?

I totally get not wanting to be left hanging and having some answers and pathway for how contributions can happen. But as you also agree on, I also get real life being more important and getting in the way sometimes. And in that sense, being out of it for a month or so does not exactly seem like an earth-shattering amount, even if it's annoying when it happens to be the project lead and not much can happen.

I just can't help but feel like all of this has been pretty impatient and premature, which also makes it hard for me to really understand the point of the fork, even if I can relate to the basic rationale behind it. But then again, I have no knowledge of the direct going ons and communications between the contributors and the events that led to this. So there might be a lot I'm just not getting.

density,
density avatar

@fr0g I am in substantial agreement with you after reading all this back n forth.

ernest,
ernest avatar

Yes, I say this fully aware - there are many things that I have failed at. Much of what I said, I failed to achieve. However, I never wanted to keep people on a leash; I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.

Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn't visible from the outside. However, in that mental state, the last thing I wanted to do was resolve conflicts among adults, and it all started to boil down to that. As @BaldProphet mentioned - "microcosm of the open-source community."

Moreover, there were too many different visions of the project, ignoring requests, etc. That's precisely why I decided to temporarily halt development, to secure the future of kbin. It was my decision, and as I mentioned, forking turned out to be the best thing that could happen. As you can see, the differences are not that significant, but it will be easier for all of us - especially since we can always draw inspiration from each other, and I don't think anyone has a problem with that.

However, I still maintain contact with many people, and sometimes they mention to me the attitude of certain individuals on mbin's Matrix - it is at least puzzling. In any case, I want to stay away from that and focus on my work with contributors who understand and prefer my approach.

melroy,
@melroy@kbin.melroy.org avatar

Despite the fork. I hope we can learn from each other indeed. That will only benefit both of us.

Although we merge into main it's not a release, we use GitHub/Docker tags to mark releases. And use semantic versioning if needed for minor and patch releases.

TheVillageGuy, (edited )

Thank you for your in depth, genuine, reply

Believe me, I tried to delegate tasks, had many private conversations and discussions. Perhaps it wasn't visible from the outside

I am sorry but I'm having a hard time believing you when you say that you were seriously trying to delegate, as not a single soul ever said anything which would remotely confirm this. I believe you had conversations, but they ultimately didn't result in anything in this context.

However, in that mental state, the last thing I wanted to do was resolve conflicts among adults

I am not sure how to interpret this as there were no conflicts that I'm aware of that needed resolving during your absence, everybody was just waiting

I am more of a person who prefers to stay on the sidelines and engage in what brings me the greatest pleasure - coding, just like any other contributor.

There's nothing wrong with being like that, there are other people willing to do things like resolving issues. Like me. I realize I appeared out of nowhere. As a new instance owner it took a while for me to notice, but when the situation became clear to me I was ready to jump in and help, just like all the other people who had offered their help (before me).

You've basically just admitted that you were either incapable of or unwilling to engage in structural problem solving and management of the kbin project. That's fine, but you should have reached out and informed the community as soon as you became aware of this.

forking turned out to be the best thing that could happen

Yes, forking can have positive side effects and perhaps having two versions in development synchronously can merit more than one. This however was not the proper way to achieve this and using it as an excuse to justify your behavior and inaction is unjust.

However, it is not too late. You can still do the right thing by starting delegation now, by clearly assigning multiple people to all essential tasks, and giving multiple people complete control of kbin.social, so that, should a similar situation occur in the future, you and the community will confidently know that the project will not grind to a halt again.

Then seek a constructive dialog with the mbin community and we can make the project, in it's current for, work. Together.

If you feel uncomfortable with or are have trouble doing any of this, as you've clearly indicated you'd rather spend your time on coding, you are always welcome to ask me for advice.

Never hesitate to ask for help.

ernest,
ernest avatar

You see, I don't know how I would act now in hindsight. You have to take into consideration that, at the peak, hundreds of people willing to help appeared out of nowhere, people I didn't know at all. By nature, I am rather distrustful and approach new relationships cautiously - I really need a lot of time to get to know another person well. It's true that after some time, a certain structure began to take shape, but not everything is always as it seems at first glance - especially when so many strong personalities converge in one place. Perhaps it was a mistake that instead of addressing many things publicly, I tried to solve them in private conversations.

And you're right, anyone who knows me a bit knows that I have trouble asking for help. Sometimes, I take too much on myself, which is not good in the long run. I'm working on it. But this time was something more. I promised to take care of things, and under normal circumstances, it would probably be easy for me because I have some experience in resolving such situations. But these were not normal circumstances. I realized this too late. I was just overwhelmed by real life. So many problems collapsed on me that I could never have anticipated. These were the worst months of my entire life. I don't want to write too much about it or make excuses, but at some point, even getting out of bed or eating something became difficult. When I tried to get back to the project, the thought of the backlog and how many people I let down made me feel sick. That's why I'm really glad to be where I am now. I can only apologize to you and try to fix some mistakes. I need to do it at my own pace. I want to clean up the mess, find my rhythm, and then engage in broader communication with people. I'm still recovering on my own.

What I did was indeed a bit malicious, but I believe it was the only way to achieve the intended effect. The fact that I really like you all should not mean that I will be uncritical of your work. I don't want you to fully trust everything that comes from me - only in this way can we fully utilize the potential we have in developing the fediverse. Frontend errors are just a trivial matter; they can be quickly found and fixed. However, the situation is completely different when it comes to backend mechanics. Seemingly minor errors when I was developing karab.in made me undo them for weeks. With larger instances, there may not be a second chance. This is not a centralized system, you have to consider others above all. That's why I am so sensitive to it and have so many doubts about making changes.

It's not that I want to make things difficult for you. I really care about mbin developing in the right direction. I am curious about what the future will bring. I would like kbin to remain rather ascetic, subtle, and something that you need to learn and understand a bit, rather than having everything handed to you on a platter. Mbin can be a different face, with more features, bolder, and I know that you have many great ideas for it. A simple example is the labels for marking mods/admins/ops that you are currently working on - kbin has it marked in a subtle way with a faint left border outline - you can do it differently, and that's great. As someone very wise once said, "If it's not diverse, it's not the fediverse."

@melroy I am sure that this is just the beginning of our shared adventure. I hope you won't hold a grudge against me for long ;) Guys, I deeply regret that we met at this stage of my life, but as I say, all I can do is try to fix my mistakes. Thanks for everything!

density,
density avatar

deleted_by_author

    •
    density,
    density avatar

    OP here. I was intending for this thread to be about the mbin fork and its governance, not about kbin. But I guess I kinda got answers to my questions (in so much as they exist) and then some.

    I have no particular relationship/loyalty to ernest or to kbin. Like a lot of people, I just got here. I may or may not stick around.

    I myself am a person who tends to become intensely excited by new projects. I can come in with lots of ideas and energy feeling like I will be comitted for a long time. But can then loose interest just as quickly. (It's taken a lot of times around the block to learn that.) So I understand why a maintainer of an open source project would have reticence to bring me, or someone like me, into their project in a position of authority without enough time (months -> years) to prove the comitment and to demonstrate competance. In fact I would regard it as poor judgement to just accept a ton of input like that. Just accepting whoever is offering energy can really lead to a lot of problems. I've been on both sides of those problems!

    I started this thread to ask questions about mbin because I'd never seen an open source projects described like this. The mbin folks came in not really to provide answers to those questions, but to make insults on how they perceive ernest's personality and moral charecteristics. These based on vague but petty sounding grievances. None of these posts do much to reccomend the project to me. Sounds like waa waa waa babies. If the main grievance is they weren't allowed authority on kbin main, then I agree with that judgment based on the posts here.

    Hopefully everyone simmers down. Maybe mbin can define itself in a less reactionary way in the weeks and months to come.

    @radek @cacheson @TheVillageGuy @BaldProphet @melroy @ernest

    TheVillageGuy, (edited )
    TheVillageGuy avatar

    Well then. I don't know what happened here. I was asked about this situation so I linked here, to find, to my surprise, that my final comment is missing.

    This is a month ago now and I don't want to continue the thread, but also do not like my comments going missing. So here is my response to the above

    

I understand your response, if I would stumble across this just new I'd respond the same.

This situation had been going on for months and this was in fact the first time ever that Ernest has properly responded to a message, anywhere, from anyone, since he went silent. So I took this opportunity to ask questions and get answers from him. A lot of people had already given up or lost interest, but I wanted to know for sure.

I was undecided up to now, but have always expressed my serious doubts about whether a person like him is suitable as a leader of a project like this. Not because of his personality, I am sure he's an awesome guy, but because of his lack of professionalism when things go wrong. Don't get me wrong, I felt very sorry for him all along, he was in a terrible position, no doubt about that and as I've said before I fully sympathize with him. But he should not have dragged the project and its community down with him. I'm glad he's climbing back up again and with him his loyal supporters.

What this entire roller-coaster ride, including this thread, has demonstrated to me over the past few months is, sadly, that should something go wrong again, it will very likely happen in the exact same way.

That for me removes all doubt; I conclude that he is not a suitable leader. I am sorry to say it but it's the way it is.

There is no grievance, but if this all sounds like waa waa babies to you I can fully understand. People were not pleased by the bad code being planted so that kind of set the tone and I understand I sounded like I was trying to make him sound bad. Everything I've said to and/or asked about him is based on reality, however.

It makes sense to me it came across as reactionary, but it's done now. A lot was cleared up for me, all doubt has been removed. Let's all move on with whichever version we prefer and make this great project better than ever
    HeartyBeast,
    HeartyBeast avatar

    You know you come across as incredibly toxic, yes?

    Horza,

    At this point you are just evidencing that Ernest's judgement was spot on.

    TheVillageGuy,

    How so?

    voidavoid,

    If it’s any consolation, you likely won’t have to worry about using it, as its liable to be unusable.

    kherge,
    @kherge@beehaw.org avatar

    I think it’s an interesting experiment. If it survives natural human tendency to mess with things, then it could be a good process discovery that is further refined and implemented elsewhere.

    I don’t have any reason to believe it’ll be a success, but that shouldn’t stop people from at least trying.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • fediverse
  • DreamBathrooms
  • thenastyranch
  • mdbf
  • Durango
  • Youngstown
  • slotface
  • hgfsjryuu7
  • vwfavf
  • rosin
  • kavyap
  • osvaldo12
  • PowerRangers
  • InstantRegret
  • magazineikmin
  • normalnudes
  • khanakhh
  • GTA5RPClips
  • ethstaker
  • cubers
  • ngwrru68w68
  • tacticalgear
  • everett
  • tester
  • Leos
  • cisconetworking
  • modclub
  • anitta
  • provamag3
  • All magazines
    •