5 ms·

built in remix.run with a Python backend, basementcommunity is a nod to early forums from the early 2000s like something awful and fark, focusing on manual mode

built in remix.run with a Python backend, basementcommunity is a nod to early forums from the early 2000s like something awful and fark, focusing on manual moderation and discussions happen in chronological order

deleted 4y ago
[deleted]
bartread 4y ago
I like it. Never noticed a forum with a wall of shame before even though I lurked on a few old skool car forums in the mid-2000s. I do remember a heck of a scrap occurring sometime 2005/6 between 300zx.co.uk and a couple of the other forums of the time. Loads of people banned, even longtime users, site admins, committee members. It was a mess.
- floren 4y ago
  The "wall of shame" on this site comes pretty directly from the Something Awful forums Leper's Colony: https://forums.somethingawful.com/banlist.php https://forums.somethingawful.com/banlist.php
  - partly_cloudy 4y ago
    yup
quadrature 4y ago
I've been playing around with remix and i come from a python backend. would love to know more about how you mix these two ?. Is the backend essentially just a rest API with a handoff to remix for rendering ?.
- partly_cloudy 4y ago
  yep the Python backend is a standalone rest API and the FE is running on a completely separate server
jay-barronville 4y ago
Why Remix with a Python backend? Did you need Python for anything specific? Is there some specific need that a pure Remix backend couldn’t give you? Just curious.
- partly_cloudy 4y ago
  actually at the time i wrote the API, i was still considering how the FE was going to be written, so because i never used remix until this point, i didn't realize they offered an all-in-one solution. honestly i like the seperation of concerns though, so i'm happy with it. might even rewrite the API again to teach myself rust
  - Kiro 4y ago
    So why even use Remix? Maybe I misunderstand what it is.
    - Ralfp 4y ago
      With Remix, you run two two servers: - Remix server - API server When user visits your page, their first HTTP request hits the Remix, which pulls data from API server and renders initial HTTP response from your React.js UI. It then sends this response to the client, so you see full site load at one time, even with JavaScript off. If you have JavaScript enabled, the client version of the React.js UI will load and replace the HTML generated on server, making things interactive. This UI will hit Remix API server for Remix features, but you can still hit your API server from individual components if you need.
ricopags 4y ago
any plans to share the code? I've been thinking of rebooting a crappy club for jerks and this looks like it could be a great jumping off point if you'd be willing to share

deleted 4y ago

[deleted]

bartread 4y ago

I like it. Never noticed a forum with a wall of shame before even though I lurked on a few old skool car forums in the mid-2000s. I do remember a heck of a scrap occurring sometime 2005/6 between 300zx.co.uk and a couple of the other forums of the time. Loads of people banned, even longtime users, site admins, committee members. It was a mess.

floren 4y ago
The "wall of shame" on this site comes pretty directly from the Something Awful forums Leper's Colony: https://forums.somethingawful.com/banlist.php https://forums.somethingawful.com/banlist.php
- partly_cloudy 4y ago
  yup

quadrature 4y ago

I've been playing around with remix and i come from a python backend. would love to know more about how you mix these two ?. Is the backend essentially just a rest API with a handoff to remix for rendering ?.

partly_cloudy 4y ago
yep the Python backend is a standalone rest API and the FE is running on a completely separate server

jay-barronville 4y ago

Why Remix with a Python backend? Did you need Python for anything specific? Is there some specific need that a pure Remix backend couldn’t give you? Just curious.

partly_cloudy 4y ago
actually at the time i wrote the API, i was still considering how the FE was going to be written, so because i never used remix until this point, i didn't realize they offered an all-in-one solution. honestly i like the seperation of concerns though, so i'm happy with it. might even rewrite the API again to teach myself rust
- Kiro 4y ago
  So why even use Remix? Maybe I misunderstand what it is.
  - Ralfp 4y ago
    With Remix, you run two two servers: - Remix server - API server When user visits your page, their first HTTP request hits the Remix, which pulls data from API server and renders initial HTTP response from your React.js UI. It then sends this response to the client, so you see full site load at one time, even with JavaScript off. If you have JavaScript enabled, the client version of the React.js UI will load and replace the HTML generated on server, making things interactive. This UI will hit Remix API server for Remix features, but you can still hit your API server from individual components if you need.

ricopags 4y ago

any plans to share the code? I've been thinking of rebooting a crappy club for jerks and this looks like it could be a great jumping off point if you'd be willing to share