No newlines before content in autogenerated markdown

This commit is contained in:
JP Hastings-Spital 2024-05-10 08:42:31 +01:00
parent b729c52122
commit 796692cd5d
17 changed files with 31 additions and 21 deletions

View file

@ -30,7 +30,6 @@ tags:
- biology
- curious
---
I really enjoyed reading about dopamine, desire and pleasure here! Its worth a read, even if it slightly veers into the “how to abuse this knowledge for personal gain with your new product” space.
Ive been (ha!) pleasantly surprised by how this article pulls lots of different concepts — half-understood by me — together. Ill be using it to try and provide motivation for myself while doing things that wont pay off for a while (hello 2023/24 tax return).

View file

@ -16,7 +16,6 @@ references:
tags:
- parenthood
---
What a wonderful read! Im not a parent (yet?) but I found myself eagerly reading every section here, despite this articles length!
{{< friend "ap" >}} (the author of this article), his partner, and their child are all good friends, and Ive been lucky enough to see slivers of this journey theyve been on—I can tell theyre all loving it (even the crappy days!)

View file

@ -14,7 +14,6 @@ references:
author: Lily Scherlis
tags: []
---
An extremely interesting article that helped me realise how different my definition of what “boundaries” are seems to differ from what contemporary usage is!
For me, a personal boundary is a pre-negotiated _promise_, not a _demand_. “These things hurt me, so if you end up doing them/I end up in that position (irrespective of intent or blame) then I will probably take these actions to protect myself.”

View file

@ -16,7 +16,6 @@ tags:
- creativity
- self-help
---
I really enjoyed skimming this article! Its too long for my distracted brain, but Ive often thought of “becoming bored” as a part of my creative process. I think thats part of isolating myself from expectations in much the same way as called out here.
This has also put me to thinking about raising kids; how to ensure theres always *some* time without peer/social pressure (ie. the absence of consumption devices, like phones with apps)

View file

@ -14,7 +14,6 @@ references:
tags:
- measurement
---
As ever, a great read from DynoMight! I particularly enjoy the assertion on the burden of proof being on the expert to show the flaw in a simpler proof (that disagrees?) with their own more complex one.
### Highlights

View file

@ -13,7 +13,6 @@ references:
tags:
- tech
---
An interesting take on why the internet can feel soulless, and some implied ways to counter that.
Slightly strong on the “back in the good old days” vibes, but a valid critique of search engines as a remover of mystery. Taking things for granted (“the advert to any question is at my finger tips”) has definitely removed the humanness of information for me.

View file

@ -17,14 +17,12 @@ tags:
- homelab
- tech
---
A concise and smart article talking to those of us interested in offering hobby networked services to others.
Im still in the mindset that a form of fully decentralised systems could overcome many of the issues mentioned here. My current bet would be on client-side web applications (or just websites) served from content addressed stores (like §IPFS), storing data primarily on local machines (think [fission.codes](https://fission.codes) and the §LocalFirst movement), is going to be a fruitful route.
Ill be looking forward to the next article on the challenges with end-to-end encryption (E2EE)!
### Highlights
> Good backups are:

View file

@ -14,7 +14,6 @@ references:
author: dynomight
tags: []
---
I fit the eNxP model by this article's assertions, and it feels representative enough to be useful. I like the idea of these tools to label & understand yourself _particularly_ because you can figure out where you _don't_ fit the model/where the label _isn't_ useful.
```plain

View file

@ -15,7 +15,6 @@ references:
tags:
- ai
---
Strong agree here. Until we are able to feel “seen” by something non-human well always need colleagues and peers in jobs, or the humans will burn out, leave that job, and take their tribal knowledge with them.
There will still be many companies that do this anyway; the number of “news” sites that have already replaced writing staff with LLMs is evidence enough. Hopefully the human connections people reformed through/after the pandemic lockdowns will give the disenfranchised a direction that brings the next pendulum swing a bit nearer though.

View file

@ -12,7 +12,6 @@ references:
tags:
- words
---
I love creating or finding words for niche (or expanding) concepts and areas. These highlighted ones are particularly great!
### Highlights

View file

@ -13,5 +13,4 @@ references:
tags:
- color
---
An excellent explanation of colourspaces and their uses today.

View file

@ -17,7 +17,6 @@ references:
tags:
- tech
---
This is an inspiring (and well thought through) approach to a problem on a lot of folks minds after the XZ attack.
I wonder how this would _actually_ come into reality though. Its easy to justify “accept 0.1% of revenue”, but I think thatd get very challenging when looking internationally. The UK (should) care about Open Source maintainability enough to start an institute like this, but which companies could they squeeze to get the funding? Almost all large tech companies are (legally) based elsewhere.

View file

@ -0,0 +1,27 @@
---
title: Slop is the new name for unwanted AI-generated content
date: "2024-05-09T16:03:02Z"
bookmarkOf: https://simonwillison.net/2024/May/8/slop/
references:
bookmark:
url: https://simonwillison.net/2024/May/8/slop/
type: entry
name: Slop is the new name for unwanted AI-generated content
summary: 'I saw this tweet yesterday from @deepfates, and I am very on board with
this: Watching in real time as “slop” becomes a term of art. the way that “spam”
…'
tags:
- ai
- words
---
I will be using this word from here on! Unreviewed AI-generated drivel is now “slop”.
### Highlights
> the way that “spam” became the term for unwanted emails, “slop” is going in the dictionary as the term for unwanted AI generated content
---
> sharing unreviewed content that has been artificially generated with other people [is _rude_](https://simonwillison.net/2023/Aug/27/wordcamp-llms/#personal-ai-ethics).
I can absolutely get behind this. Its rude when you impose your world on other people without at least some consideration, and auto-generated _slop_ fits that definition perfectly.

View file

@ -15,7 +15,6 @@ tags:
- comedy
- communication
---
I love this approach to replying to someone whose message youd rather not handle directly!
It sits very closely to the advice I gave a lot to aspiring staff engineers: ask a question that assumes the outcome youd like, and see what happens 😁

View file

@ -15,7 +15,6 @@ references:
author: Julie Zhuo
tags: []
---
I enjoyed this articles passion for _being alive_, I think theres a lot of similarity to a previous articles [obviousness](/tags/obviousness), and putting ourselves in emotionally challenging positions sometimes.
I plan on taking some every day risks this year & always.

View file

@ -16,8 +16,6 @@ tags:
- curious
- grief
---
A superb read, especially for me as I look for more depth in life.
I think I've certainly trained myself for a frictionless existence, and have (up until the last few years) tended to avoid difficult thoughts — but I feel so much richer for embracing them!

View file

@ -125,8 +125,8 @@ func outputArticle(article Article, outputDir string) error {
return err
}
fmt.Fprint(hugoPost, "---\n\n")
fmt.Fprintln(hugoPost, linkHashtags(article.Annonation, fm.Tags))
fmt.Fprint(hugoPost, "---\n")
fmt.Fprintln(hugoPost, linkHashtags(strings.TrimSpace(article.Annotation), fm.Tags))
if len(article.Highlights) > 0 {
fmt.Fprint(hugoPost, "\n### Highlights\n")
@ -206,7 +206,7 @@ type Article struct {
OriginalURL string
OriginalSummary string
OriginalAuthor string
Annonation string
Annotation string
Highlights []ArticleHighlight
Tags []string
}
@ -396,7 +396,7 @@ func parseResponse(body []byte) ([]Article, string, error) {
BookmarkDate: bookmarked,
PublishDate: published,
Highlights: highlights,
Annonation: annotation,
Annotation: annotation,
}
for _, label := range sr.Labels {