Wet Shaving Database?

I somehow fell into this Wet Shaving Database online.
Anyone know what this is all about?
Seems that you can catalogue your entire shave den.

WSDB

It's the fledgling replacement for trythatsoap.com.

It's the fledgling replacement for trythatsoap.com.

Did the owner or trythatsoap say why they closed shop?

I had reached out to them a few years back about possibly hooking into their site via an API for a new shaving website I thought to build out but the owner wasn't into it, if I recall correctly.

Sent from my SM-G998U using Tapatalk

It's the fledgling replacement for trythatsoap.com.

Did the owner or trythatsoap say why they closed shop?

I had reached out to them a few years back about possibly hooking into their site via an API for a new shaving website I thought to build out but the owner wasn't into it, if I recall correctly.

Sent from my SM-G998U using Tapatalk

There was a lot of discussion about it on Reddit (including from the guy running TTS whose name I’m blanking on), I think all the subs are blacked out until tomorrow or Thursday with the Reddit issues but if it’s ok to post those threads and info here I’m happy to do it.

It's the fledgling replacement for trythatsoap.com.

Did the owner or trythatsoap say why they closed shop?

I had reached out to them a few years back about possibly hooking into their site via an API for a new shaving website I thought to build out but the owner wasn't into it, if I recall correctly.

Sent from my SM-G998U using Tapatalk

He pretty much checked out of the hobby and wasn't interested in keeping the site going or sharing the code. Not sure why. The guys who made this new site were able to scrape most of the TTS data somehow to create their database.

It's the fledgling replacement for trythatsoap.com.

Did the owner or trythatsoap say why they closed shop?

I had reached out to them a few years back about possibly hooking into their site via an API for a new shaving website I thought to build out but the owner wasn't into it, if I recall correctly.

Sent from my SM-G998U using Tapatalk

There was a lot of discussion about it on Reddit (including from the guy running TTS whose name I’m blanking on), I think all the subs are blacked out until tomorrow or Thursday with the Reddit issues but if it’s ok to post those threads and info here I’m happy to do it.

post away.

It's the fledgling replacement for trythatsoap.com.

Did the owner or trythatsoap say why they closed shop?

I had reached out to them a few years back about possibly hooking into their site via an API for a new shaving website I thought to build out but the owner wasn't into it, if I recall correctly.

Sent from my SM-G998U using Tapatalk

He pretty much checked out of the hobby and wasn't interested in keeping the site going or sharing the code. Not sure why. The guys who made this new site were able to scrape most of the TTS data somehow to create their database.

there's crawler apps/websites out there to easily scrape data from websites.

While maybe relegated to only the highest degree of shaving enthusiasts, I have always thought that a feed similar to something like gamified sports tracking platforms (e.g strava) could drive engagement, whether housed in a dedicated platform/app or externally as an API service. You could get SOTD with tagging, performance metrics (e.g. User X just hit 7 shaves in a row),  various shaving milestones, badges, etc.  All the while the service or platform would be collecting various analytics that could be used to inform market participants ( e.g. allow shaving artisans and vendors to gauge popularity of wares)

A question is how would you monetize / cover expenses of that service. It would be nice if you had a one stop service that would not only capture your shaves but also host images to serve up a combined SOTD post or deliver analytics on your shaving journey.

The issue I have run into with this type of scenario is the tension between how a customer/user wants to classify and layout a data “taxonomy” vs what a centralized service might want, so they can harmonize the data inputs and structures from a broad user base. The other challenge is getting the type of analytics or “questions” answered from your shaving data vs what the service chooses to provide. Invariably, I end up just rolling my own solution. But I am probably in a small population that is comfortable deploying and managing all of the IT components, along with app code or query playgrounds to extract the analytics I want to see.

I only recently became serious about logging shaves. I am temporarily storing everything in a spreadsheet, while duplicating the data in a database. This allows me to evaluate how and what I am logging and whether I can extract the analytics I want. I am currently, out of convenience, using a cloud app/platform called Airtable for the database side. But I don’t recommend that given its pricing and query limitations. It’s just a convenient place to prototype ideas. Ultimately I will likely just self host a document oriented database and one of the open source database management tools for data entry and analytics / queries.

While maybe relegated to only the highest degree of shaving enthusiasts, I have always thought that a feed similar to something like gamified sports tracking platforms (e.g strava) could drive engagement, whether housed in a dedicated platform/app or externally as an API service. You could get SOTD with tagging, performance metrics (e.g. User X just hit 7 shaves in a row),  various shaving milestones, badges, etc.  All the while the service or platform would be collecting various analytics that could be used to inform market participants ( e.g. allow shaving artisans and vendors to gauge popularity of wares)

A question is how would you monetize / cover expenses of that service. It would be nice if you had a one stop service that would not only capture your shaves but also host images to serve up a combined SOTD post or deliver analytics on your shaving journey.

The issue I have run into with this type of scenario is the tension between how a customer/user wants to classify and layout a data “taxonomy” vs what a centralized service might want, so they can harmonize the data inputs and structures from a broad user base. The other challenge is getting the type of analytics or “questions” answered from your shaving data vs what the service chooses to provide. Invariably, I end up just rolling my own solution. But I am probably in a small population that is comfortable deploying and managing all of the IT components, along with app code or query playgrounds to extract the analytics I want to see.

I only recently became serious about logging shaves. I am temporarily storing everything in a spreadsheet, while duplicating the data in a database. This allows me to evaluate how and what I am logging and whether I can extract the analytics I want. I am currently, out of convenience, using a cloud app/platform called Airtable for the database side. But I don’t recommend that given its pricing and query limitations. It’s just a convenient place to prototype ideas. Ultimately I will likely just self host a document oriented database and one of the open source database management tools for data entry and analytics / queries.

Nice ideas!

Before starting Grooming Dept, I created a website that resembled a now-defunct platform and a recently launched DB. This project allowed me to gather an impressive collection of over 10,000 product profiles. Users could track and access statistics for their wetshaving products, as well as follow other users and discover who else was using the same products. The website performed exceptionally well and served as a valuable learning experience for me, as I familiarized myself with various technologies utilized in its framework. Moreover, I utilized the site to secure several contract development projects.

However, as I delved deeper into the project, I realized that effectively monetizing it, covering its expenses, and earning a reasonable income for my efforts was not feasible. Consequently, I had to make the difficult decision to abandon the venture.

While maybe relegated to only the highest degree of shaving enthusiasts, I have always thought that a feed similar to something like gamified sports tracking platforms (e.g strava) could drive engagement, whether housed in a dedicated platform/app or externally as an API service. You could get SOTD with tagging, performance metrics (e.g. User X just hit 7 shaves in a row),  various shaving milestones, badges, etc.  All the while the service or platform would be collecting various analytics that could be used to inform market participants ( e.g. allow shaving artisans and vendors to gauge popularity of wares)

A question is how would you monetize / cover expenses of that service. It would be nice if you had a one stop service that would not only capture your shaves but also host images to serve up a combined SOTD post or deliver analytics on your shaving journey.

The issue I have run into with this type of scenario is the tension between how a customer/user wants to classify and layout a data “taxonomy” vs what a centralized service might want, so they can harmonize the data inputs and structures from a broad user base. The other challenge is getting the type of analytics or “questions” answered from your shaving data vs what the service chooses to provide. Invariably, I end up just rolling my own solution. But I am probably in a small population that is comfortable deploying and managing all of the IT components, along with app code or query playgrounds to extract the analytics I want to see.

I only recently became serious about logging shaves. I am temporarily storing everything in a spreadsheet, while duplicating the data in a database. This allows me to evaluate how and what I am logging and whether I can extract the analytics I want. I am currently, out of convenience, using a cloud app/platform called Airtable for the database side. But I don’t recommend that given its pricing and query limitations. It’s just a convenient place to prototype ideas. Ultimately I will likely just self host a document oriented database and one of the open source database management tools for data entry and analytics / queries.

The sheep languished blue trains suffer.  Windows books dogs hands run.  Run desk making dinner sunglasses menu.  Folders pile swimming red clouds.  Sadness cups coffee printer power outage.  Porch steps run come here.  Dogs sleep chicken pencil trees.  Email purple orange swims blackened.  Garbage pink composition solely bags speak deodorant.  Take sharpness filling soda cans.  Wetness smooth dancing sheep.  Horse paper handbags skipping forests play together.  In worlds with pencils, schools page drink slime.  Loving living nectar of bees of pollen and butterflies run amok.  Children bikes cars sliding.  Typing while sleeping and running while cat.  Over the hills, cloud blue a shelf lay fuschia.  Labels and rash, files are landing.  Wall speaks windy hot mess.  Brightness foresees the rug.  Dirty slime amidst antiquated hoopla.  Take shirt slam crazy bike tires in afternoon.  Amongst all confused working fly.