One of the most enjoyable challenges during the development process was ensuring the PDF documents are temper proof (sealed). Traditionally, some companies charge exorbitant fees, up to $10,000 for a 1-year certificate.
However, through meticulous research, we discovered a three-year certificate for a fraction of the cost, like $600. It offers the same level of functionality.
I had to contact every company from Adobe Approved Trust List: https://helpx.adobe.com/acrobat/kb/approved-trust-list2.html
To set up the necessary Hardware Security Module (HSM), we opted for Google HSM, which costs just a few bucks a month.
it's because these products aren't consumer products - they are business products. You often won't find business products run off ads, because business products have a value proposition which is positive, and thus the business would pay for it.
One of my ideas what to create Atlassian plugin that would allow to use custom domain.
I did some PoC. With heavy http proxing/rewriting it would be somehow doable but too fragile. I have skipped that.
Basically all of this is matter of Atlassian priority. If most of clients can accept current state then why bother?
It is good market, there are niche needs. Most of work is web development not rocket science.
Actually plugins for Jira / Confluence is something well done by Atlassian.
They can not create single solution for all, but with plugins? It is close.
> File name extension. This is a very common one. "cgi", even ".html" is something which will change. You may not be using HTML for that page in 20 years time, but you might want today's links to it to still be valid. The canonical way of making links to the W3C site doesn't use the extension.(how?)
Since I switched from ASP to PHP (2008), I avoided file extensions in page URI in most cases, and instead placed every page into its own folder.
This is compatible with every web server without using rewrite rules.
When I switched from PHP to static generators (2017), most URIs continued working without redirects.
To be fair, it's the OP that chose to use the URL with the extension. However, you could say WC3 could've disable their servers from automatically creating URLs with file extension if they wanted to follow this.
Right? Just close your e-mail client. Or you can set up recurring timer or calendar event. Check once in the morning, after lunch, and perhaps before you end your work day.
