DESCRIPTION
Randomly generated values for forge ownership verification through
DNS TXT records was making development process complicated. Using
starchart instance's hostname for the TXT record's value is secure
enough for our use case.
This patch gets rid of all the code necessary to implement random
value challenges
SUMMARY
Renamed function parameters from "hostname" to "url" wherever a
url::Url is received
db_core::get_hostname is renamed to db_core::clean_url, better
describing its new implementation
forge_core::get_hostname is renamed to forge_core::get_url to better
describe its new implementation
URL PROCESSING METHODS
federate/federate-core
Parses URL and returns only the hostname
db/db-core
Parses URL, cleans it by removing path and query parameters and
returns the end result
SUMMARY
Renamed function parameters from "hostname" to "url" wherever a
url::Url is received
db_core::get_hostname is renamed to db_core::clean_url, better
describing its new implementation
forge_core::get_hostname is renamed to forge_core::get_url to better
describe its new implementation
URL PROCESSING METHODS
federate/federate-core
Parses URL and returns only the hostname
db/db-core
Parses URL, cleans it by removing path and query parameters and
returns the end result
DESCRIPTION
If user hasn't configured a profile photo on their forge instance,
it would point to the default photo of the forge instance, which
might be the same for all users without a profile photo on that
forge instance.
DESCRIPTION
add_user
Adds new user to DB. Implementers must ensure username
uniqueness scoped at forge instance level. When applicable, HTML
link to profile photo may be stored as we..
user_exists
Checks if a user exists in database. Optionally provide hostname
of forge instance to get forge-specific results.
