13:31 ancient articles
that have been lurking in my email for far too long
unclear how successful gig econymy has been overall: postulated to have erodded 100 years worth of worker protections
passion economy: minting via personal passions and direct user relationships! leverage 'tools' of the creator economy to inject more emotion into their work? 1,000 true fans really is true!
capital: evolution to ownership of data that enables productivity - knowing human behavior allows for better catering to it, so data ownership is in aggregate more valuable than any one time transaction is - allows optimizing for the transactino model that will best nsure success. several large firms have aggregated control of user data, which is probablu bad
oversaturation of creators: only the platforh wins in the long term, really, as vast majority of creators are lust contributing to platform usage and network effects.
creator incomes are just as volatile as gig workers - unclear whether it's a safe path forward.
platforms as intermediaries for creators directly own, control and regulate means of income for creators; this is probably not healthy, as the network optimizes for the best vales for the network rather than for the rights and liberties of any individual. in short - centralization and consolidation of platforms is bad!
distributed channels for audiences that communicate directly to consumer: email, rss feeds, direct monetization for end users.
vital to be able to control the platforms you publish on! anything less is just beholden to another company, organization or platform.
improved product design: provide transparency to creators regarding their successes and failures, demonstrating to them precicely how and why they see the numbers that they do.
can build wellness tools into the platform! like time tracking and budgeting tools or mental health resources.
linus on the future of the browser?
thesis: we need a medium for thought rather than just a tool!. with some ideas attached
building a medium requires protocols, standards, platforms - we're stuck on cli when we need gui! personally i think any new protocol or tech must be bootstrapped with existing utilities first, and available in the browser, before transitioning to anything more sustainable and independent.
a web browser should be optimized for browsing semantic information - not just tools and apps - and the ability to organize this information should be first class
no new or interesting insights here. i wonder if i should start writing; these concepts are not new to me and i've already traed these thougnt processes, though on the tool development end i am nowhere near as prolific. maybe i've done too much research and not enough hard work.
https://alyssax.com/: who is this?? how is she so prolific?? i have to get there!
the shangri la diet
just eat food that makes you desire to eat less of it; enter the olive oil diet http://www.aaronsw.com/weblog/miraclediet
keeping wiki structure intact doesn't work for me; it's nice to stamp long form articles in at some point, but i typically prefer free flowing ideas over trying to squeeze everything into a box on the wiki. i ultimately do not want to perform the maintenance work required to keep that up - i just want to spew text into a file and have the computer automate the rest. or is that so hard? is that truly what i want?
some ideas, borrowed from someone else
organized and extensible generic document storage and protocol? make it federated? basically copy google drive, federate it and open source it, then keep going with things taht would never be considered a google business priority. this drifted into my idea instead, but the poiet stands that there is potential for one!
automated cms to remove things you don't like from socials and only allow interactions with the parts you do like!