Still Maintained?

[Finkman]

Reading the pending PRs and open issues leads me to the question:

Is this project still actively developed?

[xshenhan]

same question

[zhaobenny]

While we await an answer, I have a fork with some of the pending PRs merged for anyone that needs Docker images with fixes.

[ormandj]

Has anybody tried to contact @szabodanika via alternative means?

[Finkman]

I read on his page that he is maintaining only on holidays.
So… we should be patient.

[DX37]

While we await an answer, I have a fork with some of the pending PRs merged for anyone that needs Docker images with fixes.

Dude, can you fix eternal pasta? I enabled it and set some to never expire, but they are setting to 1 week max and still expiring. Lost some uploaded files on my own...

[zhaobenny]

While we await an answer, I have a fork with some of the pending PRs merged for anyone that needs Docker images with fixes.

Dude, can you fix eternal pasta? I enabled it and set some to never expire, but they are setting to 1 week max and still expiring. Lost some uploaded files on my own...

The fix for that should already be in the fixed docker image: #215

[DX37]

While we await an answer, I have a fork with some of the pending PRs merged for anyone that needs Docker images with fixes.

Dude, can you fix eternal pasta? I enabled it and set some to never expire, but they are setting to 1 week max and still expiring. Lost some uploaded files on my own...

The fix for that should already be in the fixed docker image: #215

It's not that. "Never expire" is visible, I can select it. But created pasta is still sets to 1 week.
https://github.com/szabodanika/microbin/assets/12829428/f2c8d2e1-f60e-45c6-8a62-1ee7dcc7e686

[szabodanika]

Hi everyone asking. I apologise for disappearing and I really appreciate that you considered using MicroBin. The project is not abandoned (will set it to archived if/when that happens) but not exactly maintained at the moment either. I am still a student and during the academic year I have absolutely no time for side projects (MicroBin grew to a size that requires a LOT of time as the only developer). In the summer I have much more time which you can see from the commit history. This summer I will definitely continue working on the project. No new features planned for the time being as I would like to squash all the bugs first, I understand that there are a few really annoying ones. Feel free to keep opening issues and PRs, they will be tended to eventually, I promise.

[Timshel]

I always have the best timings, just started working on a fork today 😆.
I opened some PR with the change I made.
Not sure what'll do 🤔.

[runofthemillgeek]

@DX37 I've made a fix for it in #260 which seems to be working for me.

[Kofl]

I always have the best timings, just started working on a fork today 😆. I opened some PR with the change I made. Not sure what'll do 🤔.

I really hope the initial developer finds time in summer for this great project. Maybe he is also open for a second main contributor, as Timshel really did great work for e.g. on dani-garcia/vaultwarden for the SSO implementation.

[uniquePWD]

Hi everyone asking. I apologise for disappearing and I really appreciate that you considered using MicroBin. The project is not abandoned (will set it to archived if/when that happens) but not exactly maintained at the moment either. I am still a student and during the academic year I have absolutely no time for side projects (MicroBin grew to a size that requires a LOT of time as the only developer). In the summer I have much more time which you can see from the commit history. This summer I will definitely continue working on the project. No new features planned for the time being as I would like to squash all the bugs first, I understand that there are a few really annoying ones. Feel free to keep opening issues and PRs, they will be tended to eventually, I promise.

Glad to see this is still being maintained. With all the pull requests, the community is clearly ready to help support you.

[johnmmcgee]

Great project and I too would love to see it maintained. Perhaps give others write access to the repo who would help maintain it?

[uniquePWD]

Hi everyone asking. I apologise for disappearing and I really appreciate that you considered using MicroBin. The project is not abandoned (will set it to archived if/when that happens) but not exactly maintained at the moment either. I am still a student and during the academic year I have absolutely no time for side projects (MicroBin grew to a size that requires a LOT of time as the only developer). In the summer I have much more time which you can see from the commit history. This summer I will definitely continue working on the project. No new features planned for the time being as I would like to squash all the bugs first, I understand that there are a few really annoying ones. Feel free to keep opening issues and PRs, they will be tended to eventually, I promise.

With summer almost over, any news on this?

[uxfion]

‌‌‌May need a new successor or collaborator.

[Timshel]

Hey
I worked on a fork in March but then stopped when the author posted his message.
I don't have much time to work on it but decided to make a release 2.0.5 with the change I made and publish a docker image (the base image is now based on bookworm-slim executable is renamed to sharebin and all env prefix was replaced with SHAREBIN).

For now, I don't have anything more planned but will be around to merge fix and will check bugs.
Will see if there is some interest :).

[johnmmcgee]

Hey I worked on a fork in March but then stopped when the author posted his message. I don't have much time to work on it but decided to make a release 2.0.5 with the change I made and publish a docker image (the base image is now based on bookworm-slim executable is renamed to sharebin and all env prefix was replaced with SHAREBIN).

For now, I don't have anything more planned but will be around to merge fix and will check bugs. Will see if there is some interest :).

Awesome stuff. Thank you for the effort.

[dvdsk]

@szabodanika

Dániel, I hope you are doing well. Like many I appreciate the work you, together with the wider FOSS community, have put into microbin. It is a wonderfully light, clean looking webapp. Understandably you do not have the time to maintain microbin on your own. Unfortunately you being the only maintainer has led to the community's efforts being splintered around multiple forks wasting a lot of work.

The good news is that there is still a lot of effort being put in. While applying PR's to my own maintained fork, I ran into three others. I think together we could take care of microbin with you.

I propose you add me as interim maintainer of microbin. I have experience taking over maintainership and mobilizing the FOSS community. See my work with the rodio community. Just like you I do not have time to maintain microbin forever but I can help out to build up a team which can. The people maintaining microbin forks might be able to help.

I hope to hear from you in the next two weeks. If you cannot respond, that is okay. Open source is fun but there are more important things in life. If that happens I'll set up a microbin organization and move my fork to it then try to organize the community around that. We will not let your creation die, it's to useful to us :)

PS; I will also try and contact @szabodanika over mail

[uniquePWD]

It makes me happy to see that MicroBin will not only survive but flourish. It requires very little upkeep, so hopefully it's not much of a burden on all who come together to help maintain it.

[szabodanika]

Hey guys, can you please email me at [email protected] if you would like to be added to a mail chain about establishing a group of maintainers instead of me being the only "maintainer" of the MicroBin.

[dvdsk]

Looking through the list of forks I think @mikedamm (fork), @kyleyh838 (fork), @overcuriousity (fork), @Timshel (fork] and @OXeu (fork). might all be interested. I hope by mentioning their names here there is a larger chance they see your message about the mail chain.

[overcuriousity]

My fork exists because the upstream seems to be abandoned.
Currently I am doing only occasional security fixes.

[Danie10]

This is pretty sad as this project had tremendous potential with ability to edit, list, etc. But there are a few things requiring fixing and I just can't use it in this state as my requirements are for read-only with password protected edit and delete.

[overcuriousity]

This is pretty sad as this project had tremendous potential with ability to edit, list, etc. But there are a few things requiring fixing and I just can't use it in this state as my requirements are for read-only with password protected edit and delete.

Feel free to contribute to my Fork! Can´t really code in Rust anyway w.o. AI.

[Danie10]

@overcuriousity thanks I need a Docker install tho - but I see the links to the forks now above - I'll explore those.

[dvdsk]

If you read the last few messages you can see that microbin is very much maintained and in the process of setting up a group of maintainers to speed up development. You can also check the commit history to confirm that.

[uniquePWD]

Did a maintenance group manage to form? Is MicroBin safe going forward?

[overcuriousity]

Maintainer is currently evaluating how to go forward from here.
Meanwhile my fork is maintained and I would consider it to be safe (pentested a bit), but this should also be true for the original microbin which received a number of commits in October (not pentested it, but integrated into my fork).

[Danie10]

EDIT Link Fixed: I just did a video comparing MicroBin and PrivateBin at https://www.youtube.com/watch?v=jusUL_YrRkA. After looking at both, I'm pretty happy with MicroBin - I included my workaround for how to delete a Read-Only note with password, when it was reporting incorrect password. For my purposes MicroBin is working out better (and I need it it a Docker container).

[Finkman]

I guess the link is wrong. I see something strange about Austrailian election.

[uniquePWD]

The correct link should be https://youtu.be/jusUL_YrRkA

[Danie10]

Sorry guys, yes that was an incorrect link (ouch). OK, I also edited in my post above so it is correct. But one that @uniquePWD provided was also correct.

[tecosaur]

Not being involved in the email chain, I don't suppose there has been any progress that can be publicly shared?

[dvdsk]

Not being involved in the email chain, I don't suppose there has been any progress that can be publicly shared?

No good news there unfortunately, there was one other person interested in taking over/helping out. I requested access to microbin for me and that person. Since then the mail chain has been silent.

That was some time ago, by now I no longer have the time to make a difference (rodio maintenance is eating all my time).

[Danie10]

Not sure if there are maybe good active forks otherwise. I just need to have a Docker installation, but must say mine is otherwise just running quite well still as-is.

[uniquePWD]

Maybe an idea would be to put out a release which features all the merged patches and in the release notes, mention that the project needs maintainers?

[tecosaur]

Mmm, something would be good. I don't think I want to sign up for being the maintainer, but there are a few changes I'd like to contribute to with this project, see: https://public.tecosaur.net/plans.html#microbin.

[dvdsk]

If you want to work on microbin I would be happy to merge those changes on my fork. It has all viable PR's from this repo merged and if the current maintainer of microbin hands over maintenance to me we can merge that repo back into this*.

*Last time the maintainer reappeared they quickly merged a number of PR's into microbin. As a consequence of that the history between my fork and microbin has diverged. If I become maintainer I will be overwriting that diverged history preserving the work in the fork.

[uniquePWD]

I think that's a good plan. Timothy submit your PRs to David's fork and then put that release out.

[dvdsk]

oh and Timothy if you want to be a maintainer, I do not see any problem adding you as one to the fork. Same for anyone here, let me know and ill add you.

[Timshel]

Since I always have the best timings just updated the fork I created in March with the merged PR 😅 .
I did not answer the past call for maintainers since If I ever start working on it, I would make some breaking changes (probably dropping json backend and adding Postgres support).
Anyway don't plan to be very active in the short term but will be around to merge stuff and update the docker image if needed.

[Danie10]

Sounds good. The thing is with any forks, I'd want to be able to migrate across and retain all my existing pastes, with Docker. So if there is any confirmation from the forks whether that would be possible, it would help.

[Timshel]

@Danie10 did not test it and might depend on how you configured your volume. But one of the first change I made was to ensure that the SHAREBIN_DATA_DIR could work with an absolute path (had some issues with attachments).
Otherwise, did not change any of the file logic hierarchy or db/document name.

[Danie10]

@Timshel This is what I'm using:

image: danielszabo99/microbin:latest
volumes:
  - microbin-data:/app/microbin_data

[dvdsk]

I did not answer the past call for maintainers since If I ever start working on it, I would make some breaking changes (probably dropping json backend and adding Postgres support).

I'm more then okay with breaking change. But I think we do need to provide migration and discuss breaking changes in advance.

For example regarding db, the first change that should be made is to decouple the db code from the rest of microbin. Then adding/removing/changing db implementations becomes trivial. This is a relatively easy change, just a lot of work.

Regarding the json db, one of its advantages is that it has no runtime or build time C-dependencies. Thanks to it Microbin can be build such that its binary runs on any linux system (with the same architecture). No need to run docker, just copy the binary and you are done.

[Timshel]

@Danie10 I expect with just changing the volume to microbin-data:/app/sharebin_data it should work (make a backup 😄).
If you want to discuss it further please open an issue.

[Timshel]

@dvdsk to be honest at the moment the interest appear to be quite low (46 downloads on the docker image).
So I encourage people to test it and open issues if they need help, and I'll update the readme but I won't be very proactive.

I mentioned the hypothetical breaking change mainly to explain why I did not answer the call for maintainer and give a sort of heads-up if some people end-up using my fork.

I do not want to draw away traffic from your efforts but had started to merge before your post so decided to still mention the release.

[tecosaur]

Sounds like the best idea would be for me to start from @dvdsk's fork, and then see about those changes I'm thinking of working on.

[dvdsk]

@Timshel if you end up changing your mind and would like to join the maintainers of the fork let me know. Your work would be highly appreciated. We do not need to endlessly discuss changes in text, we can always jump on a call to hammer things out.

[uniquePWD]

@dvdsk to be honest at the moment the interest appear to be quite low (46 downloads on the docker image). So I encourage people to test it and open issues if they need help, and I'll update the readme but I won't be very proactive.

I mentioned the hypothetical breaking change mainly to explain why I did not answer the call for maintainer and give a sort of heads-up if some people end-up using my fork.

I do not want to draw away traffic from your efforts but had started to merge before your post so decided to still mention the release.

I had an interest in your fork, but between requiring the renaming of all the environment variables and also the lack of ARM64 build, it was a no go for me.

[dvdsk]

I propose we keep the name of microbin for the time being. I do however understand the renaming, eventually you get enough new features that you want to differentiate from the original unmaintained project. Otherwise you might get a lot of confused end users. A good example of how to do that is the ratatui lib (maintained and very successful fork of tui-rs). A new name is the best way to differentiate. Which is why I think @Timshel went for a rename.

My hope is still that we can eventually merge back here and move this repo to an organization, so for now lets not rename. If we can not unfork we can consider a rename. We should probably duplicate the environment variables so the maintained fork is still a drop in replacement.