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

another one of these super-cool 'lets burn the planet for fun using generative AI' projects.

The planet has been here far longer than humans, and will be here far longer than humans, and has seen far harsher conditions too. Don't worry about the planet, worry about the humans.

Not to mention that descendants of DALL-E, and like, operating on fusion energy, won’t have the fragile climate dependencies that we do!

We are a spark. We burned bright. Our preciousness is enhanced by our temporal finitude. They will never forget us, safe in the cold storage of their historical archives!


worth it

There's this earthquake phrase in past tense:

> We felt like we had agency.


in german law it's even impossible to transfer copyright (Urheberrecht). There is but one way: inheriting. What can be transferred though is usage right - licensing.


I just found this explanation on the linked site:

Many Germans incorrectly believe that copyrights cannot be abandoned. The actual situation in German law is as follows:

"Nutzungsrechte" (literally "usage rights") include the rights of copying, modification, distribution, etc. These rights can be waived, as in other countries.

"Urheberrechte" (literally "originator rights") include reputation rights and generally cannot be waived. This protection against fraud, libel, etc. has nothing to do with whether something is in the public domain.

https://cr.yp.to/publicdomain.html


how is your tea different from https://opam.ocaml.org/packages/teash/?


Sorry for the less-than-useful reply, but I tried out most of the TEA TUI frameworks in OCaml and none of them worked very well or well updated.

I do not recall what problem I had with that particular one, but I ended up just using raw Notty in the end.


is the user base shrinking or why should we?

IMO pulsating, vivid stability is more important than growth.


glimpsed into it, looks fancy but find it apologetic. IMO it's double-standards to campaign against "the next datacenter from being built" without reducing personal usage and demand.

Individual frugality is the precondition for collective degrowth, both practically and morally. Otherwise you just open business opportunities for datacenter growth.

IMO both should be pursued, make one and don't omit the other.


The "Why RSS" doesn't mention why instead of RFC4287 Atom.


Name recognition mostly, but you can just call an Atom feed an RSS feed and no one goes to jail for it, so just use the name that gets the results you care about.


Hi thanks for this comment. I'll look into Atom a bit more for this tool. Heard a lot about it.


It was first and thus more broadly supported?


RSS came out in 1999, Atom in 2005. There's not a meaningful difference in support between the two at this point.


But RSS gained wide acceptance in that early period. Atom came along later and never seemed to gain as much usage.

People still think of "RSS feeds" and "RSS readers" even if some of those are Atom or at least offer Atom as an option.


It could still be true that more people publish RSS than Atom. But functionally 100% of readers have supported both for a long, long time now.


100% includes iTunes or Podcatchers in general where I hardly find documentation for but would be interested for (my) https://mro.name/radio-privatkopie/

Can you give me a pointer how to write the Atom podcast feed?


Podcasting is kind of a special case, since Apple's guidelines mandate the use of RSS [1]. So if you're publishing a podcast and you want to get into the Apple Podcasts directory, you have to publish a RSS 2.0 feed (as well as meet all their other extra requirements).

If you don't care about the Apple Podcasts directory you can publish an Atom podcast feed that will work with most podcatchers. The primary thing you do differently from a normal Atom feed is to use the `link` element with `rel=enclosure` to reference the audio file for each episode/entry.

    <link rel="enclosure" href="http://example.com/audio.m4a" length="100" type="audio/mp4" />
I wrote Splitflap, the valid RSS/Atom feed generator package for Racket [2]. Not many folks use Racket but you might find the docs a good resource on this sort of thing anyway.

[1]: https://podcasters.apple.com/support/823-podcast-requirement...

[2]: https://docs.racket-lang.org/splitflap/index.html


I have some like this http://rec.mro.name/podcasts/zuendfunk/broadcasts.atom (and .rss, too) which plays the audio nicely e.g. in https://miniflux.app but I remember having trouble with iTunes on MacOS and the Apple podcast iOS app.

But his is mostly try-and-error and merely no specs. Apple doesn't talk about atom AFAIK.

Racket is interesting, I'm into Ocaml, but create those feeds via https://codeberg.org/mro/internet-radio-recorder/src/branch/...


Hey thanks for your comment. Today I actually added support for this. If you make a markdown link to an audio file it will create an RSS enclosure. Including the file length (if it can be retrieved from header information).

[audio/mpeg](http://example.mp3)

<enclosure url='http://example.mp3' type='audio/mpeg' length='2273741' />


… and Aaron Swartz's "Building for Users: Designing URLs" https://codeberg.org/mro/ProgrammableWebSwartz2013/src/branc...


> And yet, no matter how you look at it, this can’t just be a simple coincidence.

why not?


for curiosity - what wisdom do you intend to draw from visualising relations of single gut bacteria? Or is it grains of sand in the sea? How many of them will you zoom into? Maybe clustering may make things feasible.


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

Search: