party.darklite.org - Demoparty travel planning
category: general [glöplog]
Announcing: https://party.darklite.org/
A demoscene site where you can enter and view how people are traveling to demoparties. Login is via SceneID.
Some of you may recognize the predecessor for this, which was done in wikispaces. Now that wikispaces has gone the way of the dodo, we decided to make a dedicated service for this.
May contain traces of nuts and python code. Does contain bugs.
We also released a little wild video party prod at Vortex about this, for those interested: https://www.pouet.net/prod.php?which=79229
I do plan to release the code in a public git repo.
This official thread will also address any questions, bugs, worries and feature requests.
Enjoy RESPONSEbly!
Sincerely,
T-101 / Darklite
A demoscene site where you can enter and view how people are traveling to demoparties. Login is via SceneID.
Some of you may recognize the predecessor for this, which was done in wikispaces. Now that wikispaces has gone the way of the dodo, we decided to make a dedicated service for this.
May contain traces of nuts and python code. Does contain bugs.
We also released a little wild video party prod at Vortex about this, for those interested: https://www.pouet.net/prod.php?which=79229
I do plan to release the code in a public git repo.
This official thread will also address any questions, bugs, worries and feature requests.
Enjoy RESPONSEbly!
Sincerely,
T-101 / Darklite
That's really useful! :) Cool.
Help is needed, will YOU be the one to help?
http://wanted.scene.org/post/141/need-icons-for-party-darklite-org
We need official icons for the favicon and to be used on other sites. If you feel the urge to brush up your best pixellating computer: here's your chance!
Contact via the url provided and lets make icons great again!
http://wanted.scene.org/post/141/need-icons-for-party-darklite-org
We need official icons for the favicon and to be used on other sites. If you feel the urge to brush up your best pixellating computer: here's your chance!
Contact via the url provided and lets make icons great again!
• Edit trip.
• Change second “Additional info” field of the “towards party” section to somethang longer than 24 characters (who makes up these tiny limits? Are you paying per byte?).
• Hit “Save.”
• Field is marked with error (which is not the bug).
• The fields “departure datetime” and “arrival datetime” of the “towards home” section are now empty.
• Change second “Additional info” field of the “towards party” section to somethang longer than 24 characters (who makes up these tiny limits? Are you paying per byte?).
• Hit “Save.”
• Field is marked with error (which is not the bug).
• The fields “departure datetime” and “arrival datetime” of the “towards home” section are now empty.
Feature request: transport type doesn't allow for bicycles. Please add it, thanks.
another bug found, maybe a party shouldn't last a negative amount of days.
more bugs yay: this url is now 500'ing
Also another feature request: home->party and party->home travel should be separate (eg. I'm going to rsync by train, but going back home by bicycle)
also "country" for synchrony is kinda moot, picked the one where the compos happen (looks like demozoo did this too this way)
Announcing a soft relauch of the site! https://party.darklite.org/
No one has been going anywhere for the past two years, which gave me plenty of time ... to completely rewrite this in two weeks.
Some new features include but are not restricted to:
- We finally have a favicon! Thanks to Epo on this
- Slightly optimized layout, mobile friendly
- Filter party visitors by name, country, flight number etc.
- In mobile devices, datepicker will render as client default which makes for much better user experience that the JS thingie in desktop views
- An entire one (1) top10 list of most visited parties
- Removed Google Analytics
- The font from Google is now locally served instead of their CDN
- Snazzy OpenGraph for prettier url previews in more modern messengers than IRC
- A lot less wtf in the code
Thank you Bombe and porocyon four your bug reports, those were addressed. The trip details can now be 32 characters :) and they are no longer mandatory. The 500 errors were due to the bug that allowed two parties with the same slug exist. That is no longer the case. I forgot about the bicycle, but future updates are afoot.
I appreciate and I'm humbled by all the support and kudos lots of people have expressed to me over this project. Please don't hesitate to send me suggestions and above all, bug reports. I will be putting the code in a public repo "soon", just need to clean it up a bit :rainbow-poo:
Greetings and see y'all at parties to come!
T-101 / Darklite ^ Dekadence ^ Primitive ^ Accession
No one has been going anywhere for the past two years, which gave me plenty of time ... to completely rewrite this in two weeks.
Some new features include but are not restricted to:
- We finally have a favicon! Thanks to Epo on this
- Slightly optimized layout, mobile friendly
- Filter party visitors by name, country, flight number etc.
- In mobile devices, datepicker will render as client default which makes for much better user experience that the JS thingie in desktop views
- An entire one (1) top10 list of most visited parties
- Removed Google Analytics
- The font from Google is now locally served instead of their CDN
- Snazzy OpenGraph for prettier url previews in more modern messengers than IRC
- A lot less wtf in the code
Thank you Bombe and porocyon four your bug reports, those were addressed. The trip details can now be 32 characters :) and they are no longer mandatory. The 500 errors were due to the bug that allowed two parties with the same slug exist. That is no longer the case. I forgot about the bicycle, but future updates are afoot.
I appreciate and I'm humbled by all the support and kudos lots of people have expressed to me over this project. Please don't hesitate to send me suggestions and above all, bug reports. I will be putting the code in a public repo "soon", just need to clean it up a bit :rainbow-poo:
Greetings and see y'all at parties to come!
T-101 / Darklite ^ Dekadence ^ Primitive ^ Accession
Added support for dark mode.
And after literally no one except Response (twice) asking for it, I've now released the codebase as open source: https://github.com/T-101/party.darklite.org
Enjoy, or not. But do go to parties <3
Sincerely, drunk, and at Black Valley 2023:
T-101, Response, tFt and Darklite
And after literally no one except Response (twice) asking for it, I've now released the codebase as open source: https://github.com/T-101/party.darklite.org
Enjoy, or not. But do go to parties <3
Sincerely, drunk, and at Black Valley 2023:
T-101, Response, tFt and Darklite
I started thinking. Nearly caused an aneurysm.
But what if someone would like to be forgotten. They have a right to do so.
What would be the "correct" way to implement that in the db?
- Delete all rows connected to that user?
- Mark those rows as [deleted user]?
- None of the above? All of the above? I don't know.
Any thoughts on this? I would love to have the overall stats to remain the same, but that may not be on the table.
And what it the user wants to come back? The only way to use the site is to use SceneID, so blocking that would seem a little excessive.
But what if someone would like to be forgotten. They have a right to do so.
What would be the "correct" way to implement that in the db?
- Delete all rows connected to that user?
- Mark those rows as [deleted user]?
- None of the above? All of the above? I don't know.
Any thoughts on this? I would love to have the overall stats to remain the same, but that may not be on the table.
And what it the user wants to come back? The only way to use the site is to use SceneID, so blocking that would seem a little excessive.
From my experience and generally speaking, deleting all rows connected to a user (which should happen automatically when all foreign key constraints are setup correctly and the data is properly normalized) has too many potential side effects threatening your data integrity and overall traceability / transparency, thus its best to simply flag users as deleted and anonymize the fields containing personal information. To be compliant to the GDPR this process has to be irreversible so resurrecting a previously deleted account is out of the question, so is restricting access for "forgotten users" (why would one even want that?).
deleted user. leave everything else.
What LJ said. Often you can't even really delete the user DB row, because of foreign keys and the likes, but you can set all fields to "[deleted]" + wipe their password and you pretty much solved it.
Don't just delete everything. If you want to be more thorough, you could give them the option to also set all their content to [deleted]. When you do that, a conversation might look like
A: Hey there
B: Lovely weather huh
[deleted]: [this message has been deleted]
A: WHAT THE FUCK MAN! SRSLY GET A GRIP
Compare this to:
A: Hey there
B: Lovely weather huh
A: WHAT THE FUCK MAN! SRSLY GET A GRIP
and it should be obvious why completely deleting everything ever posted by that user is not usually a good idea.
Don't just delete everything. If you want to be more thorough, you could give them the option to also set all their content to [deleted]. When you do that, a conversation might look like
A: Hey there
B: Lovely weather huh
[deleted]: [this message has been deleted]
A: WHAT THE FUCK MAN! SRSLY GET A GRIP
Compare this to:
A: Hey there
B: Lovely weather huh
A: WHAT THE FUCK MAN! SRSLY GET A GRIP
and it should be obvious why completely deleting everything ever posted by that user is not usually a good idea.
