Live data from Hacker News

PhpBB 3.3.10

phpbb.com

141–150 of 203 posts

Re: PhpBB 3.3.10

#142

Earlier quoted context omitted.

One bad thing about old forum threads is a lot of the images are lost. Disk space and bandwidth were still expensive back then. The free image hosts mostly disappeared or started charging (so many forums have dead photobucket links).

Same thing is going to happen again once imgur shuts down. While the pictures that were actually hosted on the forum itself are usually fine.

Same thing happened when gfycat spun off the adult content into redgifs. A thousand subreddits all had their content go 404.

Re: PhpBB 3.3.10

#143

A lot of nostalgia here, but I'm sure I'm not the only one who shudders when hearing the words "PhpBB" because of all the security vulnerabilities

Not only that, I had a PhpBB hosting service back in the day and every update they changed something which nearly broke my service...

There are some really strange things in the PhpBB codebase - I remember that the software somehow found out that I injected custom code and therefore stopped working.

(My biggest problem was the upgrade from 3.0.12 to a newer version (probably 3.1) back in 2014 / 2015)

Re: PhpBB 3.3.10

#144

Ah the OG. Does anyone knowledgeable about forum software know witch is the most resource-less intensive? PhpBB, SMF, MyBB, Xenforo, BBPress (or others)? I know with SMF, one can disable lots of features and make it lightweight, but would like to know more.

I would mention PunBB[0], which can run on a potato computer. It was often configured to use a SQLite database, so it seems very light in terms of CPU, disk and memory usage. And source code? It is very thin too.

Also Flarum [1] looks good in terms of being lightweight. It is based on Laravel Framework, so it has own pros and cons, but thanks to wise implementation of mithril.js, it feels very fast from a user perspective.

On a different spectrum, I would list Discourse [2], followed by Invision Power Board (IPB) [3]. Both require 2GB+ of RAM and a good CPU to run the server.

[0]: https://punbb.informer.com/forums/

[1]: https://flarum.org/

[2]: https://github.com/discourse/discourse/blob/main/docs/INSTAL...

[3]: https://invisioncommunity.com/

Re: PhpBB 3.3.10

#145
post #54

Earlier quoted context omitted.

Which really didn't matter back then. People just deleted the spam, recovered from backup, patched whatever flaw they found, and changed passwords. It wasn't the end of the world.

Lots of the forums I used to use died this way. The site owners eventually got tired of having to janny the site daily to fight an endless wave of attacks. It's all moved to reddit and discord these days.

Janny?

Re: PhpBB 3.3.10

#147
post #9

Every time I see hype about Mastodon and the fediverse I miss the phpBB days. There was something special about the interlocking network of forums that didn't need to "federate" in any formal capacity. We just joined communities we liked and formed overlapping networks like normal people do and always have done. No one at the time felt any need to try to accommodate the whole world in one venue. As someone who never…

AIUI the Fediverse is just a machine-readable protocol for BBS-like or social-like interactions. So it would seem quite possible for PhpBB to interoperate with it, e.g. have users on a PhpBB board formally reference a Fediverse post such that their replies can be seen by Fediverse clients, and vice versa. It decouples social connections from the admin/moderating policies of a single board, much like email or Usenet news.

Re: PhpBB 3.3.10

#148

I used to despise PhpBB, at the time I thought it was vastly inferior to SMF. SMF seemed far more professional, the closest you could get to vbulletin while being free. In retrospect I miss it just as much. I really do mourn the loss of communities I was part of, I even owned one for a short while. The friends, the discussions, the projects, all lost to time.

I wasn't a fan of PhpBB either but got used to it as a user. PunBB, Flux, and MyBB were fantastic for small admin teams. There was very little overhead for modification and maintenance. I ran a PunBB board for over a decade. It was extremely lightweight, and if you left off the footer ID & version info in the template you wouldn't get hacked nearly as easily as with the popular systems. (One of the worst ever was whe…

I also ran a PunBB forum (an automotive forum) for about 6 years before selling the site to VerticalScope. It was the largest PunBB-powered site for quite some time, by number of posts and users, and considering that it's still running the same old version of PunBB to this day, I'm guessing that the VerticalScope team couldn't figure out how to migrate it to InvisionPowerBoard.

Shocked they haven't been hacked and defaced, but PunBB never seemed to attract much attention compared to PhpBB and others.

Re: PhpBB 3.3.10

#149
A shameless self promotion, but for last 10 years or so I've been developing and maintaining my own forum software, Misago:

https://misago-project.org/

It's build with Python and React, so obviously not so easy to setup like PHP solutions, but there's also a magic docker setup that you can just git clone to your server and get forum running in minutes.

But with Misago I am trying to find a sweet spot between "new wave" of forum software and old solutions. So there's plenty of interactivity in the UI that JS provides and there's markdown support, but there's also classic pagination instead of infinite scrolling.

Re: PhpBB 3.3.10

#150
post #103
post #43

In the last month, I’ve been experimentally replacing my use of Trello, stickies, and todo lists with a phpBB instance. So far I’m the only user, but it’s a surprisingly nice system for keeping track of notes and regular status updates on my projects. And when I need to collaborate with someone, the permission system is quite nice as well. The fact that it’s free, mature, and relatively easy to install and maintain a…

Huh now I really wonder if it would work out if you would replace Slack with a bulletin board organization wise

I implemented one for my company in 2006, and it worked much better than the Slack they use now, imho.
Post reply on HN