Pinned toot
Pinned toot

This One Trick Will Revolutionize Your Use of Social Media: Block fuckwits.

On social media, the advantage is that a large userbase and participation. The disadvantage: it's 99.9999% crap.

What's working for me is to filter ruthlessly. If someone is disruptive, ideological, insane, or crazy-making, I'll block them without thought (I used to agonize over that, I don't any more).

High signal is rare, but odds of missing out by blocking idiots are low.

web.archive.org/web/2018030315

Pinned toot

My present Recaptcha policy:

Request audio.

Respond "Fuck you Google"

Repeat until access granted, or the joy fades.

Bonus: All audio AI parsing tends to "Fuck you Google".

Pinned toot

My current policy for "Cookie Consent" dialogues:

1. Fire up uMatrix and globally block cookies for domain.

2. Fire up uBlock Origin to block element on page.

3. Self-Destructing Cookies for edge case motherfuckers.

Remember, boys and girls and all that lieth betwixt and beyond: FIRST pillage THEN burn!

Pinned toot

"Pseudonyms and anonymity are also an established part of many cultures -- for good reason."

- Alma Whitten, former Director of Privacy, Product and Engineering, Google

rms 

I am a:
⚪ Man
⚪ Woman
🔘 Man of constant sorrow
And I:
⚪ Am seeking men
⚪ Am seeking women
🔘 've seen trouble all my days

@dredmorbius even when space and time dies, Monday will survive.

However, the good news is that one of these Mondays will be our last.

We's IPO doesn't Work

WeWork owner The We Company took a last-minute decision on Monday to suspend preparations for an initial public offering (IPO), concerned that its stock market debut would be snubbed by many investors, people familiar with the matter said.

HN discussion:
news.ycombinator.com/item?id=2

WeWork parent pulls IPO following pushback: sources

reuters.com/article/us-wework-

Do you prefer using a product or a tool?

Straightforward UX, or extensive feature-set?

Clear value proposition, or infinitely customisable?

Slick or austere?

Strictly implementing one vision and set of goals, or adding all kinds of features that different people request or contribute?

Extensive user documented, or code and settings panels (or config files) as documentation?

Historically, the former tends to be proprietary apps, while the latter then to be free software projects that clone the intitial vison/functionality, and then evolve mostly by adding features. The complexity goes up and the UX goes down.

These days we have free software products (eg. Mastodon and Pixelfed) and free software tools (eg. Pleroma).

The question is how do you preserve the user-freedom advantages of tools while gaining the user traction and usability of products?

I suggest one approach could be having a generic backend tool, with standard protocol-based federation and an open API that enables frontend app designers/developers to create slick products that implement all kind of different visions and use cases.

I hope Pleroma and http://commonspub.org can help make something like this happen.

hayek, you absolute boondoggler! the road to serfdom was capitalism all along

a courier arrives from the next village on horseback with books, zines, letters, art prints, and a hard drive full of music and movies. we offload the drive while the courier joins us for lunch, sharing news — harvests, births, deaths, the goings-on of various governance councils — while we load a drive with our own new media. the courier leaves as full as they came, and well-fed besides.

And a via a correspondant:

> The poor have been rebels but they have never been anarchists. They have got more interest than anyone else in there being some decent government. The poor man really has a stake in the country. The rich man hasn’t; he can go away to New Guinea on a yacht. The poor have sometimes objected to being governed badly; the rich have objected to being governed at all. Aristocrats were always anarchists, as you can see from the barons' wars.

-- G K Chesterton

Go now defaults to attempting to fetch code dependencies from a proxy operated by Google before getting it from source. This feels a bit weird. By default, you are basically leaking the names of your dependencies when you build code.
(via @juliobiason)
codeengineered.com/blog/2019/g

Hardly a novel concept, I know:

"The love of possessions is a disease in them. These people have made many rules that the rich may break, but the poor may not! They have a religion in which the poor worship, but the rich will not! They even take tithes from the poor and weak to support the rich and those who rule."
-- Sitting Bull (goodreads.com/quotes/683834-be)

"The rich ruleth over the poor, and the borrower is servant to the lender."
-- Proverbs 22:7

2/

Law-takers vs. law-makers

This makes a neat mapping between competitive/monopoly market theory (price takers vs. makers), to law and power.

Daniel Markovits ("The Poverty Trap") discusses this at about 50 minutes (roll back to 40 for the preamble) here:
media.rawvoice.com/lse_publicl (MP3)

There's a 2010 book w/ a title:
taylorfrancis.com/books/e/9781

1/

Shakin' like tremelo...

Drop that casette in your Walkman, pop in your earbuds, and rock out.

invidio.us/watch?v=BZhfFXEMMI4

Metcalfe law's shadow: the risks in a network are proportional to the square number of people connected to the network.

-- pacala @ HN
news.ycombinator.com/item?id=2

Hey, #django people: Do you know any documentation which describes the control flow of all the many functions in form handling with generic views? I got lost in all the get_form_kwargs, get_initial, form_valid and co. Thanks!

: After you post something with some specific hashtag, take a moment to see who else has posted under that tag previously.

Maybe there's not much. Maybe there is. Pleasant suprise is pleasant.

Show more