@technotramp could I share a little of your Unexpected Tracks as the music for my show this week? (I talk about lisps and smolnet community news, while sharing awesome underground music of people I meet). Is there a big ipfs music scene? You are the first one I encountered.
I'm enjoying Honeycomb -> Funky Cat right now. I once had some bubble gum from Japan that had the words "highly technical flavor" printed on the packaging which this puts me in mind of somehow
@lispi314
I absolutely agree with you on all counts, which is why this inversion of my expectations is shocking for me.
I guess we could go on to pivot the conversation and rethink our way to Edge Computing.
But sharing compressed original jams in a precooked virtual machine player in the modern Deep Web seems awesome to me and something I didn't expect to see (speaking as #gopher).
Google is trying to put the web in a cage in the same way they put your devices in a cage (Android, ChromeOS).
There’s one really easy, simple and efficient way to fight them: uninstall Chrome/Chromium, use #firefox
Do it. Now.
– But I prefer Chrome because of…
If you are not ready to sacrifice a little comfort (so little, Firefox is great) to save the web, then you don’t deserve a free web anyway. You are part of those killing it.
@reiver While I adore Gopher’s plaintext “figure it out on a typewriter” creative restriction, Gemtext doesn’t feel like a legitimate creative restriction to me, and doesn’t seem justified compared to taking a hatchet to JavaScript, particularly XmlHttpRequest. I don’t really see a comfortable line I can draw that brings in certain elements but not others. I prefer moves that exactly turn HTML pages back into documents again, I guess.
If markup even barely starts to have semantic meaning in the document, there goes the avalanche. Even full Markdown itself can quickly bring about a feeling of dissonance and then a kind of feature claustrophobia. Markdown lite is even worse for me. I never really feel that way with #gopher because I can just indicate things my own way in plain text.
The one single special element that is immune to all of this is links, and gopher has it.
#meta#lispyGopherShow ( #lisp#gopher#climate#sm0lnet )
Next week, in theme with #McCLIM and #ECL development I will also be hanging around #irc , both ~chat and liberachat. If anyone knows any good channels for the show chat to hang out in, please do tell.
It’s so fascinating having an archive like the one I have for Tedium. Being able to look back at pieces that are both extremely weird and deeply personal.
@ernie This point extends perfectly well to the Free Software / #FLOSS community also.
I work on what I find fun and interesting. I have no illusion that #NNCP, #Gopher, #Yggdrasil, and such are suddenly going to become popular. But wow are they FUN to work with, and useful too. I blog for the same reason. I've written several books with major publishers, about topics I enjoy, but still, I find that writing about what I want, when I want, without a deadline is more fulfilling.
I'm growing to really dislike a lot of the #w3c#standards.
Specifically the following aspects:
There's no way to gradually implement half of these. You have to start with 80% of a complete working implementation.
A lot of them are technical solutions in search of problems. As with design patterns: you usually don't know what your problem is well enough to formalize it until it's been done a few times, and there is a lack of that lived experience here.
Like I need 80% of #ActivityPub implemented before I can even effectively test it. The same is true with #JsonLD.
Compare with, say, #gopher, or #STOMP, #ODBC, or #AMQP. Or even patterns like #REST. Even at their most complex I can get started writing something for them with no issue whatsoever, and libraries already exist in most major languages.
#dog is channeling Alice's Restaurant this morning: "And I started jumpin' up and down, yellin' "KILL! Kill!" and he started Jumpin' up and down with me, and we was both jumpin' up and down, yellin' "Kill! Kill! Kill! Kill!"" #gopher hunting... (yes... he finally found the gopher).
Sorry, mastodon friends. Every time I log on to the mastodons I feel lost and discom"praise bob"ulated. Sometimes I wish the mastodons would just slow down to #gopher speed, or even single-session dialup #bbs speed. I just don't have the bandwiff these dayz to keep up. #feelingbadfomo 😦
I am increasingly worried about the current AI hype cycle taking down all of computer science with it. The more I think about it, the field is on the verge of a legitimacy crisis from several root-causes.
I've seen some AI/ML people (Timnit, etc) talk about the need for an anti-AGI movement. I think that applies to #CS generally. If the public at large comes to equate CS with AGI, it will kill the whole field for a decade when AGI implodes.
@rysiek@emc2 Neo-luddites are already here, yet often they stay either on other networks than http-based ones (like #gopher, #gemini,#pubnix, etc) or they stay with non-IT tech.
Another approach that I find super logical is what communities like Amish do : before adopting a particular tech, they gather together and discuss - what are the pros, what are the cons and if it is worth it.
Unfortunately, in our freedom-chanting modern world, there is little space left for real choice.
#lisp y #gopher show w/ screwtape in about three hours!
Music: More cyanmentality from last week, because I forgot they gave me free access to their pay-to-download bandcamp albums
-I decide my common lisp gopher mud chapter 1 on my hopfield net book needed to actually be gud (work work)
-hopfield nets as a solution to every single problem no matter what
-hash tables requiring only a few stray bits of a key
#lisp y #gopher show w/ screwtape as named by gef in about 4.75 hours #music original electric by noted kiwi https://cyanmentality.bandcamp.com/
Clarifying my thoughts on why current generative AI are bad #gopher examples of my bunny hopfield nets with memory collisions, but higher polynomial update functions spacing the memories out removing the collisions. Pictures and ASCII. STILL WIP. #lisp discussion of the great commentary I got on my failure to TDD, a bit on interlisp and git.