In this meeting, the State Changers category discussed a variety of topics revolving primarily around WeWeb and Xano platforms. Participants sought to understand how to implement secure time-check functionalities at the front end, particularly in situations when a link is clicked; they learned the role of using a timestamp and comparing it with the current time to ascertain whether the link had expired or not.
The process outlined involved creating a second field (the expiration time or the create time) in the URL alongside the key, putting them together using an ampersand. The check would be on the WeWeb side, where, on page load, the query would inspect the timestamp. Custom JavaScript was proposed to execute this function. Participants also discussed the concept of "states," mainly in relation to form submission success. They explored how various actions (like returning to a default value or resetting) affect these states in the WeWeb environment. The intricacies of creating these actions by either resetting variables to default or implementing more complex solutions were addressed. However, it was noted that depending on how variables are managed, they might need to take additional steps to ensure accurate state representation between sessions. A concern was brought up about knowing when a webpage is unloaded, but it was pointed out that web browsers don't often provide accurate signal for this, making it challenging to create an efficient solution. The discussion then turned to geolocation, which elicited caution because of the inaccuracy of most geolocation services. Overall, the meeting touched on keyword technologies such as WeWeb, Xano, and JavaScript, amongst others, with the primary aim to solve specific development challenges related to timestamps, variables, states, and geolocation.
(Source: Office Hours 2/3 )
