mdpm

Fork is great, I paid for it happily. It's UI makes sense, radiates the right level of information, and you can use the keyboard almost exclusively. Heavily recommended.

My only thought here is that it's sad that the opportunities to discuss what were clearly impactful materials were dismissed, and that the books are somehow to blame.

Two quotes I don't see in this thread:

    Where they burn books, they will also ultimately burn people

and

    Art should comfort the disturbed, and disturb the comfortable

I think that's the point? It's trying to display the difference between the most commonly used projection and the actual relative sizes of territories.

(Forgive me if my snark detectors are misfiring, and have an xkcd)

https://xkcd.com/977/

I had the phones prior to the attempt (they're my previous handsets). Not wanting to buy fresh phones just to check feasibility. Sadly the choice just seems to be which nation-state-finance-intelligence cluster you want to feed your data to.

I've been trying to execute on this approach, as I'm very interested in checking out of the tracking-by-default ecosystems.

We're using some Xiaomi devices we purchased, and I'm currently seething. I can't root without 'unlocking', which is a process that requires me to activate a Mi Account, which then requires my email and a SIM (?!), and 'find my device' (location) to even allow installation of apps via USB. To unlock the computers I bought, so I can use the root account, to install an alternate.

Seems the prison walls are just set far enough away that we don't notice.

tl;dr, in order to get some privacy, I'm being asked to associate my IMEI, my IMSI, my email, and my location.

OpenID hasn't died at all - it's just used in a different context. We implement this now for SSO in corporates to unify fragmented IAM scenarios.

Accepting any domain as an OpenID IdP is not likely to be a feature of publicly facing sites, as they still provide the ability to create / register / use these accounts for spam and other unwanted abusive purposes.

.NET Core shares your opinion. Many of these are just registered/configured by default.

XSRF, rate limiting, permissions/RBAC, feature toggles/TIP, analytics, profiling, silly examples like recent samesite changes - Just a few examples, and that's without touching the developer tooling.

As each of these orthogonal concerns starts drifting in, applications become more and more complex as they 'tack on' support for these in code, rather than having structures in place to allow for extensions and modifications.

Abstractions always have their cost. Complexity exists in the problem domain of the web, and always will. .NET Core is generally well architected in response to a long experience in enterprise and developer concerns. It's not a magical answer to every domain's requirements, but it's generally a damn good compromise ime.

This would remove the benefit of functional idioms, and mitigate any advantages the differing approaches have. F# and C# and not just syntactically different.

This falls under the principle of "Complexity has to go somewhere".

Seconding this - as someone who's been developing software for 22+ years, using everything from SmallTalk to the MS stacks, Rider is an amazing IDE.

Low ceremony? Complexity in real world applications requires complexity in the frameworks that address them. Users will be more disappointed by simplicity that leaves them addressing complexity without guardrails, conventions, and tooling support.

If your view of low ceremony is matching HTTP verbs to methods, you may happily code your own against the HTTP primitives; if you want a framework that abstracts the complexity and provides a shiny-happy path, you may have to allow for some ceremony. The tooling is the antidote to this.

I think the place you trip up here is in not wanting to use a batteries included approach, while using a framework that makes the necessary abstraction/complexity tradeoffs for projects of mid to large scale. The appropriate tradeoffs _cannot_ be one size fits all.

F#'s support is tricky, as the number of users here is dwarfed by those in C#; and although .NET supports this language diversity, there are no direct idiomatic 'conversions' possible between C# and F# in many cases. This multiplies the effort of providing documentation and examples. I too would like to see it treated as a first class citizen, and for that - the code is OSS.

Communities sharing resources, rather than nuclear families is a good idea. Much of the world lives like this already. Not every house on your street needs a lawnmower (or a lawn).

Lack of privacy however, is a lack of personhood. It will be eroded, and some aspects of it should change, nudity for example should be less abhorrent to all. But this seems like a thought experiment for the sake of argument, and I fear that arguments are all it will generate.

In this case, it's rather that consistent work toward transformative goals has unlocked optimisations that have been deliberately and consciously been worked towards for the last several years and versions.

Consciousness is a property we ascribe to our own awareness of our awareness. As we are part of the universe, if consciousness is a thing, it is then a property of the universe, not just the human mind.

The human mind is a plastic, adaptive system, which is shaped by senses that consume the universe and which attempt to model the universe. It is past and present interlocked - causality, bound up in tight knots of matter.

This is the universe, being aware of itself. It is perhaps not capable of being understood, just reveled in.

The async stuff may require some attention, but it's part of the performance story when dealing with many requests, not when evaluating just one.

As regards configuration, all the means you could want for configuration are there. You can access items directly [1], or via strongly typed objects. These all support multiple sources of configuration data, and many means of overriding them.

I generally really don't like environment variables as they expose configured secrets to everything in the same machine / container, but we make use of the standard configuration system's environment variable overrides, but we use akv2k8s.io and thus only expose secrets to the container's entry point application.

[1] public Startup(IConfiguration config) { // injects config store var setting = config["yourConfigKey"] // ... but you now have to convert this from a string for any other datatype }

There is no .NET Core 4? There was a .NET Framework 4. 5 is how the streams are being crossed.

Agreed on not creating silos.

Adding User 'flair' is perhaps a viable option, where users can simply tag other users with a short description. That enables both properties - avoiding discourse you find troubling, and allowing users to highlight those that they find enlightening.

Freedom of speech works well when paired with freedom to listen. Removing content (even if only from a user's view) only deepens the filter bubbles we're being shaped by.

well, this takes me way back ...

https://web.archive.org/web/20080118050700/http://www.poetic...

While the Japanese were no saints, and have had one of the largest rebrandings in history - please don't underestimate the VoC.

Organic systems fare better when decentralised, that much is true (bacteria are inarguably more successful than man), but the politicisation of media in any direction is dangerous. SMTP didn't try sell you on an ethos.

Social and content silos, our natural tendency to create filter bubbles, and adversarial machine learning 'curating' your experiences and thus effectively, your culture; this is the danger.

This is a non-story.

When men are rightly occupied, their amusement grows out of their work, as the colour-petals out of a fruitful flower;—when they are faithfully helpful and compassionate, all their emotions become steady, deep, perpetual, and vivifying to the soul as the natural pulse to the body. But now, having no true business, we pour our whole masculine energy into the false business of money-making; and having no true emotion, we must have false emotions dressed up for us to play with, not innocently, as children with dolls, but guiltily and darkly.

- John Ruskin

These are all still on linux. That we're seeing results like we are with dotnet core, nascent and barely over v1 is great.

Cloud, just JS/C#, Json serialisation - http://i.imgur.com/KTOwNq0.png

Cloud, same languages, db query - http://i.imgur.com/z9dPuwS.png

I can't wait for the windows results. Those interested should also see https://github.com/aspnet/benchmarks

And who shall I say is calling?

-- You will be missed but never forgotten.

If I hired someone to stand outside and cover up some share of the offerings on my store's billboard, clearly varying only by the perceived race of whoever was walking by, the discrimination here would be violently evident.

Regardless of specific laws and statutes this may violate, it's an affront to every part of the progress we've made as a species. In my country, South Africa, this tool seems to be literally against the constitutional principles (Chapter 2, ss 9, 3-4).

Regardless of moral or legal questions even, do we not need to query what the societal cost is of allowing corporations to be facile and duplicitous, automatically, at the scale of enterprises like Facebook?

How has no-one here made the observation that the reason for this is due to true password strength checks, that use existing password distribution data that is prohibitive in size to send to the browser?

They're not doing the wrong thing, and the risk of side-channel attacks on this infrequent behaviour (i.e., not authentication) are trivial compared to the risks of high entropy passwords that are also highly reused, and are thus vulnerable to trivial brute force attempts.

I am simply frightened by this. Dependency freezing is a tenet of reproducible builds, reproducible builds a principle of engineering for any sort of reliability. This varies not a whit between interpreted or compiled languages. To extrapolate that to a massive generalisation like 'not good for web' is Not Even Wrong.

tangential, but spaceengine is awesome.

Meanwhile, I still can't edit a playlist while playing it.

edit: constructively put - there's simpler stuff to fix UX and match user patterns still isn't there?