Skip to contentPlease note that GitHub no longer supports old versions of Firefox.We recommend upgrading to the latest Safari, Google Chrome, or Firefox.IgnoreLearn morepixelpost/pixelpostSign upWhy GitHub?Features →Code reviewProject managementIntegrationsActionsPackage registryTeam managementSocial codingDocumentationCode hostingCustomer stories →Security →EnterpriseExploreExplore GitHub →Learn & contributeTopicsCollectionsTrendingLearning LabOpen source guidesConnect with othersEventsCommunity forumGitHub EducationMarketplacePricingPlans →Compare plansContact SalesNonprofit →Education →In this repositoryAll GitHub↵Jump to↵No suggested jump to resultsIn this repositoryAll GitHub↵Jump to↵In this repositoryAll GitHub↵Jump to↵Sign inSign upThis repository has been archived by the owner. It is now read-only.Watch11Star30Fork13pixelpost/pixelpostArchived
Code
Issues
0
Pull requests
0
Projects
0
Wiki
Security
Insights
Code
Issues
0
Pull requests
0
Projects
0
Wiki
Security
Pulse
Dismiss
Document your code
Every project on GitHub comes with a version-controlled wiki to give your
documentation the high level of care it deserves. It’s easy to create
well-maintained, Markdown or rich text documentation alongside your code.
Sign up for free
See pricing for teams and enterprises
Home
Jump to bottom
Jay Williams edited this page May 6, 2019
·
2 revisions
tldr: This project is abandoned, and has known security issues, use at your own risk.
Well, I have been thinking quite long before actually posting this message, but it is evident that something has to be said. Let me just make one thing clear: This is solemnly my own view on things.
It seems that currently I’m the only developer/moderator left at this site who tries to be active. Despite the fact I tried to do as much as possible this has resulted in a lot of (automatic) spam comments, not only on the forums but at the blog as well. I made a start to clean everything up but it is so much. It is nearly impossible to do this by myself.
Today I saw some questions about the much expected new version of Pixelpost. And I know that you guys want to know the current status of it. Well, here it is. It started as a good project, with three developers spending time on it. It took some time (and a couple of complete rewrites) to get to a state we felt was like a solid base for a photoblog and a worthy replacement of the old Pixelpost code.
But then things took a turn for the worse, and suddenly all three developers didn’t had much time left to spend on the new version. Real life kept (and keeps) them occupied enough, making it hard to continue development. As I can only speak for myself I find it difficult to work on this version alone since I rely on input of the other developers a lot. Sometimes you have to toss an idea back and forth before it gets its actual shape.
A few years back I did the majority of the code that pushed the 1.5 to the 1.6 version and I actively help