Bad idea of the day: color words based on the average semantic distance of the highest-TFIDF words in their dictionary entries, across parallel corpora in different languages, so that translations are almost the same color

a few thoughts about writing tests for web applications:

- yes, you're basically writing a stripped down version of the logic of your app all over again in a different framework

- there are best practices but folks seem to be even more splintered on how testing should be handled than they are on which framework you should use. it's something you'll have to decide with your team

- it requires thinking very differently about your app than you usually do, and will have you rethinking how you're handling data

- it does indeed increase the amount of time, code, and effort it takes to write an app. that's not an illusion and it's something to be accepted as part of the process because...

- it saves an unseen amount of time and effort you would have put into debugging. you won't know how much you've saved because you won't be doing that work. this is easy to forget

I've been scratching my head about the difference in MIG-generated code — and in Mach message format in general — between Darwin and the Hurd. Sadly this stuff is grossly underdocumented (like most of Mach & Hurd internals).

1/7

@strypey I think it's good to have many different protocols at this stage, to gain experience and figure out which approaches work well and which don't.

Email also had a lot of different protocols in the early days. Then there was sendmail, which could speak all of them, and relay messages between different networks speaking different protocols.

Then, eventually, SMTP won.

I think soon we may need a sendmail of federated social networks.

@Wolf480pl
> I think soon we may need a sendmail of federated social networks.

I'm starting to imagine this being a multi-protocol client, rather than a server. I blogged a huge rant a week or two back about replacing FarceBook, and how it's too big a job for any one open source project to do successfully. But a nicely designed client, that does chat (XMPP), email, micro-blog (all the fediverse standards), events (AP+WebCal), and photos and videos (AP+WebTorrent), that could do it.
@imacrea

re: Long post Show more

@Wolf480pl tell that to the developers of #Pidgin, or any of the other highly successful multi-protocol clients that have existed over the years. You wouldn't need a different UI for every account, just for each type of activity;
* live chat
* public note (DMs can be presented with short emails)
* public blog (private blogs can be presented with longer emails)
* photo
* video
* event
*etc
@imacrea

'A Revolution In Your Pocket':
- Ross Schulman
rbs.io/2019/05/a-revolution-in

This is a brilliant summary of the vision for #EthicalDesign (to borrow a phrase from ind.ie's manifesto) and what could to be done to help it succeed.

I want to take a moment to thank everyone providing mirrors and BitTorrent seeds for Kiwix content archives. 😇

#Kiwix #OfflineWikipedia

The time has come. I have written an article that you all must read. Then you can begin the 15 minutes of hate with my picture as your subject.

Purism's Gamble

poetgrant.press/purisms-gamble

This is pure opinion and after writing it, I have realized that it is more focused on GNOME than on Purism, though in a nuanced way, I am indeed speaking about Purism. Anyway, just go look at it and begin the hatred for yours truly!

Cheers!

@strypey @imacrea
And then, if we narrow down to one type of activity - eg. microblogging - I'd rather have one account on one server which can speak all the federated socnet protocols (AP, Zot, OStatus, whatever movim uses on top of XMPP, etc.) and talk with all my friends, instead of having separate accounts for each protocol, only connected through the client.

Web Crawler/Search Engine software (help wanted) Show more

@Wolf480pl sure, the #OneRing protocol is the platonic the ideal. But if you look at the first couple of posts in that rant, and especially when you factor in #XMPP (eg #Movim and #SalutAToi) it's become pretty clear to me that's not going to happen. A unified client OTOH is still possible.
@imacrea

Go is Google's language, not ours

utcc.utoronto.ca/~cks/space/bl

(This shouldn't surprise anyone seeing what Google means by "open source".)

"To confront rigid radicalism effectively, we think, is not to pin it down and attack it, but to understand it so that we can learn to dissipate it. Because these tendencies are linked to fear, anxiety, shame—to our very desires and sense of who we are and what we are becoming—we think it is important to approach all of this with care and compassion."
joyfulmilitancy.com/2018/06/03

This reminds me of #FrancesLee's writing on the same subject.

@strypey @imacrea
Yes.
But then:
- one server could speak all those protocols as well
- these are all the same type of activity

@Wolf480pl sure, like I said, it doesn't have to be a native client. I think the main problem at the moment is that too many of the implementators also have skin the game of specifying standards. So they're very attached to the "rightness" of this or that standard, and stubbornly unwilling to implement the others. From what I've seen this has improved as the promotion of AP brought new devs into the space and will likely improve more the more we can do that.

CSS grid and CSS calc() have changed my life for the better.

Show more
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).