News for hackers. Stuff that matters.

ILIWYCMBgPicCha

Re:Ask HN: List of Subdomains to Reserve on Tuesday March 05, 2024 @04:20AM (#39601104)
Yeah, using a different domain isn't a bad idea. I had considered it, but I know slack doesn't do it. (I also know I'm not Slack).

There was a service I used some years (decades?) ago that let users choose from three or four domains that they owned. I could always do that in the future, too.

Re:Ask HN: List of Subdomains to Reserve on Tuesday March 05, 2024 @04:16AM (#39601073)
Thanks! I also found this list:

https://github.com/rbsec/dnscan/tree/master

Has entries for the most popular 100, 500, 1000, and 10,000 subdomains.

Re:Ask HN: List of Subdomains to Reserve on Tuesday March 05, 2024 @04:15AM (#39601066)
Good point. I am already checking against the naughty-words list from here:

https://github.com/LDNOOBW/List-of-Dirty-Naughty-Obscene-and...

Ask HN: List of Subdomains to Reserve

One of the features I am working on for my app (https://bigpicture.site) is the ability for each customer to have a custom subdomain in their url (similar to slack where each workspace is in the form of {name}.slack.com.)I understand the technical details of setting up the wildcard subdomains and handling it, but I am curious if there is a canonical list somewhere of subdomains I shouldn't let...

( Read More... | 10 comments | 2 points | on HN )
Re:Ask HN: Support / Bug fix Issue workflow pain points on Sunday March 03, 2024 @07:22AM (#39580402)
Keeping linked tickets seems like the best practice to me. Especially as organizations grow, a single reported issue could wind up being work tickets for multiple teams, and even make it into product management roadmaps for longer-term fixes.

Sometimes a bug will have a short-term fix to stop the immediate pain, but also have a long-term fix that might include re-working an entire feature.

Using Jira (or other similar app's) linking features is the easiest way to keep track of these dependencies.

To use your example, the individual customer who reported the issue wants to know the status of the ticket "Customer Y says Screenshot button isn't working", and hopefully there is a self-service way for them to get that information. Whereas, all customers will want to know (likely as part of some relase notes) that "Screenshots in Safari are now Supported."

It is an interesting idea. I can see this newsletter being of use to product managers and the like who have to do competitive analyses.

Sometimes it is hard to get feedback on B2B SaaS apps, though. A lot of them don't offer free trials, and even if they do, you are not using them at scale, so might not see their power.

A lot of times, buying decisions also don't come down to the usability of the product, but of other less apparent aspects, such as the trust and health of the company. Support contracts, implementation hand-holding, the cost of consulting time, ramp-up time, time to live for a customer, total lifetime cost, etc... all these things (and more) get factored into buying decisions and should be included in rating a B2B SaaS.

Gartner performs this kind of analysis across a range of industries, and has certain rubrics they use to analyze products, and the health of the businesses that own them.

It would be interesting to know how you intend to review and rate the products.

Maybe an idea would be to find customers of these products and interview them on their experiences?