Ferk

@Ferk@lemmy.ml
0 Post – 17 Comments
Joined 3 years ago

Saying that I dont trust a homophobe is not “sharing my political opinions”

That's true.

However, you did not just say that. You mentioned how he supports some homophobic politics (ie. regulation against gay marriage), which you (and I'm sure a lot of people, me included) disagree with. That's politics.

You also shared your opinion about why you think privacy is important for our society. That's also politics.

I'm not saying that what you said is wrong... I'm saying that what you said is political. Sharing political opinions is ok. It's not like talking about politics is somehow a bad thing. At least not in this context. A lot of what surrounds the choice of a web browser like this is political.

espeak default voice backend is synthesized without using actually real voice samples. So it doesn't require downloading a huge package for each language, which is convenient in some cases, but the outcome is extremely robotic.

You can use MBROLA as backend for espeak so that it uses some voice samples and the result should be less jarring (it'd still be easy to tell it's not natural voice, but at least you'd be able to understand it better). There's a tutorial on this here: https://github.com/espeak-ng/espeak-ng/blob/master/docs/mbrola.md

Or you can try piper (https://github.com/rhasspy/piper) it's one of the most natural-sounding TTS (here are some samples).

It can be formatted "nicely" with no issue. But that doesn't necessarily make it easy to understand.

What that person posted was in a function named smb() that only gets called by rmb() under certain conditions, and rmb() gets called by AdB() under other conditions after being called from eeB() used in BaP().... it's a long list of hard to read minified functions and variables in a mess of chained calls, declared in an order that doesn't necessarily match up with what you'd expect would be the flow.

In the same file you can also easily find references to the user agent being read at multiple points, sometimes storing it in variables with equally esoteric short names that might sneak past the reader if they aren't pedantic enough.

Like, for example, there's this function:

function vc() {
    var a = za.navigator;
    return a && (a = a.userAgent) ? a : ""
}

Searching for vc() gives you 56 instances in that file, often compared to some strings to check what browser the user is using. And that's just one of the methods where the userAgent is obtained, there's also a yc=Yba?Yba.userAgentData||null:null; later on too... and several direct uses of both userAgent and userAgentData.

And I'm not saying that the particular instance that was pointed out was the cause of the problem.. it's entirely possible that the issue is somewhere else... but my point is that you cannot point to a snippet of "nicely formated" messed up transpiler output without really understanding fully when does it get called and expect to draw accurate conclusions from it.

That's out of context. That snippet of code existing is not sufficient to understand when does that part of the code gets actually executed, right?

For all we know, that might have been taken from a piece of logic like this that adds the delay only for specific cases:

if ( complex_obfuscated_logic_to_discriminate_users ) {

    setTimeout(function() {
        c();
        a.resolve(1)
    }, 5E3);

} else {

    c();
    a.resolve(1)

}

It's possible that complex_obfuscated_logic_to_discriminate_users has some logic that changes based on user agent.

And I expect it's likely more complex than just one if-else. I haven't had the time to check it myself, but there's probably a mess of extremely hard to read obfuscated code as result of some compilation steps purposefully designed to make it very hard to properly understand when are some paths actually being executed, as a way to make tampering more difficult.

1 more...

If they were complaining about cronjobs being created (like the post says), then they must have known what cron is.

I have purchased every single open source game that I've seen listed on steam as paid. Examples:

For more FOSS games on steam, there's a decent list collected on this curator (also pointing which ones are only partially open): https://store.steampowered.com/curator/38475471-Libre-Open-Source-Games/?appid=1769170

It doesn't really matter whether it was "targeted" at Firefox specifically or not, what matters is whether the website has logic that discriminates against Firefox users. Those are 2 different things. "End" vs "means".

I wouldn't be surprised if the logic was written by some AI, without specifically targeting any browser, and from the training data the AI concluded that there's a high enough chance of adblocking to deserve handicapping the UX when the browser happens to be Firefox's. Given that all it's doing is slowing the website down (instead of straight out blocking them) it might be that this is just a lower level of protection they added for cases where there's some indicators even if there's not a 100% confidence an adblock is used.

"you want a government backdoor on GPL licensed code? publish the backdoor for everyone to use, see and exploit/check for themselves. And/or watch as people simply take a version of the software built from a more reputable source without that backdoor instead. Thanks for the money!"

"you want to force all foss projects existing in the global internet across countries to get paid by you or close? enjoy your logistic nightmare as you pay to be made fun of by all other countries while I fork projects with one click"

It's changing by having a library like wlroots do most of the work.

When you consider the overall picture, "wlroots + compositor" is actually less complex than "X11 + window manager" because you no longer need to consider the insanely high requirements of having to have a team maintaining the spaghetti mess of X11 code.

Wayland-based dwl has roughly the same line count as X11-based dwm (about 2.2k), without having to depend on a whole separate service as big as X11.

But of course, it being a completely different approach, it's likely that for most smaller projects (ie. not Gnome or KDE) it's easier to start a new project than creating a layer to maintain two different parallel implementations.

If you want something that's more or less compatible with openbox, there seems to be this project, labwc, which claims to be inspired by openbox and compatible with its config/themes.. though I haven't personally tried it.

Also keep in mind that openbox (and I expect labwc too) doesn't include any "panels" / "taskbars" or anything like that... and it's likely your X11 panels might not work well if they do not explicitly support Wayland (but I believe that, for example, xfce-panel now supports both).

Bash. By default it might seem less featureful than zsh.. but bash is a lot more powerful and extensible than some give it credit for. It might be more complex to set it up the way you like it, but once you do it, that configuration can be ported over wherever bash exists (ie. almost everywhere).

The thing is that being "willfully ignorant" has served them well, so it makes it the smart move when the goal is "line go up".

Give me money and call me stupid, why would I care what a few "smart" people think when millions of "stupid" people give me all I want?

I think part of the reason why the long extension is often preferred is because it's much clearer and it's guaranteed to be supported and decompressed by the respective tools. Even when they don't suppot tar archives, they'll just give you the uncompressed tar in that case.

It's also very common to do that with other extensions (not just .tar) when compressing big files. For example, when archiving logs they'll often be stored as .log.gz, which makes it automatically clear that it's a log file directly compressed with gzip and meant to be examined with tools like zcat and zless to view it.

And in cases like that you really need it to be clear on what data does the gzip stores, since it does not keep metadata about the file so you might not be able to get back the original name/extension of the file if you rename the gz file.

Nonsense video, underlying problem is monopolies and private companies who develop the standards, not what browser you use.

It's the other way around. Which browser you use is what directly determines whether monopoly and private companies develop the standard you use.

You could write a standard independently of those companies, but then if everyone chooses to use browser engines from companies that don't follow it, what's the point?

If everyone uses a particular browser then whatever that browser implements becomes the standard. It's all about what browser you use.

If the standards are fully open, transparent and not concerning then it would make no difference if you use chrome and firefox because everyone would use same basis.

If what you want is everyone using the same basis, then what you need is to get everyone to use the same browser engine (which is what is happening already).

However, focusing on that is likely to not result in it being "fully open" as long as the popular browsers are not interested in openness (in particular with a MIT-licensed basis that is allowed to be privately altered, extended and corrupted in proprietary forks by those popular browsers who don't have to be "transparent" on what exactly they changed).

If what you want is for it to be "fully open", then you'd want people to be more careful and choose a browser with a "fully open" basis, instead of using whatever is more popular. It's still all about what browser you use.

2 more...

This.

I don't understand the appeal of microblogging. The content is generally very low quality, the signal-to-noise ratio is horrible... I'm not interested in the shower thoughts of any particular individual ...or in marketing stunts.

The only individuals I'm interested on are my family & friends, and even for them I'd rather use a more private platform.

And when I want to read a public post I'd rather it's well thought and ideally not restricted by micro-limitations. Even better if it's curated by a public voting process among a community of people with my same interests, or some other process that makes it so I don't have to waste my time going through tons of content I'm not remotelly interested on.

I think it's more that executives think the average consumer is stupid and cares too much about IP branding. And I feel they are not completelly wrong. Though I think the OGL fiasco showed the D&D fanbase might be smarter than that ...hopefully.

You can grow potatoes for political reasons too. Everything a human being does might be politically motivated, but that doesn't mean potatoes are political.

Anyone can take that same software, that was created as a particular political statement, and use it for the completelly opposite political reasons to make a completelly different political statement. Just the same way as many have used songs in contexts that are completelly politically opposite to what the original author of the song intended.

In the end, the only thing that's political is the goal/purpose/motivation of an action, not the result of the action. No piece of software/hardware/thing is political when you dettach the artist from the art and just see it for what it is, regardless of what the author might have wanted you to see it as.

No it is not, this is a myth. As you also can use free software on closed OS, which happens to be the standard

Why does it "happen to be the standard"?

Because people use it. At the end of the day, usage is what determines what's standard.

Whether a particular person can opt to go for something non-standard (eg. Linux) doesn't make what I said any less true.

And the problem is that the non-standard person can't expect the same level of support (eg. Linux drivers for obscure hardware).. because devs and companies won't care so much for any deviations from what's standard.

The point is that user generated or govt establish frameworks can b used as basis

That would be useless if people (both end users and web developers) don't use it.

The Mozilla Foundation created their own browser. Yet they are dying since they are getting abandoned by both web devs and end users. Creating your own does not solve the problem.

If web devs design for Chrome and Chrome adds Chrome-specific deviations from the standard, it's gonna be extremelly hard to keep up, which is what is happening with Firefox.. they can't keep up, they keep receiving reports of problems because websites are developed for Chrome.

This is already the case, you can choose not to use FLoC. Nothing changes here.

Yes, In there I was just describing how things work. As I see it.

Please learn the difference between Browser engine and web standards, nonsense you talk here

Web standards are just a set of rules that hipothetically Browser engines follow.

In practice, however, no browser engine actually follows the standard 100%, since they all have their very own extensions or try different optimizations that result in differences of implementation.. Google keeps adding their own spin on things at a pace that is hard to keep up for any other browser.

If it were possible for web standards to be really, truly, and fully respected, then indeed it wouldn't matter what browser you use. But that's not what the reality is. There are websites that work and look different in Chrome than in Firefox.