It seems to me that copyright doesn't exist anymore as a reasonable notion and effective right for an individual creator--A.I. being the final stake through the heart
> What used to look professional now looks generic. What used to look weird now looks human.
> The signal you want to send isn’t “I spent effort on this,” because that signal is now cheap to fake. The signal you want to send is “a human actually wrote/made this.” That one currently costs almost nothing to send, because so few people are sending it.
or, in other words ...
"when the going gets weird, the weird turn pro" --
From Fear and Loathing in Las Vegas (1971) by Hunter S. Thompson
P.S. so, was this, elegantly composed, brilliantly thought provoking, comment sufficiently Weird enough?
Haha tricky one. Presumably AI will get better at mimicking humaness - including being weird when called for. Then we'll have to exhibit increasingly strange and divergent qualities in order to signpost our biological origin?
> Good documentation includes background and decision information that cannot be derived from the code. It is hard to imagine any foreseeable software or robot that could collect this information from the people involved with a programming project—at the very least it must understand natural language, which is still the Holy Grail to the AI community.
Re-reading this short essay (after many years) got me to wondering if those of you using AI coding assistance tools are using them to both analyze and document existing code (i.e. non AI gen'd code but AI gen'd coments/doc for humans to read) or only transiently (e.g. for your own quick understanding or to help the AI whip up an API etc)
I also (humorously?) wonder if any of you have automated AI using the git ~blame/history to email the humans who wrote some code asking for their rationales (or perhaps complaining?)
> "People think they want to interact with a robot that totally mimics a human, but they really don’t," Simmons says.
There were those used to try hard, carefully yet hopefully, to learn how robots, computers and "artificial intelligence" might benefit or harm people, especially for those with special needs.
But now I think we're in a harms race.
[FYI, Proto was a magazine published by Harvard Medical School's teaching hospital, Massachusetts General Hospital, from 2005-2022.]
> Maybe nobody will read it. These comments are now many hours old and HN has a way of walking away once they have had their turn shouting into the void.
All that is gold does not glitter,
Not all those who wander are lost;
The old that is strong does not wither,
Deep roots are not reached by the frost.
> March 15 there were 1,251 updates [from feed of small websites ...] too active, to publish all the updates on a single page, even for just one day. Well, I could publish them, but nobody has time to read them all.
if the reader accumulates a small set of whitelist keywords, perhaps selected via optionally generating a tag cloud ui, then that est. 1,251 likely drops to ~ single page (most days)
if you wish to serve that as noscript it would suffice to partition in/visible content eg by <section class="keywords ..." and let the user apply css (or script by extension or bookmarklet/s) to reveal just their locally known interests
Kudos on your site effort and I immediately see your point.
In fact I took your topmost entry with no helpful site/update tags and dove in a little to try to understand why a RSS friendly blogger might not be passing along ~ tags for better reader discovery.
Turns out my scarce info test case blogger has a mastodon that immediately lists all these tags about himself [I've stripped it down] ...
#FrontEnd Developer #CSS
#Halifax #London #Singapore
Technical writer and rabbit-hole deep-diver
Former Organiser for https://londonwebstandards.org & https://stateofthebrowser.com
Interests: #Bushcraft #Outdoors #DnD #Fantasy #SciFi #HipHop #CSS #Eleventy #IndieWeb #OpenSource #OpenWeb
I conclude if he knew such site and post tags getting to RSS would be of use, he'd probably make the tiny effort to wire the descriptions.
Nonetheless I merely crawled links for a minute to found this info, so I imagine something like the free tier of the Cloudflare crawling api might suffice over time for a simplistic automated fix to hint decorate blog sites.
I mean, given that we're not trying to recreate pagerank, but just trying to tip the balance in favor of desirable initial discovery.
Crawling related sites for tags could work (open graph tags on the website are another good source). I'm wary of mixing data across contexts though. A blog and a Mastodon profile may intend to present a different face to the world or could discuss different topics.
While XML/XHTML aren't spec'ed/evolved to support your fun font sans attribute challenge, certainly modern html does ...
<p>
<style>
@scope { font-family: "Arial" ; }
</style>
Prospero: Where in the world is my teapot? Hello? I'm waiting!
</p>
I know one could argue that that css rule property is essentially an attribute, but it illustrates, like XML plists[1], that one can define the tags arbitrarily to have their content be meta upon sibling/nested content, subsuming attributes' role.
To wit, it seems to me a style issue.
[1] Apple has long used XML plists for data ~ interchange or even archival storage such as .webarchive (ie just a plist flavor). Of course they soon added a simple binary version to compress out some redundancy and encoding waste.
They used an XML nested tag approach, not attributes. Maybe not well rounded pegs and holes but it has worked for them on a large scale over a long time.
https://daringfireball.net/preferences/
reply