I would claim that Neocities should specifically not add social networking aspects. If someone wants social features on their site then they can copy/paste snippets of HTML/CSS/Javascript into the static site.
I think the difficulty with doing that is that social network integration is almost exclusively focused on consumption. At the lowest end of the spectrum are the widgets containing information from within the network. That's a reasonable way to direct users from a Web site into a network (eg. a user visiting a newspaper's site may go and visit the newspaper's Facebook page) but it's useless at getting people from the network to go to a site. Nobody goes to Bob's Web site to check his Facebook status; they do it from within Facebook.
The situations where this can work well are:
1) Consumer APIs with machine-readable results. The simplest mashup, data visualisation, interactive game, etc. can be made really interesting when it has real-world data to play with. As an example, one of my first programs was a balls-on-springs physics simulation, but I drove it with artist similarity data from last.fm (audioscrobbler at the time).
2) Producer APIs allow data to persist once the static page is closed. This could be as simple as posting a highscore from a game, all the way up to posting the result of a Web-based creative application. What programmer didn't throw together a "paint program" as soon as they found out how to get the mouse position and make a line on a canvas?
I think the difficulty with doing that is that social network integration is almost exclusively focused on consumption. At the lowest end of the spectrum are the widgets containing information from within the network. That's a reasonable way to direct users from a Web site into a network (eg. a user visiting a newspaper's site may go and visit the newspaper's Facebook page) but it's useless at getting people from the network to go to a site. Nobody goes to Bob's Web site to check his Facebook status; they do it from within Facebook.
The situations where this can work well are: 1) Consumer APIs with machine-readable results. The simplest mashup, data visualisation, interactive game, etc. can be made really interesting when it has real-world data to play with. As an example, one of my first programs was a balls-on-springs physics simulation, but I drove it with artist similarity data from last.fm (audioscrobbler at the time). 2) Producer APIs allow data to persist once the static page is closed. This could be as simple as posting a highscore from a game, all the way up to posting the result of a Web-based creative application. What programmer didn't throw together a "paint program" as soon as they found out how to get the mouse position and make a line on a canvas?