Hacker News new | past | comments | ask | show | jobs | submit | elemcontrib's comments login

Slightly tangential but perhaps somebody could answer this question:

So having decided that rather than trade as a fictitious company and go the "personal brand" route, I'm interested to know who has successfully sold their own desktop apps from a website with their personal domain eg. JoeBloggs.com. Do buyers really care so long as the software meets their requirements, or does the psychology of a trading entity really affect peoples' appetites to purchase?

Reasons include authenticity, the ability to self brand for freelance dev work, and being able to list ad-hoc products as I develop them without having to market each one separately.

Comments welcome, as well as success stories, or otherwise.


Corporate customers are allergic to one-person shops because software price considerations pale next to stability of your company. They care much more about being able to depend on an SLA than whether the software costs $499 vs $999.

In fact, they prefer paying too much for software because that impresses management and keeps budgets increasing.


I'd keep it separate just for liability reasons. Also if it fails and you have to go back to a normal job you may want to obfuscate that part of your CV, that's going to be easier to do if you presented yourself as an organisation.


How does having Bitcoin be a software project with innumerable contributers make it a secure, distributed store of value? Just asking.


How does it make it not a secure, distributed store of value? Just asking.


The fact that the software behind it is a centrally controlled project?


First, it's important to understand that Bitcoin is fundamentally a protocol, not a piece of software. Bitcoin Core is merely the most widely used implementation of that protocol.

Second, would you apply the same line of reasoning to other popular open-source projects, such as Linux or PostgreSQL? Do you believe that those projects are equally insecure?


Thank you for clarifying that Bitcoin is fundamentally a protocol. However, if the network has de facto settled on a certain implementation, then what does that say?

Linux and PostgreSQL et al would exhibit characteristics of whatever their respective gatekeepers let in.

Btw, I'm not making a definitive statement about Bitcoin's insecurity per se. I'm rather via process of invalidation querying how the ubiquitous claim, that it is an unhackable, secure (basically untouchable) money alternative to fiat, actually holds.


It has held for the past 15 years. You are also free to inspect the source code of Bitcoin Core and/or study the protocol for flaws.


It's basically a group of devs calling the shots. Like any open source project code audits could well be an afterthought with post-incident remediation. Also the average Bitcoin user isn't going to download the source code and inspect it. They just trust that these devs are and always will act in their best interests.

This reminds me of an incident at the beginning of the Ukraine situation when the owner of a heavily used library used in many prominent upstream projects decided one day that his ideological position was so strong that he would initiate a supply chain attack in his code targeting Russian users by IP or something. There was nothing to stop this. That's the nature of open source software.

It's neither trustless nor regulated.


You just need one honest pair of eyes watching the code to sound the alarm. Even if the Bitcoin core developers conspired to sneak in malware, it might affect a few users but would be quickly detected and wouldn't impact the Bitcoin network/protocol itself.



I'm in the beginning stages of a write-up about it for an SPA. It would be useful if there were more current working examples online like the other frameworks to demonstrate how to use the library. It's a swiss army knife and the shortage of real world examples and patterns of its use in modern use cases eg. components, as an spa, etc is a real shortcoming right now. https://fj.indiewp.com/jsrender-and-jsviews-for-your-next-sp...


A return to purpose


My take on it is that if someone is genuinely interested in signing up for a service then they'll verify their email as part of the signup process. I enforce verification at signup. This eliminates 100% spam. It becomes a policy decision and not a technical one.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: