~sivers/sive.rs

ref: b2f50afe9f3a46f2848387525ab5fefcaad1de58 sive.rs/site/mhost -rw-r--r-- 5.6 KiB
b2f50afe — Derek Sivers ArtistData is gone 2 months ago
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<!DOCTYPE html>
<html lang="en" dir="ltr">
<head>
<meta charset="utf-8">
<title>Musician’s own website as definitive source of all info | Derek Sivers</title>
<meta name="description" content="Musicians spend too much time entering their data on multiple websites.  Filling out forms.  Uploading MP3s.  Uploading photos.  Entering dates and venues into concert calendars.  Pasting lyrics and bio.  All those stupid profiles scattered around the web, which of course will soon be outdated unless they’re constantly updated.">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="/style.css">
<link rel="alternate" type="application/atom+xml" title="Derek Sivers" href="/en.atom">
<link rel="alternate" type="application/rss+xml" title="Derek Sivers podcast" href="/podcast.rss">
<link rel="prev" href="https://sive.rs/hellyeah">
<link rel="next" href="https://sive.rs/hatenot">
</head>
<body id="article">
<section id="masthead">
<h1><a href="/" title="Derek Sivers">Derek Sivers</a></h1>
</section>
<div id="content">

<article>
<header>
<div class="blogparent"><a href="/blog">Articles</a>:</div>
<h1>Musician’s own website as definitive source of all info</h1>
<small>2009-08-28</small>
</header>

<p>
	Musicians spend too much time entering their data on multiple websites.
	Filling out forms.
	Uploading MP3s.
	Uploading photos.
	Entering dates and venues into concert calendars.
	Pasting lyrics and bio.
	All those stupid profiles scattered around the web, which of course will soon be outdated unless they’re constantly updated.
</p><p>
	Some outside sites say, “We’ll manage all your data!” — but I don’t want to go to yet-another-website to enter all of my data, and trust them not to go out of business.
	In fact, I don’t want to enter my info anywhere but my own website!
</p><p>
	So, I think the musician’s own “.com” homepage website should be the one-and-only place the musician ever has to enter their info.
	It should be the sole definitive source for their music, photos, bio, lyrics, calendar, blog, and especially their fan/friend/email list.
</p><p>
<strong>
	Then it’s the web hosting company’s job to spread that info other sites.
</strong>
</p>
<h4>
	How it works for the musician:
</h4>
<ol><li>
	Log in to your own website.
</li><li>
	Recorded a new song?
	Upload the master-quality audio file
</li><li>
	While it’s uploading, enter the song info: name, copyright, credits, lyrics, sample-start-time, etc.
</li><li>
	Booked a new show?
	Enter the date and venue info.
</li><li>
	Have a new photo or bio?
	Enter it just once in your site.
</li><li>
	That’s it.
<strong>
	You’ll never need to enter that info or upload that song ever again.
</strong>
</li></ol>
<p>
	You own all your data, and your web-host makes it easy to get a backup any time, like mailing you a USB drive.
</p>
<h4>
	Then your web-host can do the boring copying:
</h4>
<p>
	Your web-hosting company gives you some simple options.
</p>
<pre>
Do you want us to send this to...
[x] Facebook
[x] iTunes
[x] Amazon
[x] Instagram
[ ] Napster
[ ] Pandora
[ ] Spotify
[ ] ReverbNation
</pre>
<p>
	You’d give them your account details for the places where you already have an account, or at the others, they could create an account for you.
</p><p>
	Best of all: <strong>all of this extra service is included for free</strong> in your basic webhosting package, as thanks to you for choosing to host your website there.
	Assuming the standard web-hosting rate of $10-$20/month.
	They don’t need to take a percentage of sales or anything.
	The $10-$20/month webhosting fee has plenty of profit margin to cover everything.
</p>
<h4>
	How it works on the back-end:
</h4>
<p>
	For some websites, the distribution can be automated.
	The web host sends a server-to-server message to the remote company’s servers, adding the necessary info and files.
	This is how digital distribution of music already works.
</p><p>
	For other sites, there can be some quick simple human labor.
	An employee quickly logs into that site as you, with your permission, and uploads the song, info, photos or calendar, using the super-fast internet connection.
</p><p>
	The trickiest part would be copying the friend/fan list from multiple sites back into your one definitive master database of fans/friends.
</p><p>
	Because the company does it for dozens of clients per day, they can do it incredibly fast and cheap, so they don’t need to charge extra for this hands-on service.
</p><p>
	But where it gets really exciting is for the company to set up <strong>an open API where any outside companies can <em>pull</em> information directly from the source!</strong>
</p><p>
	That way, any new music websites could launch with instant access to thousands of musicians, with the most up-to-date info, and not need to host any of the audio, images, or text on their site.
	Everything be pulled real-time from your site using the API.
</p><p>
<strong>
	So if you changed a photo, removed a song, renamed a song, or even changed the name of the band, it would all be changed instantly on ALL sites, worldwide.
</strong>
</p>
<img src="/images/peacock.jpg" alt="http://www.flickr.com/photos/mmqb01/468351110/" />

<footer>
© 2009 <a href="https://sive.rs/">Derek Sivers</a>.
(
  « <a href="/hellyeah" accesskey="p" rel="prev">previous</a>
    ||
  <a href="/hatenot" accesskey="n" rel="next">next</a> »
)
<h1>
  Copy &amp; share:
  <span class="url"><a href="https://sive.rs/mhost">sive.rs/mhost</a></span>
</h1>
</footer>
</article>
<div id="comments"></div>
<script type="text/javascript" src="/js/comments.js"></script>

</div>
</body>
</html>