Search
519 results for “jameshowell”
-
Necessity never made good bargain.
James Howell (c. 1594 - 1666) Welsh historian and writer
Paroimiographia [Παροιμιογραφία]: Proverbs, or, Old Sayed Sawes & Adages, “New Sayings,” 3rd Century (1659)More about this quote: wist.info/howell-james/16348/
#quote #quotes #quotation #qotd #jameshowell #proverb #bargain #desperation #necessity #need #requirement #tradeoff
-
A hungry man [is] an angry man.
James Howell (c. 1594 - 1666) Welsh historian and writer
Paroimiographia [Παροιμιογραφία]: Proverbs, or, Old Sayed Sawes & Adages, “English Proverbs” (1659)
[compiler]More about this quote: wist.info/howell-james/12061/
#quote #quotes #quotation #qotd #jameshowell #anger #discontent #dissatisfaction #hunger #resentment #temper
-
Burn not thy fingers to snuff another man’s candle.
James Howell (c. 1594 - 1666) Welsh historian and writer
Paroimiographia [Παροιμιογραφία], or, Old Sayed Sawes & Adages, “New Sayings” (1659)More about this quote: wist.info/howell-james/12025/
#quote #quotes #quotation #qotd #jameshowell #competition #conflict #cost #selfdefeating #selfdestruction
-
RE: https://fediscience.org/@jameshowell/115028024955832856
First week of classes, highest volume of email biannually, no big deal, thanks to #emacs and #mu4e
Don't hate me because I am efficient
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell Thank you! It was weird thinking back to that. Do you remember the XFree86 server that was built to run in low memory situations? Was it called Xtiny or something? #xwindows #xfree86
-
@jameshowell @blogdiva @ramsey @SrRochardBunson @sabogato
Millenarian eschatologists gonna #ImmanentizeTheEschaton
-
@jameshowell @blogdiva @ramsey @SrRochardBunson @sabogato
Once you grok that our modern culture, society, and values are a collection of semi-arid Mediterranean desert myths, #EverythingIsARemix starts to make sense.
-
@tusharhero @jameshowell May I add a different layer to that discussion?
I stopped using gated-community web forums like #reddit altogether: https://karl-voit.at/2020/10/23/avoid-web-forums/ 😉
-
@schuemaa @jameshowell This is what I use to interact with canvas with an org file. I use it mainly for pages and announcements (which covers 90% of my use).
-
@screwlisp @jameshowell @ramin_hal9001 @kentpitman
The point on radicalization at the beginning of the show had me thinking about how radicalization of humanity into diametric opposites seems inevitable today.
I wonder, if AI could trivially solve our climate crises 'tomorrow', could we overcome that polarization (as the enacting machines lack ego), or would the human stewardship still put us in some kind of political paralysis?
-
@screwlisp @jameshowell @ramin_hal9001 @kentpitman
The point on radicalization at the beginning of the show had me thinking about how radicalization of humanity into diametric opposites seems inevitable today.
I wonder, if AI could trivially solve our climate crises 'tomorrow', could we overcome that polarization (as the enacting machines lack ego), or would the human stewardship still put us in some kind of political paralysis?
-
@screwlisp @jameshowell @ramin_hal9001 @kentpitman
The point on radicalization at the beginning of the show had me thinking about how radicalization of humanity into diametric opposites seems inevitable today.
I wonder, if AI could trivially solve our climate crises 'tomorrow', could we overcome that polarization (as the enacting machines lack ego), or would the human stewardship still put us in some kind of political paralysis?
-
@screwlisp @jameshowell @ramin_hal9001 @kentpitman
The point on radicalization at the beginning of the show had me thinking about how radicalization of humanity into diametric opposites seems inevitable today.
I wonder, if AI could trivially solve our climate crises 'tomorrow', could we overcome that polarization (as the enacting machines lack ego), or would the human stewardship still put us in some kind of political paralysis?
-
@screwlisp @jameshowell @ramin_hal9001 @kentpitman
The point on radicalization at the beginning of the show had me thinking about how radicalization of humanity into diametric opposites seems inevitable today.
I wonder, if AI could trivially solve our climate crises 'tomorrow', could we overcome that polarization (as the enacting machines lack ego), or would the human stewardship still put us in some kind of political paralysis?
-
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
-
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
-
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
-
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
-
@randyridenour @jameshowell @greg @pymander No kidding! It took me forever to get the #O365 auth flow worked out, but #pizauth worked wonders with #mu4e.
Granted, I don't use email with or via #emacs, as I don't yet quite trust I won't wind up deleting everything on the server side. Plus, I have not yet sorted out the whole "everybody in the organization uses outlook calendar".
-
Arguable that cripples the usefulness (anyone checked #Magit, may have the same problem).
The suggested fix is inadequate at least.
A rather drastic fix would be that git itself maintains a list of trusted repositories (the ones it cloned or initialized itself), plus a UI to add/remove/gc from this list. then only executing content from these .git's and rejects everything else.
One could implement that for emacs alone, keeping a list of trusted git repos and reject git on untrusted one. But thats not a fix on the root of the problem.
-
Arguable that cripples the usefulness (anyone checked #Magit, may have the same problem).
The suggested fix is inadequate at least.
A rather drastic fix would be that git itself maintains a list of trusted repositories (the ones it cloned or initialized itself), plus a UI to add/remove/gc from this list. then only executing content from these .git's and rejects everything else.
One could implement that for emacs alone, keeping a list of trusted git repos and reject git on untrusted one. But thats not a fix on the root of the problem.
-
Arguable that cripples the usefulness (anyone checked #Magit, may have the same problem).
The suggested fix is inadequate at least.
A rather drastic fix would be that git itself maintains a list of trusted repositories (the ones it cloned or initialized itself), plus a UI to add/remove/gc from this list. then only executing content from these .git's and rejects everything else.
One could implement that for emacs alone, keeping a list of trusted git repos and reject git on untrusted one. But thats not a fix on the root of the problem.
