117 karma · joined August 23, 2019
Not only has Hey.Café expanded so much in the last year but we are working hard on some really big changes. Would love if you checked it out and open to feedback and making changes based on feedback.
That would require building 2 completely different apps that work completely differently.
There is no CSS, no resources that are loaded in, all the structure and style and everything is generated as it's needed so that the server does not need to parse and create pages that end up using and spending a lot of resources when under load. This way the server only gives the JSON data out and the website parses and generates everything.
Can't do that without Javascript, just like an Android or iOS app can't work without using a front end language to generate the view that you interact with.
I checked with the email you set on the account, your mail provider said the address does not exist.
I can't stand sites that are tracker heavy so I chose to never add that type of stuff.
Each café is made by someone and they can have moderators. Things can be private or features locked down from public or even other members, so for example our own updates one only allows comments and reactions from members except admins who can post the updates.
The payload includes icon's and SVG data that I am slowly removing to lower it's size. The entire app is all in the one block.
History management the back button was added on request and based on mobile usage, it should be fine with the default browser button but I will take a look.
The links I totally get, as everything is generated as it's needed that can be changed over and I will take a look at that.
The time is based on the servers time as clients can be all over the place and I am not tracking where users are and timezones, I have never seen times jump all over the place so I will take a look as the timestamp is provided in the same request as the data so it should be updated as the content is loaded.
The inputs are sanitized and rendered as HTML characters, it just appears to be a bug with the render back as regular characters on edit so that users don't see the HTML characters in the text input, but that would be only on the user who made the content that it would do anything, but I will add rules to remove that type of tag server side also. For example what you gave turns into.
<script>alert(1);</script>
It just turns back to normal characters when you bring it up to edit the input as the one who set it.
I will use all this and make some changes, the links where not on mind mostly to the expectation it would mostly be used in an app capacity.
It also means rich embeds and more like videos, tweets, articles and formatting.
Also encryption for anything not public.
Thanks everyone!
Also the inputs to create a new conversation on your account from the main feed view at the top to be more inline with what users expect and not a button to open.