Are protected members/fields really that bad? No. They are way, way worse. As soon as a member is more accessible than private, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it "out in the wild" opens your class and classes that inherit from or interact with your class to higher bug risk. There is no way to know when a field changes, no way to control who or what changes it. If now, or at some point in the future, any of your code ever depends on a field some certain value, you now have to add validity checks and fallback logic in case it's not the expected value - every place you use it. That's a huge amount of wasted effort when you could've just made it a damn property instead ;) The best way to share information with deriving classes is the read-only property: protected object MyProperty { get; } If you absolutely have to make it read/write, don't. If you really, really have to make it read-write, rethink your design. If you still need it to be read-write, apologize to your colleagues and don't do it again :) A lot of developers believe - and will tell you - that this is overly strict. And it's true that you can get by just fine without being this strict. But taking this approach will help you go from just getting by to remarkably robust software. You'll spend far less time fixing bugs.

Python essentially doesn't have private methods, let alone protected ones, and it doesn't turn out to be that big a deal in practice.

I'm not saying never mark methods private. I'm saying the better rule of thumb is to "make methods protected unless there's a good reason not to".

Marking methods protected by default is a mitigation for one of the major issues in modern SW development: failure of imagination.

If it's dangerous, note it in the class/method Javadocs, don't just blindly slam the door shut.

Been disappointed, surprised or hurt by a library etc. that was overly permissive in it's extensibility? I have not.

The old wisdom "mark it private unless you have a good reason not to" made sense in days when it was written, before open source dominated the developer library space and VCS/dependency mgmt. became hyper collaborative thanks to Github, Maven, etc. Back then there was also money to be made by constraining the way(s) in which a library could be utilized. I spent probably the first 8 or 9 years of my career strictly adhering to this "best practice". Today, I believe it to be bad advice. Sometimes there's a reasonable argument to mark a method private, or a class final but it's exceedingly rare, and even then it's probably not improving anything.

Belangrijke stuwdam in Dnjepr verwoest, 'waterstroom onbeheersbaar'

what I'm asking people to do is to start considering what that means to your life what I'm asking 00:38:53 governments to do by if like I'm screaming is don't wait until the first patient you know start doing something about we're about to see Mass job losses we're about to see you know Replacements 00:39:07 of of categories of jobs at large

Don’t confuse Consent Mode with Additional Consent Mode, a feature that allows you to gather consent for Google ad partners that are not yet part of the Transparency and Consent Framework but are on Google’s Ad Tech Providers (ATP) list.

Seeking full energy independence from Russian gas, in response to Russia's energy blackmail in #Europe and the war in #Ukraine 🇺🇦, #Lithuania 🇱🇹 has completely abandoned Russian gas

Featured Listings

SERVING CHICAGOLAND & NORTHWEST SUBURBS

CALL US FOR A PROPERTY EVALUATION ANALYSIS!

Arlington HeightsMount ProspectSchaumburgPalatineProperty SearchCOMMERCIAL LISTINGSLease/Credit Application

But you can not make the user send a POST requests from an email

By default SMTP offers very little protection against interception. Traffic may be encrypted between servers but there are no guarantees.

email as a transmission mechanism isn't secure.

Using --ours did what I was after, just discarding the incoming cherry picked file. @Juan you're totally right about those warning messages needing to say what they did't do, not just why they didn't do it. And a bit more explanation that the ambiguity from the conflict needs to be resolved (by using --ours, etc) would be super helpful to this error message.

The effect of Antarctic meltwater on ocean currents has not yet been factored in to IPCC models on climate change, but it is going to be "considerable", Prof England said.

Just because the code is described as part of the WebDAV spec doesn't mean it's WebDAV-specific! Status codes are supposed to be generic.

I believe that SMS 2FA is wholly ineffective, and advocating for it is harmful.

This argument only works if what you’re defending is good. As I’ve already explained, SMS-2FA is not good.

Don’t let the perfect be the enemy of the good. Seat belts aren’t perfect either, do you argue we shouldn’t wear them? Etc, etc. This argument only works if what you’re defending is good. As I’ve already explained, SMS-2FA is not good.

If you use a third party password manager, you might not realize that modern browsers have password management built in with a beautiful UX. Frankly, it’s harder to not use it.

If you’re a security conscious user... You don’t need SMS-2FA. You can use unique passwords, this makes you immune to credential stuffing and reduces the impact of phishing. If you use the password manager built in to modern browsers, it can effectively eliminate phishing as well.

So in your example, you would not use a hyphen: "You can use the types [that are] built in to the library."

repressed intuition "returns to consciousness in distorted form" as the symbolic ways we compulsively try to ground ourselves and make ourselves real in the world: such as power, fame, and of course money.

Washington wallet-sized birth registration cards aren’t accepted

Uno studio facente parte del piano vaccinale italiano 2017-2019 del ministero della salute ha evidenziato come i vaccini facciano risparmiare molto in cure, ospedalizzazioni e farmaci prevenendo le malattie ed evitando le spese che si sosterrebbero curandole. Tali valori sono destinati ad aumentare di anno in anno, in quanto i soggetti vaccinati restano immunizzati e a questi si aggiungono quelli vaccinati negli anni successivi. Quindi ogni anno aumenta il numero di casi evitati e di conseguenza il relativo risparmio.

A sequence of Folgezetteln notes in the filenames of the Zettelns can from this perspective be considered a hardcoded outline and should be avoided, however convenient it seems.

keynote address in !" at the #entenary $eeting of the British Association for the Advancement of Science. %n this occasion he suggested that the fundamentalstructure of the universe was not matter but action

Voor een kernwapenvrije wereld, te beginnen in Europa Jet van Rijswijk -  02.02.2023

Result of lots of searching on net is that pre-checkout hook in git is not implemented yet. The reason can be: There is no practical use. I do have a case It can be achieved by any other means. Please tell me how? Its too difficult to implement. I don't think this is a valid reason

70% of cobalt comes from the Democratic Republic of Congo, where an estimated 40,000 children as young as 6 work in dangerous mines.

Tribes, landowners and communities find themselves wrestling with the not-so-green side of green energy.

Do not separate numbers from letters on symbols, methods and variables.

We are living in a time of unprecedented danger, and the Doomsday Clock time reflects that reality. 90 seconds to midnight is the closest the Clock has ever been set to midnight, and it’s a decision our experts do not take lightly

2023 Doomsday Clock Statement

≥

≥

Thus, there exists 1 ∈ (−1, 1) such that

In short, the agency put forth a rule that addresses the problem head-on without prevaricating or kowtowing to corporate America.

The usefulness of JSON is that while both systems still need to agree on a custom protocol, it gives you an implementation for half of that custom protocol - ubiquitous libraries to parse and generate the format, so the application needs only to handle the semantics of a particular field.

There is a fundamental distinction between simulating and comprehending the functioning (of a brain but also of any other organ or capacity).

Fluxus was an international, interdisciplinary community of artists, composers, designers and poets during the 1960s and 1970s who engaged in experimental art performances which emphasized the artistic process over the finished product.[1][2] Fluxus is known for experimental contributions to different artistic media and disciplines and for generating new art forms.

Does our most powerful force not come from the depths of our capacities to #love, #care for and #serve nature and all its beings, including ourselves?

the ultimate #guidance we need to heal Earth does not come from the #markets and our #technologies supporting them. What they are is tools, supporting a direction, facilitating transactions in a world where we do not yet speak a deep #common language of #unity, #stewardship and #coexistence but these markets and technologies should not dictate where we are headed, or else I'm afraid we are simply missing the whole point.

At Ipswich, he studied under the unorthodox artist and theorist Roy Ascott, who taught him the power of what Ascott called “process not product.”

The only negative to this method is that it may not ALWAYS work. If the data is faulty, or the link is inaccurately provided by the sender, Gmail won’t be able to recognise and include the unsubscribe button in Gmail.

You may find this link isn’t available straight away, after a few emails one should appear, this is a common technique with mailing list providers.

Hoe staten de oorlog in Oekraïne gebruiken om een nieuwe wapenwedloop op gang te brengen

Successfully Abolished

It’s as simple as running ngrok http 3000 to forward port 3000 (or any port) to a public ngrok address.

Include one or both of these headers in your messages:

If a contact ever reaches out and is no longer receiving messages because they accidentally marked one of your campaigns as spam, you can reach out to Product Support. We can remove them from the suppression list for you. 

Imagine what happens when subscribers change activities, interests, or focus. As a result, they may no longer be interested in the products and services you offer. The emails they receive from you are now either ‘marked as read’ in their inbox or simply ignored. They neither click the spam reporting button nor attempt to find the unsubscribe link in the text. They are no longer your customers, but you don’t know it.

by using symbols as keys, you will be able to use the implicit conversion of a Mash via the #to_hash method to destructure (or splat) the contents of a Mash out to a block

Hashie does not have built-in support for coercing boolean values, since Ruby does not have a built-in boolean type or standard method for coercing to a boolean. You can coerce to booleans using a custom proc.

There are also many reasons refresh tokens may expire prior to any expected lifetime of them as well.

You might notice that the “expires_in” property refers to the access token, not the refresh token. The expiration time of the refresh token is intentionally never communicated to the client. This is because the client has no actionable steps it can take even if it were able to know when the refresh token would expire.

session = ActionDispatch::Integration::Session.new(Rails.application) response = session.post("/mypath", my_params: "go_here")

I used the above to test what happens to the user if a POST happens in another session (via WebSockets), so a form wouldn't cut it.

So far for the obligatory warning. I get the point, I even agree with the argument, but I still want to send a POST request. Maybe you are testing an API without a user interface or you are writing router tests? Is it really impossible to simulate a POST request with Capybara? Nah, of course not!

I don't think a new tag makes sense here, at least not yet.

Once "Containerfile" starts becoming less of a whisper and more of the topic, then perhaps we can talk about a synonym. But definitely not now.

A beginning user should be able to docker run official-image bash (or sh) without needing to learn about --entrypoint.

Note: This repo does not publish or maintain a latest tag. Please declare a specific tag when pulling or referencing images from this repo.

Zombie processes should not be confused with orphan processes: an orphan process is a process that is still executing, but whose parent has died. When the parent dies, the orphaned child process is adopted by init (process ID 1). When orphan processes die, they do not remain as zombie processes; instead, they are waited on by init.

I have a custom font which is displaying the box character.

Glyph 0 must be assigned to a .notdef glyph. The .notdef glyph is very important for providing the user feedback that a glyph is not found in the font. This glyph should not be left without an outline as the user will only see what looks like a space if a glyph is missing and not be aware of the active font’s limitation.

It is recommended that the shape of the .notdef glyph be either an empty rectangle, a rectangle with a question mark inside of it, or a rectangle with an “X”

You need .notdef, unicode value undefined: microsoft.com/typography/otspec/recom.htm Characters are assigned in blocks of the same kind. Most blocks have some unassigned points at the end to start the next block on a round number. These points allow Unicode Consortium to add new glyphs to a block. New glyphs don't come into existence often. See typophile.com/node/102205. Maybe you can ask your question in the Typophile forum. They can tell you more about how this exactly works and how to render .notdef

I wasn't aware of 'missing character glyph', some Googling suggests that U+0000 can/should be used for missing characters in the font. However in at least one font I've tested with U+0000 is rendered as whitespace while missing characters are rendered as squares (similar to U+25A1).

At one time the replacement character was often used when there was no glyph available in a font for that character. However, most modern text rendering systems instead use a font's .notdef character, which in most cases is an empty box (or "?" or "X" in a box[5]), sometimes called a "tofu" (this browser displays 􏿾). There is no Unicode code point for this symbol.

No, there is no “glyph not found” character. Different programs use different graphic presentations. An empty narrow rectangle is a common rendering, but not the only one. It could also be a rectangle with a question mark in it or with the code number of the character, in hexadecimal, in it.

The glyph-not-found character is specified by the font engine and by the font; there is no fixed character for it.

By the way, I am not talking about � (replacement character). This one is displayed when a Unicode character could not be correctly decoded from a data stream. It does not necessarily produce the same glyph:

There is no standardized look/glyph, it’s up to the implementation

The character does not exist. Proposed solutions include encoding the character, markup for individual characters, and Private Use Codepoints.

I don't see why this is a false positive

Source Code is currently understaffed and working through our P2 bugs at the moment.

The problem is that the caller may write yield instead of block.call. The code I have given is possible caller's code. Extended method definition in my library can be simplified to my code above. Client provides block passed to define_method (body of a method), so he/she can write there anything. Especially yield. I can write in documentation that yield simply does not work, but I am trying to avoid that, and make my library 100% compatible with Ruby (alow to use any language syntax, not only a subset).

I have always been impressed by those academics who can sit impassively through a complex lecture by some visiting luminary without finding it necessary to make a single note, even a furtive one on the back of an envelope. They’d lose face, no doubt, if they were seen copying it all down, like a first-year undergraduate.

This type does not exist in Ruby, however.

This is great because it works in Terminal, iTerm2, Chrome, Sublime & Outlook. The alternative (Karabina) is less good because that maps "Home" to Command+LeftArrow, which actually switches windows in Terminal.

As our younger brothers of the New-England Indians

But this sounds like spreading fear and doubt when the Ruby parser has no such concepts :) {} always binds tightly to the call right next to it. This block {} will never go to using, unless it's rewritten as do ... end.

spamming open-source as a growth strategy is a super bad idea

Topsoil has different grades. Lower-grade topsoils are meant for filling and leveling holes and should only be used for that purpose. Higher-grade topsoils are great for conditioning or adding organic matter to the native soil. Neither grade should be used when planting.

in my personal opinion, there shouldn't be a special treatment of do-end blocks in general. I believe that anything that starts a "block", i.e. something that is terminated by and end, should have the same indentation logic

Code explains what and how Documentation explains why.

The underlying theme tyingthese myths together is that poverty is often perceived to be an issue of“them” rather than an issue of “us”—that those who experience povertyare viewed as strangers to mainstream America, falling outside accept-able behavior, and as such, are to be scorned and stigmatized.

"detail": [ { "loc": [ "body", "name" ], "message": "Field required" }, { "loc": [ "body", "email" ], "message": "'not-email' is not an 'email'" } ]

Hi L0ki,as we depend on retailers with affiliate programs to run the site without ads, and Amazon being one of them, yes, we are following their rules so we can use API and their affiliate program.As Tomas said, we are also trying to get the history back, though we noticed we aren't the only site being affected by this.As for ignoring their API and doing it the hard way - that could be possible I guess but really not preferable.And we also understand anybody not wanting to buy from Amazon anymore (as some already told us), but to be fair, if the game is available anywhere else (and I have yet to randomly find a game which is available only at Amazon), you can always check the game info on ITAD to compare the price to other retailers.

If it's not, it should be illegal for them to forbid you from showing price history. This is restricting access to information, and it's probably supposed to benefit them from shady sales (increasing the base price just before a sale, so that the "X % off" is higher).

"We are not allowed to show you Amazon history"? What prompted this? Fill me in if I missed something :).EDIT: Camelcamelcamel can still show Amazon price history, so a bit befuddled here.

I would be interested to know what the legality of this is either way. I mean, do they really have any legal right to compel you not to list their price history? However, just knowing that Amazon doesn't want you to do this will make me less likely to purchase from them in the future. Anti-consumer behavior pisses me off. Edit: If this is related to API access couldn't you just manually scrape prices off the site instead and hammer their server? Or is this more related to not wanting to bite the hand that feeds you so to speak related to the funding you can get through referral links?

However, while URLs allow you to locate a resource, a URI simply identifies a resource. This means that a URI is not necessarily intended as an address to get a resource. It is meant just as an identifier.

For example, a "write access disallowed" problem is probably unnecessary, since a 403 Forbidden status code in response to a PUT request is self-explanatory.

Rename the existing default branch to the new name (main). The argument -m transfers all commit history to the new branch: git branch -m master main

Snail mail can be too slow, and email isn't secure. So that leaves us with the decades-old, but still reliable, fax.

Maybe one day, JSON Schema would be able to express all the constraints in the OpenAPI spec, but I suspect some are going to be really hard.

When we do release a final version of JSON Schema, please do not use JSON Schema to guarantee an OpenAPI document is valid. It cannot do that. There are numerous constraints in the written specification that cannot be expressed in JSON Schema.

Yes, I understand that it had probably been tried. My question was more, "Why didn't twiddling the knob work?”

The discussion here can get very fast-paced. I am trying to periodically pause it to allow new folks, or people who don't have quite as much time, to catch up. Please feel free to comment requesting such a pause if you would like to contribute but are having trouble following it all.

I would not change the project structure to accommodate Docker (or any build tools).

The definitions provided are tremendously valuable to figure out the very similar but different two paradigms.

Concurrency means executing multiple tasks at the same time but not necessarily simultaneously.

I'm building a Rails API with a separate web frontend app as "just another API client" (various smartphone apps to follow as well). In the previous "monolithic" version of the service, where all the server side was rolled into one Rails app

Epics, issues, requirements, and others all have similar but just subtle enough differences in common interactions that the user needs to hold a complicated mental model of how they each behave.

The task is not deleted, but the two are no longer connected. It’s not possible to connect them again.

When we have our git rev-parse examine our Git repository to view our origin/HEAD, what we see is whatever we have stored in this origin/HEAD. That need not match what is in their HEAD at this time. It might match! It might not.

Windows 10 currently (01.01.2020) doesn't support Unicode country flags, and displays two-letter country codes instead of emoji flag images.

instead of inlining the images, the image URL’s (and captions) are read from a .yaml file. The URL of the yaml file is passed as an argument when loading the page. The .yaml file as well as the images should be publicly served.

Oh I see whats happening, we actually have specs for this but they're not correct

It really only takes one head scratching issue to suck up all the time it saves you over a year, and in my experience these head scratchers happen much more often than once a year. So in that sense it's not worth it, and the first time I run into an issue with it, I disable it completely.

5.7 Prioritize by weighing the value of additional information against the cost of not deciding.

Stop autoclosing of PRs While the idea of cleaning up the the PRs list by nudging reviewers with the stale message and closing PRs that didn't got a review in time cloud work for the maintainers, in practice it discourages contributors to submit contributions. Keeping PRs open and not providing feedback also doesn't help with contributors motivation, so while I'm disabling this feature of the bot we still need to come up with a process that will help us to keep the number of PRs in check, but celebrate the work contributors already did instead of ignoring it, or dismissing in the form of a "stale" alerts, and automatically closing PRs.

I don't understand why it should be so hard to keep issues open / reopen them. That's just going to cause people to open a duplicate issue/PR — or (if they notice in time) cause people to add extra "not stale" noise when the bot warns it's about to be closed. Wouldn't it be preferable to keep the discussion together in one place instead of spreading across duplicate issues? (Similarly, moving the meta conversation about an issue out to a completely separate system (Discord) seems like the wrong direction, because it wouldn't be visible to/discoverable by those arriving at the closed issue.) I get how it's useful to have stale issues not cluttering the list. But if interes/activity later picks up again, then "stale" is no longer accurate and its status should be automatically updated to reflect its newfound freshness... like it did back here: