I'm not 100% it's the right PW. I'm not logged in anywhere else. The cookie on my voat machine was lost.

Alright delete that comment. You need 10 or 20ccp to send PMs. If you can remmber some of he old PMs you sent to anyone and give permissions for @Puttitout to look at them maybe that can help establish your identity, because thats the main thing he'll be worried about. Do you think someone hijacked your account or it's not like that?

Any thoughts to registering the voat.com domain and setting up a redirection to voat.co ?

May I suggest that when there is a minimal viable beta, create an AWS account and deploy on minimal hardware - try to keep it on the free tier - for the first year.

I work with PHP/MySQL/caching/templates all day, but am pretty familiar with other techs including server setup. If there's anything I can do, someone shoot me a message.

As far as saving $$ - getting of MS hosting is a start, and then I think we can also save on system resources with the right caching approaches in place.

To someone who knows - what currently takes the most resources in the app - which actions when taken on the site take up the most system cycles...I'd be interested to know, I'm pretty good at optimizing the shit out of stuff...

Glad to help.

Best game. Ever. Period.

Right that's why I think a sub and a clear focus of:

1: This is what we are doing

2: These are the listed things we need done to achieve that

3: Assign people to those things as they put their hand up

At the moment reading this thread it seems like a lot of talk and even a few things happening but everyone needs to be pulling in the same direction. Voat needs to be specific in exactly what it needs, then we can point people to how they can help.

Slack is more useful for planning like this, as it is a different style of platform. Conversations, especially those involving more than 2 people, are far faster in a chat format than they are in the format of voat

Li li li li lick my baaallls

Fuzzy would a "semi-official" sub made just for this project be a good idea? It seems like there's a lot pulling in different directions and it would provide some clarity as to how its progressing and along what lines people should be focusing. If you're in the loop with @PuttItOut about this, maybe suggest that. I know little about coding but management of teams is an important aspect of any project, particularly where egos are involved.

It would also provide the transparency some are looking for and a place for those on slack to report back to.

plumbus you watch rick amd morty.

Elaborate. SQLAlchemy generates native SQL.

And more portable. Not being locked into one vendor means you can always move to the cheaper hosting company.

Does the migration also mean migrating off Azure?

That's about as much as I ever learned about how to play too, but I kept those servers alive for as long as I was able, until corporate made me shut them down.

Given @PuttItOut basically adopted the solution I suggested to the Slack and I got frozen out...eh. @vmlinuz is right about the problem with the slack group's behavior.

As long as we can leverage Linux hosting for the DB to reduce costs it doesn't matter to me what DB we use.

I only know some of the words used in this thread. with that said, thank you to everyone helping to keep voat alive.

get on slack

Whatever you do, don't let kikes EVER take the reigns. They will kike your shit up fam.

Voat isn't good for instant communication like a chat.

Why did nobody ask for this help six months ago?

Do you have anything useful to add to help this community project?

Good to see you still around and active Fuzzy

Don't be a tool. Slack allows for real-time discussions and sharing.

I’d consider the first step literally just commenting out areas of code that have build issues ...

I would not mind losing some features for a while, if it would speed up the process of keeping voat alive.

The slack mentioned in the other comments has already made some progress on this. Although I believe the community consensus was to switch to MySQL but supporting PostgreSQL is doable as well.

There's also been some serious efforts made to get Voat running in a Linux container so you can move Voat off Azure and take advantage of cheaper Linux based cloud hosting without having to necessarily rewrite any code. You could save 30-40% on hosting costs alone by getting off Azure.

A few members were also discussing caching options which could also bring down server load considerably.

We are here to help but need your insight and leadership to keep everyone focused on what needs to be done.

If we have a better idea of resource usage and your current scaling methods we can also assist with cost analysis which is my particular speciality.

You're not alone, and we are here to help.

I'm seriously not a fan of any ASP/Microsoft platform, but I have to hand it to you for the reasons behind not doing a platform rewrite. Can't say you are wrong on any of those points.

I know hivemind already posted this, but we want to ensure visibility, so,

Since the day of the angel announcement a slack group as been working on doing the requisite work to port voat over to open platforms, with not insignificant progress.

(invite link)

Putt. If/when you join, I'll have the guy managing our trello add you as admin, and ill add you as team admin as slack, but I'll want a PM here on voat to ensure we aren't giving it to a troll.

Sorry, I have no useful tech knowledge to share, but I would just like to thank you Putt for all your toil :)

Just a heads up, there is an active effort on slack to accomplish this. So far we have managed to migrate the DB schema to MySQL and deployed it to a container for dev purposes. We also have members working on getting the codebase to run on Mono/.NET Core with limited success.