anr13

Thanks this all helps a lot. I am adding it to my feedback document and I will make some changes. The time thing sounds like the JS failed to connect for a second to the backend endpoint, thats what tells the site what the timestamp is now for it to calculate times.

Sure. Database is really standard, media is stored on B2 and the backend is made easy so I can scale up the servers as I need really quickly. I am going to post some images over on Hey.Café of the usage here, but I am seeing only a few percent points of usage with 300k+ requests at the moment.

The JS is separated on my end to files for editing and on push to GitLab it compresses it down on the server that hosts the frontend.

Each backend endpoint is a $5 server on vultr, the front end one is also just a $5 server and the database us a $10 one but it's seeing little load.

I plan on making things extremely open like the API with no limits at all. The front end is just one JS block of code so really easy to modify and make a custom version. I like the idea of running your own instances but I find that never works well on the user side for consistency, but offering an open API for anyone to make a client they like is where I want to see it go.

Server side and the little bit I need I can get from the DNS end like country and stuff. I don't plan on adding anything user side that slows things down or makes it a mess.

I will need be adding anything like analytics user side, or tracking of any kind. I want the services to be ad free for everyone and larger features for Pros. I hope this can make it a project that can run into the future. It just had over 200K request in a few minutes and the server load is under 3% for under $50 a month and it is easy to scale.

You can get what's called Pro. Thats what lets you setup communities and groups and allows for larger content and higher quality media. This is my second large social network and the first was online for almost 10 years. It's extremely lightweight as all the generation and everything is all client side so the server just stores DB data and provides JSON payloads.

Oh, never seen that one before, I will see what I can find and fix that.

No never seen before. I will take a look.

Thanks. I know it's not for everyone, and the differences are huge once using especially the groups and longer form content and uploads. But it's not a design everyone will love.

Thats why I am making a open API that will be free to use with no limits so anyone can do anything they want as far as clients go.

A little yes, the thing with stuff like Cafés that are the groups users can join, the person who creates it can also do moderation and setup a moderation team but everything must still follow the global rules.

This means a lot more users can moderate content besides just the main staff.

You can get Pro and that gives larger quality images and the ability to upload files like videos. It also gives larger content, but over time I will allow others to make longer content also. Just need to get some real usage under the belt to see what kind of resources it uses up.

https://wave.hey.cafe/pro

Yes, adding to my list a compact mode, and a search is on the explore area, but I plan to move that to the header with drop down feedback as you type.

I am adding RSS feeds shortly it's in my todo, I can already read them and will provide RSS and JSON outputs for feeds and user info and more.

Good idea, I did add a comment to the top of the page that will take them back but I think adding a dummy comment and new conversation field is a good idea.

Not entirely. The entire front end is a single JS block, so anyone can re use, but I also am making the entire API endpoints I made open and just working on the documentation now.

I totally want to yes, the backend api's are all going to be public shortly. You can see some stuff we are working on and updates here: https://hey.cafe/c/hey and more in the conversation I made 4 days ago with some changes already made. https://hey.cafe/conversation/j8olwfmlbpmlloww4yh4bxfz9

:)

That is the one down side I built the entire thing as one JS block, so without JS there is absolutely nothing, but it also includes no external JS or anything, it's just inline and it's got no tracking or analytics at all on the client end.

Oh thats a good idea never though of that. It's got a really simple json backend api where you can request users and stuff, and feeds will follow shortly, it's all built just need documentation.

https://endpoint.hey.cafe/api/conversation_info?query=utdtls...

Nope all made by me, all in one Javascript block for the entire front end.

Here is an example of larger content. It supports auto embeds from Twitter, Youtube, Twitch and more. If you load anything not self hosted it will ask for permission before embedding content from outside the domain.

https://hey.cafe/conversation/j8olwfmlbpmlloww4yh4bxfz9

Um, more like Twitter and FB had a baby and removed the ads and tracking.

Yes I built it, and I hope people like it. It still has a lot of stuff on the roadmap and supports thins like website embeds that I use on my personal site https://anthonys.space and a lot of formatting options for posts, including Pro users able to post really long content.

Still lots to do and lots on the roadmap but suggestions and feedback are helpful.

Oh another key thing is the site is built using a single Javascript block, no trackers and no ads anywhere. Clean as it can be.

Hey.Café is a social network built around communities called cafés. Has lots of formatting options on posts similar to Markdown. It's also really really fast.