towolf

  > I honestly say the films from Tarr are arguably the best book-to-film adaptations ever, especially Sátántangó, he is the master of literary filmmaking where the spirit of text comes across the screen perfectly.

If that is so, then these are books that you read to experience ultimate ennui?

I know the films, I've watched them all, but doing e.g. Satantango in book form sounds not so enticing?

Are you aware of the "Tools -> Verbatim" mode?

Try Hetzner.

Someone installed the dashboard for us before the RBAC stuff was added. The fun started when we realized that the old ClusterRoleBinding needed to be deleted manually.

Clicking SKIP hence gave full access until we did.

It's nice when things are idempotent, but removing stray things that should go absent is usually overlooked.

When you visited, did you notice that the Milka you said is 100g here, isn't anymore?

They even put it into the slogan: "Milka Alpenmilch. Für Mich – Für Dich 80g"

This whole thing to me sounds like the "chemtrail" conspiracy.

http://www.wz.de/home/wirtschaft/schokolade-100-gramm-tafel-... https://www.milka.de//Produkte/milka-tafeln-100g?categoryId=...

Any info about how multiple fixes are integrated to approximate the true location of a fix?

I remember reading how Wigle Wardriving calculated fixes and the method seemed unsophisticated and lame.

For example, if I bike down a street then fixes would be detected 100m ahead of me and always pinned to the road at my current location.

If I bike down the road in the other direction the next time, will be fix become more accurate?

Normally higher SNR fixes should have more weight than weak fixes. Do they?

Well, I added backstory, which extended two years before this unnecessary public outrage event. People were asking questions about where the code went. I explained there was no clear single commit and how to find where it was removed.

And then I overstepped and deduced that this may be assumed to be intentional, condering the backstory.

You might say that was inappropriate and I was banned with justification. But I’m a human too and this lack of proper communication frustrates me to no end. If the developer in question can be said to have a breaking point, I have one too.

None of this would have happened if the involved parties had a better standard of communication and of handling matters.

Olav, there were eight bugs filed and no explanation. I came back to the bugs irregularly to see wether there was anything new in terms of explanation.

Then this trainwreck happened and people were asking questions.

So I thought it worthwhile to add what I knew. I don’t think I disclosed anything personal. It was strictly technical matters relevant to the bug at hand.

So why did you ban me with a false accusation?

If anything the "removing type-ahead search from nautilus" bug should’ve taught the lesson that an information campaign works better than outright censorship.

When that bug got attention Jon McCann came in, explained, and then made a full blog post[1] to expound the directions they were taking. I still didn’t like it but I was satisfied with the explanation.

Stop digging in and realize that just slightly amending your policies and interactions with users would fix everything.

[1] http://blogs.gnome.org/mccann/2012/08/01/cross-cut/

From what I’ve read on another bug from 2011 ARGB Visual could also just stay on even without a compositor.

I just looked at the bug again and it’s been sanitized. I commented 2 or 3 times in the linked bug to add backstory. Those comments are gone now. The attachment I added is still there.

Funny story, they banned me now because they think I submitted this HN story. I didn’t, I came here way later.

http://i.imgur.com/wCTh0MZ.png

Makes you think, doesn’t it? (The warnings refer to another bug a few months ago, where I tried to make another developer explain his removals, and good discussion and a full blog post resulted. All in all a good result. But still they said I was out of line because I named names)

Only looking for explanations. Really super grateful that Jasper_ added some, but it’s still not entirely clear.

I can’t see how Gsettings has anything to do with opacity and the compositor.

Perhaps separating these things out in different commits would’ve been smarter to begin with.

> but minds were changed.

So what does it take to make the minds change back again?

When I stare at opaque terminals all day I get severely perceptually understimulated to the point that I fear becoming an automaton.

But with some sliding animations and a bit of flower poking through it soothes my nerves.

Is that not enough reason?

> Really?

No idea. That’s what I derive from "we had an informal poll". Since they hang out on IRC that is probably where it happened.

You have to use an advanced search to find NOTABUG, WONTFIX, and DUPLICATE and similar bugs. Otherwise you turn up empty. There’s even more discussion in the other bugs. For some reason they didn’t dup all those bugs consistently. Maybe that would’ve lead to a criticla mass. But who knows why not.

[List of bugs mentioning problems related to background transparency](https://bugzilla.gnome.org/buglist.cgi?product=gnome-termina...)

There’s no gnome-terminal mailing list. Since "bike shedding" is struck down with regularity on the bug tracker I wrote the guy directly before he made the commits.

I asked why he wants to remove the feature. He said it’s loosely connected to other features that are buggy and he doesn’t see the point of the feature anyhow. Whether I had a justification for the feature to stay.

I replied and gave him two good reasons, one of personal merit, one of technical merit.

Then nothing else.

Then I discovered that it indeed had been removed, while I was following git snapshots. So I checked the NEWS and Changelog, ReleaseNotes and git. No mention. Could’ve been temporary or unintentional.

So I wrote the guy again to ask what’s up. No reply. Then he replied with a non-answer only pointing to a FAQ entry he made the same day with a distracting workaround.

So I checked out git locally to see where the code went.

It turned out among unrelated commits where the code was #if 0’ed out only to be removed a few commits later with "delete dead code" etc.

So I wrote him again to ask why he did this. No reply.

So I downgraded to the known-good old version and waited for release time. Same story repeats with other people. Apparently nothing personal because of my tone.

So. Conspiracy or justified puzzlement about this behaviour?

By the way. Ubuntu was using transparent background by default [1].

So it’s fair to say that at bare minimum tens of thousands of people were using this code path.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=692609#c2

You forgot to mention that the ARGB Visual type was working well enough for years, ever since xcompmgr was around, all trough compiz and GS.

And the GS → metacity → GS cycle was not crashy here at all. It worked.

And now you’re getting into Wayland territory. All the more reason to make sure that windows with alpha maps work.

You can keep the old code around in the meantime.

Also, making a poll in your 50 people IRC channel is not a very meaningful sample size is it?