Please sign in to access this page
June 16, 2025
nice website and awesome idea! I especially loved the memories you wrote :)
Removed static text in the demo memory, added a few memories from the interface, redeployed the website.
After a lot of issues with the server, I finally deployed!!!
And also, wrote the deployment guide.
I have implemented the whole emailing system!
I made a few helper functions for sending emails and media. Now, the user will receive a simple welcome email when creating a new account.
And mainly, I set up a periodical job in the code to send memories by email when they get unlocked, all of this according to user email preferences, and in the chosen email language, which is automatically set on account creation and can be edited later on.
For the email appearance, I made a simple but nice HTML layout with CSS styling.
I also made it possible for images to be attached to the sent emails in order to be displayed directly when sending memory emails!
Aside from that, I made a few changes and fixes here and there as usual.
I reorganized quite a lot of stuff to make things easier for me and to make the code cleaner. Mainly, I made a few helper functions for repetitive tasks, and I also made subtemplates for the HTML files, so that now I don't have to copy-paste the head and the header to each file, and I can modify those in a single file for the changes to apply on the entire website!
But the real addition since the last devlog here is the new gallery page.
On this page, you can see previews of all your unlocked memories, with their title, date, mood, and also a preview of their content and an image if you uploaded at least one for the memory. Moreover, you can click on the preview to open the full view page for that memory!
The memories are sorted by date with the most recent ones at the top, and there's also a search bar to find a memory with the matching text in either the title or the whole text content.
And finally, I also completed the home page (which was basically empty before), so that now you can see the latest unlocked memory, and a randomly selected memory on the home page!
I think I'm basically finished with the whole interface now! The only thing missing is the emailing system, to send emails when memories are unlocked, that's the next thing I'll work on.
And if I have some more time after that, I'll also add a page to manage your account (change email or password), and a way to recover the account by sending a code by email, but that's not certain yet.
I finally completely finished the memory view page with media previews.
The media are now directly displayed in the page, with a button to open the media fine in a new window if you want to save it or whatever.
Oh boi, this one is pretty long, yet I don't have a lot to say.
There's not a lot to show here because I spent most of these hours on backend stuff, the only frontend part I did is the page to view an unlocked memory, except I didn't add the media previews directly on the page yet.
So on the backend side, I went around here and there and fixed, optimized, or cleaned some stuff, I also added model fields and stuff like that to prepare for future implementations.
But most importantly, I completely finished the private media implementation this time! Everything is now in place to properly handle AND serve private medias, both internally in the code with a helper function and externally with a way to access a memory's media file from the proper URL with permission checks so that only the owner of these media or a superuser can request and get the media files. For now you need to know the database keys to those media objects to find the right URL, but once I'll have implemented the media previews, you'll be able to request the raw media file in the browser by simply clicking on the previews!
(Thank gosh this private media hell is finally done, it was such a pain to set up lmao)
Okay, this one part somehow got way harder than I expected!
So, I implemented the page for the user to create a new memory. On this page, you can give the memory a title, write come content, select your mood by picking an emoji, and you can also customize the lock time for the memory, or keep the default one you set in your preferences.
But the thing that got really complicated was the media upload part.
Basically, you can upload medias (images, videos, etc) with your memory, and these medias will be attached to the memory object, and the files themselves will be stored in a dedicated folder.
The first challenge here was with the frontend, because I had to use a lot of JavaScript to make all of this work, and here I honestly got a lot of help from AI and then built more stuff over the generated code, because I only know the basics in JavaScript.
The second challenge was to privately store those medias, because with the way Django medias work, those can be accessed by anyone who can find the correct URL, but those medias in my case are private.
So I had to create a custom media storage backend which stores medias in their own folder, and those medias can only be accessed internally by the server-side code, meaning that I can perform verification and then serve the media directly from the code, without it being directly exposed.
Now the next step would be to modify the media upload system a bit to improve it, and to build the memory preview page, which shouldn't be that hard (I hope) since I already have almost all the frontend and backend code.
I fully implemented the page to change user preferences.
I also made an empty home page, and coded a bit of JavaScript so that the user gets a warning before exiting on a page containing a form, and also to lock some preferences if the user decided to prevent himself from editing the memories lock time in the preferences.
I also made quite random changes here and there for styling and navigation mainly.
The next step would now be to implement all the memories system in itself.
I finished implementing the sign up page, and also added better cleaner logic in my code.
I modified some CSS again, and also made a terms and conditions page and a page explaining password security. I mainly took the text from these two pages from my previous project, but did some better formatting in HTML and CSS.
I finished the log in page and its backend.
I reused part of the code from my previous project where I also had a log in page, but this time I used Django forms instead of pure HTML forms, I also changed a bit the logic to avoid repetitions, I had way too much in my previous project.
Also I spent some time on the CSS again to try and make the page appealing and visually pleasing, that was quite the challenge to make everything look aligned but I managed to do it using a grid layout.
For the last project, I basically didn't use CSS, so this time I'm making sure the web page looks somewhat pretty!
I wrote a basic index page in HTML, but I mainly spent some time on the CSS to make the page look better.
The layout and styling is pretty basic, but since I have little to no experience in CSS I'm really satisfied with it, I might adjust it later but for now I'll keep it like that and move on to coding the app in itself!
For now I made the basic Django project and app configuration, and I mainly spent some time making some drawings of what I want the interface to look like, so that I know exactly what to do when coding the project.
This is an online private diary where you can write stuff when you want to. Those memories will then be saved and hidden, then those will get revealed again and sent by email after a certain amount of time to remind you of those precious memories! In addition to your notes, you can select your mood, and even upload photos or other pieces of media! HOW TO TEST: If you don't want to create an account, you can log in using 'test' as the username and '12345678' as the password. Since it takes at least one day for a memory to unlock after being written, I already wrote one, which is currently unlocked and therefore visible. There is already one memory which I wrote myself from the same interface as the one you'll have access to, I did this so that there will be at least one unlocked memory which you can display, to showcase the interface, but you can write your own memory and then check back one day after, it will appear as well! You can also check the received emails for the test account by going to https://yopmail.com/ and putting 'diarytrove' as the email name, PLEASE DON'T DELETE THE EMAILS THERE, OTHERWISE OTHER PEOPLE WON'T SEE THEM. AI: I used just a bit of AI (less than 30% but I checked the box anyway) mainly for the JavaScript and to get help on some technical aspects, while reviewing and editing the output each time to ensure proper functioning and security.
I FINALLY managed to deploy the project!
So I did a few changes on some settings and config files, and then started deploying the website.
At first, I used Nest (The server provided by HackClub to host projects), but it broke my project because it uses a proxy, which masks the IP address from the request and causes some issues with parts of the app, so I had to host it myself.
So I made a small setup in my room with my raspberry pi, and configured it as a web server, opened the necessary ports on my router, and after a few very long days, I finally managed to properly deploy the website using an Nginx server with SSL security.
I just finished writing a little readme, and made a full deployment guide. I'm now currently making a little banner for the project, and then I'll be ready to ship a minimum viable product (I may have some beef with CSS but meh, who cares about styling anyway), YIPEEE!
First, I spent quite some time reworking on the project's code in order to reorganize everything, create some helper functions to avoid repetitions, and stuff like that. This part is not directly visible by the user, but the code is now way easier to understand and to expend.
I also added dark mode, with a bit of styling for the page to be displayed according to the browser's color mode, which is great because that bright white page was starting to blind me a bit 😅
And the thing that took me the longest was to update the entire project for it to be translatable in other languages.
I went into each file to mark each and every string of displayed text as translatable with the gettext module from Django, this includes the python files, html files and js ones as well. And after spending way too long to figure out how all of this works, I generated the translation files, and manually wrote all the translations for the French language.
Now, if the browser is set to display pages in French, then the website will be displayed in French, else it will default to English.
I mainly improved some things here and there, including the registration form, with some basic conditions to accept, I also fixed a few bugs with registration and preferences, I also improved the format for the emails, and the last thing is not visible in the interface but I added scheduling for some functions to periodically execute in the code, for stuff like deleting expired pixels for instance.
I improved a bit the way each link is listed on the home page, by adding the domain of their destination url as well as the number of times it has been clicked.
I also added a button to delete a link, with a confirmation popup, and added a bit of styling around the shortened link to make it more visible.
But most of all, I configured my subdomain to also turn it into a mail domain (using Zoho mail), and configured Zoho mail and Django to be able to send automated emails from the web platform in order to notify the user when his link has been clicked. The user can also set an account-wide preference or a link specific preference to choose whether to send an email on the first click, on each click, or to never send one. I will now continue by adding better styling and format the emails sent.
The interface is now fully fixed and adapted to create short links.
I also coded the tracking system, which now successfully logs each click on the short link, except if the person clicking it created it (if he's connected to the account owning this link).
For the person clicking the link, he will get instantly redirected to the destination url.
I finally managed to migrate everything and rename the whole django project after recreating it from scratch and copying relevant files and code blocks, and renaming every variable in the code to be relevant to the new app.
This project has now become ShortView! Monitor the shortened links you send!
I added the link to the webapp to directly get an image, which can be tracked since it does a request to the server.
HOWEVER, I need to change basically the whole system because I realized that when putting an image from a url in a google email, it automatically copies the resource to google's servers, which mean that the request to my server is never made, therefore not allowing to track when someone opens an email.
Since I already did quite some work on this project, I'll just change it a bit to something else.
So, now introducing ShortView! (I guess)
Instead of using an invisible pixel, you'll be able to create a shortened link to a webpage, and the webapp will register clicks on the link, so that you'll know if the person you sent the link to clicked it or not, with all the usual information.
As an attachment, I put a screenshot of the image displaying properly when requesting it from the url, but now I'm going to replace this with the webpage the shortened link points to.
So, time for some model changing, variable renaming and database struggle now 😭
I added a page to create a new pixel agent, on which the user can give its properties. The pixel will then be created and saved in the database, and the user will be redirected on the newly created pixel's page. The pixel will also be displayed in the home page.
I also properly set up the django site model, meaning that it can now create absolute urls.
So I changed the way that pixel's url works: before, each pixel would have its url saved in the database, but now it's not statically saved anymore, but created on the go using the pixel's id and the domain when needed. So now, on a pixel page, it is possible to copy properly its display url (which were placeholders before).
I added a registering system to create a new account.
It verifies that both the username and email address aren't already in use on the platform, and it checks for basic password requirements.
There's also hint texts when hovering above the fields which explains the requirements for the username and the password.
This is done with client side javascript first, then checked again with server side python.
Then, if everything is conform, it will create a new user account in the database, and attach a profile model with the default user preferences.
From there, the user will automatically get logged in, and will be able to log in later, and use his account normally.
I also fixed some bugs here and there.
I added a page which will display information about the selected pixel, displaying its image url which can be copied, as well as a history of each time the mail containing it has been opened, with the date, ip address and request header from the opener (for now this is manually entered placeholder data, but the display part is working).
I also added a page to modify user preferences, for now the only ones are whether or not to display expired pixels, and the default expiration time, with the ability to set it to never expire (in the future, when the pixel functionality will actually be implemented, an expired pixel won't register mail openings anymore, which is useful to avoid notifications from old pixels later on).
I started adding some CSS styling, to use different colors depending on whether the mail containing the pixel was opened or not, and to cross out expired pixels.
I also spend waaay too long figuring out how to reload the static css file after an edit before realizing the browser kept the old one in cache 😭.
A webapp that allows you to create a tracked shortened link and know when it's clicked. NOTE: You need to open the link on another device or in an incognito tab for it to register, as it won't register clicks from the link owner. FOR TESTING: If you don't want to create an account, you can login into the testing account: username: test / password: test ; you can then check the mail notifications on yopmail.com with the email name 'shortview'
This was widely regarded as a great move by everyone.