This is a draft of features that creating a backend will provide. This is a hi

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-ur

I'm biased, but I agree with <a class="user-mention notranslate" data-hovercard-

Draft Overview Of Features A Backend Would Provide about freespeech HOT 3 CLOSED

merkie commented on August 11, 2024

Draft Overview Of Features A Backend Would Provide

from freespeech.

MRSessions commented on August 11, 2024 2

@fatfingers23 What are the possibilities of adding a .NET Core backend?
I have some experience with Azure Storage Blobs, I think that could be a good place for image storage.

from freespeech.

ariadnimac commented on August 11, 2024 2

The keyboard could change according to which words the user uses the most, so that the most used words are at the top and easier to find.

from freespeech.

IanKnighton commented on August 11, 2024 1

I'm biased, but I agree with @MRSessions, a .Net Core backend would be a pretty good solution.
Azure AD B2C would be a good option for the Account Creation/Storage. There would need to be some way of linking preferences to a user, but offloading the actual authentication and PII to Azure would alleviate a lot of compliance and security concerns. This could also be done through Auth0 or any other service out there, but I think the Azure approach is nice because you can centralize the management/secrets shared across applications.

from freespeech.

Recommend Projects