Honeydue is a financial app for couples. You may prefer Honeydue over Simplifi if you're looking for a free budgeting app that helps you see individual and shared expenses.

Another simple way is to set up automatic deposits from your checking account into your savings account. Set the deposits to occur on the same day each month (like the day after your paycheck hits the account). This way, you’ll be saving a fixed amount of money regularly without even giving yourself the chance to use it for something else.

Users will no longer have access to their Mint accounts on March 23, 2024

You can’t split anything, so that charge at the gas station is all gas, even if you spent a little in the food mart.

In fact, fully anonymized data may carry little to no value to your business, which makes data collection and processing completely irrelevant.

Striking a balance between data anonymization and data utility is crucial yet very challenging.

When Undodog runs, he rides the Reset Rocket.

Furthermore, there is compelling evidence that obtaining consent can result in bias, which, in certain circumstances, can affect the outcome of the analysis. Introducing bias into data would not be in the interest of any of the stakeholders.

In this case, the DPA ruled that the anonymization of personal data can be used to meet the law’s data deletion requirement.

however, choose to anonymize additional personal information (last name, first name, and address) so the data could be used in ongoing analytics projects.

And, does the PI actually need to be completely deleted or can some or all of the PI be anonymized?

Ironically, data brokers need to collect additional info to verify your identity and ensure they’re deleting the right person’s data.

If you’ve got some technical savvy, the open-source tool Privacy Bot can send mass data deletion requests from your email address.

Other companies ignore requests, hide forms or require unreasonable proof of identity — one company in Consumer Reports’s data opt-out study asked a participant to submit a notarized affidavit, Mahoney said.

But according to the EFF’s Tsukayama, de-identified personal data is an oxymoron. She pointed to studies — like this one from researchers in Europe — that have found ways to re-identify large percentages of individuals in anonymized data sets.

Additionally, CCPA doesn’t require companies to delete personal data that has been aggregated or “de-identified.” That means if they combine your data with data from other people in a way that obscures which data comes from whom, they’re allowed to keep it.

Lo said the whole process felt like an exercise in futility.

Does submitting a request mean my data will get deleted?Nope. Deletion requests are subject to some broad exemptions. Some companies — like financial services — have to hold on to certain data for legal compliance and reporting. The CCPA also allows companies to keep your data if they’re using it for security, debugging or fraud protection, or “to enable solely internal uses that are reasonably aligned with the expectations of the consumer based on the consumer’s relationship with the business.”

What if I don’t live in California?Only California residents have the right to data deletion under CCPA. (Why companies have the right to your data and you do not is another story. And here’s another. And another.)But some companies have said they’ll honor deletion requests no matter where you live. Spotify, Uber and Twitter said they treat deletion requests from any geographic location the same. Netflix, Microsoft, Starbucks and UPS have also said they’ll extend CCPA rights to all Americans.

The company will probably ask for you to send over additional information or set up an appointment to verify your identity — that’s so no one can pretend to be you and steal or delete your data. To verify, you may need to confirm your account username and password, provide a piece of data like your phone number for the company to cross-check, or, rarely, show your government-issued ID. You should never be required to set up an account to get your data deleted, according to CCPA.

The companies behind six of the 11 apps, including Southwest Airlines and Twitter, were not sharing how many requests they’d received and honored. Twitter said it plans to add the information.

People have to verify their identities before companies can delete data, which poses an extra obstacle.

or were left with no idea whether it worked

Nobody can see deleted accounts - not even developers. Deleted accounts are fully deleted. There's nothing to see basically by definition.

There is no active user with that ID, so you cannot search by it. The whole point of deleting an account is to make it inaccessible, unreferenced, and unlinked. We're not going to implement "soft" account deletion.

You cannot. And you're not supposed to. When an account is deleted, it is disassociated from all existing posts by design.

I am currently working with a system presently where every table has a Deleted flag for soft-delete. It is the bane of all existence. It totally breaks relational integrity when a user can "delete" a record from one table, yet children records which FK back to that table are not cascade soft-deleted. Really makes for trash data after time passes.

Don't worry about performance too early though - it's more important to get the design right, and "right" in this case means using the database the way a database is meant to be used, as a transactional system.

The only issue left to tackle is the performance issue. In many cases it actually turns out to be a non-issue because of the clustered index on AgreementStatus (AgreementId, EffectiveDate) - there's very little I/O seeking going on there. But if it is ever an issue, there are ways to solve that, using triggers, indexed/materialized views, application-level events, etc.

Udi Dahan wrote about this in Don't Delete - Just Don't. There is always some sort of task, transaction, activity, or (my preferred term) event which actually represents the "delete". It's OK if you subsequently want to denormalize into a "current state" table for performance, but do that after you've nailed down the transactional model, not before. In this case you have "users". Users are essentially customers. Customers have a business relationship with you. That relationship does not simply vanish into thin air because they canceled their account. What's really happening is:

Now you have something with all of the benefits of soft-deletes but none of the drawbacks:

The truth is that both of these approaches are wrong. Deleting is wrong. If you're actually asking this question then it means you're modelling the current state instead of the transactions. This is a bad, bad practice in database-land.

In any system even remotely tied to money, hard-deletion violates all sorts of accounting expectations, even if moved to an archive/tombstone table. The correct way to handle this is a retroactive event.

So, soft delete is better, right? No, not really: Setting up cascades becomes extremely difficult. You almost always end up with what appear to the client as orphaned rows. You only get to track one deletion. What if the row is deleted and undeleted multiple times? Read performance suffers, although this can be mitigated somewhat with partitioning, views, and/or filtered indexes. As hinted at earlier, it may actually be illegal in some scenarios/jurisdictions.

The industry’s first standard for handling user data deletion requests

This is the first technical standard of its kind for the digital advertising industry

Avoiding one-off, proprietary builds per partnership and policy, or just as bad, manual processes to reach out to partners for deletes, can save the industry real money and reduce room for error.

I find it ridiculous that we spend energy on debating whether an alternate spelling is "correct" - real people, not English professors and dictionary authorities, are the authorities on English-as-used, and will ultimately make the distinction irrelevant.

Program with an eye to adding a check boxes within P1 and/or P2 training.

It's like someone creating a new List and a new Set, printing their size(), and then asking what's the difference. Of course, there is none: The size is 0 for both.

nowadays many people work with docker containers. Most default docker images do not have bash and something like [[ $string == *foo* ]] will not work.

It's not so much a criticism as the preference of a more universal solution over a more limited one. Please consider that, years later, people (like me) will stop by to look for this answer and may be pleased to find one that's useful in a wider scope than the original question. As they say in the Open Source world: "choice is good!"

if [[ $string == *"My long"* ]]; then

Please use $needle in a $haystack idiom in your example. It's much easier to read and understand.

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Multiline scripts (we mostly target one-liners)

When you need to publish multiple packages and want to avoid your contributors having to open PRs on many separate repositories whenever they want to make a change.

when projects want to keep strict boundaries within their code and avoid becoming an entangled monolith. This is for example the case for Yarn itself, or many enterprise codebases.

This pattern is often called monorepo when used in conjunction with a repository.

Given that we historically didn't release many majors, some people have started to colloquially call "Yarn 2" everything using this new codebase, so Yarn 2.x and beyond (including 3.x). This is incorrect though ("Yarn 2" is really just 2.x), and a better term to refer to the new codebase would be Yarn 2+, or Yarn Berry (which is the codename I picked for the new codebase when I started working on it).

The purported reason seems to be the claim that some people find "master" offensive. (FWIW I'd give that explanation more credence if the people giving it seem to be offended themselves rather than be offended on behalf of someone else. But whatever, it's their repo.)

git remote set-head origin -a

I think the above answers what you actually wanted to know, but to go ahead and answer the question you explicitly asked...

I reported this as a bug until proven otherwise

This is for those who purchased our Humble Bundle at the Tier 1 level ($1). First, click add to cart. Do not remove this item from your order - it will also be discounted to $0.Once this is added to the cart, it will automatically add the appropriate products. Enter the coupon you were given in your Humble Bundle receipt to get 100% off.  Be sure to use normal checkout. PayPal, Apple Pay, and Google Pay will not work with the coupon code.  On the checkout page, scroll all of the way down and the coupon code field is on the bottom right. You will not have to enter any card information as the coupon code you were given from Humble Bundle takes 100% off and removes the card information fields. If you are asked to enter card information, something was done incorrectly.

(OP means Original Poster)

if printf '%s\0' "${array[@]}" | grep -qwz $value

for pathname do

Your "driver" (wrapper, really) script

#!/bin/sh if [ "$#" -eq 0 ]; then set -- /dev/stdin fi for pathname do gawk -f awk_prac.awk "$pathname" done

if [ "$#" -eq 0 ]; then cat else printf '%s\n' "$@" fi |

if [ "$#" -ne 0 ] then printf '%s\n' "$1" else cat fi |

if (( ${#} == 0 )) ; then while read -r __my_function ; do my_function "${__my_function}" done else target_utility "${@}" fi

Also unclear why the answer is criticized for providing a "more general case" since the OP said "You are right, this [base64] was just used as an example, though.

target_utility

The lonesome cat isn’t useless.  UUOCs are typically characterized by having exactly one filename argument; this one has none.  It connects the input to the function (which is the input of the if statement) to the output of the if statement (which is the input to the base64 –decode statement)

Well, here’s a non-recursive solution in which the main commands appear only once:

resolved through use of recursion

(It seems reasonable to assume users are often expected to occasionally adapt answers rather than expect to use them verbatim.)

This answer is one of various possible solutions for a "Bash function that accepts input from parameter or pipe" since the OP indicated [in a comment] that base64 was not the actual problem domain. As such, it makes no attempt to assure input is able to be directly read from a file.

but in a different situation target_utility "${@}" could represent more complex code

Though the OP's issue may not present a problem ideally resolved through use of recursion, other reader's problems may benefit from using it, or, from considering use of an wrapper function:

Duplicating non-trivial code in both the if and in the else could create unnecessary issues.

If one had to deal with the drain of such critique for every answer, perhaps site usage would go down. People have lives to lead and the OP is apparently already happy. IMO, it is time to move on.

n the end, this site is about helping community. All the associated answers and comments are available for a visitor to peruse and consider. It is decidedly less valuable to the community when all answers are identical.

he value of what really seems to be nitpicking seems questionable even if there is also value in a judicious hunt for theoretical ideals.

The title of the question is what triggered the process of finding this Q/A for material that aided development of the above to solve a real life problem described by the title. The OP declared that base64 decode was not the "real" problem; pedantic constraint of answers to a particular "example" seems less helpful. When this question and its answers were key to helping solve real problems, alternate answers can be gifts to the community in recognition of the fact that many more people will use this Q/A to solve problems. Since the answer is on-topic per the title, I feel it is "game on".

The answer credits others while solving a problem that wasn't optimally solved by other (helpful) answers at the time. I shared to help others. It is up to a reader to select answers and review for appropriateness to their needs. This almost looks like an attack when all that was required was an alternative answer standing on its own merits or demerits.

You should never rely on the presence or contents of anything under the .git directory. That's git's territory, not yours or the build system's. Use it's plumbing commands to get access to the information you need, rather than trying to read files directly. Git provides no guarantee about the location or contents of any of those files as far as I'm aware.

Note that UTF-8 characters can be used in branch names:

>, ==> and -> are valid branch names

This is not specific to Git-- it's part of how POSIX shells process commands. When you don't have quotes (or a preceding backslash), $ign is interpreted as an empty shell variable, so git only sees 'pew'.

Master (master/main) branch. The default production branch in a Git repository that needs to be permanently stable. Developers can merge changes into the master branch only after code review and testing. All collaborators on a project must keep the master branch stable and updated.

You can pre-seed your less pager with a search pattern so that you can move between files with n/N keys: [pager] diff = diff-so-fancy | less --tabs=4 -RFXS --pattern '^(Date|added|deleted|modified): '

xdg-mime default augmented-open.desktop x-scheme-handler/file-line-column This registers the augmented-open.desktop handler as the default handler for URLs using the file-line-column:// protocol.

for best results pipe rg --json output to delta: this avoids parsing ambiguities that are inevitable with the output of git grep and grep

Pull requests are quite welcome, and should target the next branch.

Nix

diff-so-fancy strives to make your diffs human readable instead of machine readable

The most popular is probably antigen but it's only in maintenance mode.

Every commit which is merged into main is considered a stable release. Every open PR is considered a beta release that I test locally.

Regression in 3.13: custom matcher hash argument improperly converted to keyword args, results in ArgumentError

Its a bit tricky because of the ambiguity of how the args get presented. You can see through the little demo the args are presented the same way whether its a straight kwargs or a hash, but the assignment of the args to parameters is different. def foo(*args) puts args.inspect end def bar(x=1, a:2) puts "x:#{x} a:#{a}" end foo(:a => 1) # [{:a=>1}] foo({:a => 1}) # [{:a=>1}] bar(:a => 1). # x:1 a:1 bar({:a => 1}). # x:{:a => 1} a:2

“…” would be cool, but (unless I’ve missed something in Ruby 3.2+), it can only delegate all args, and foo(1, …) is impossible.

The main change with Ruby 3.0 is that it differentiates between passing a hash and passing keyword arguments to a method with variable or optional keyword parameters. So def my_method(**kwargs); end my_method(k: 1) # fine my_method({k: 1}) # crashes

my_func(1, 2, 'foo' => 1, :kw => true) # ArgumentError: unknown keyword: "foo" even though Hash.ruby2_keywords_hash?(args.last) returns true.

even though Hash.ruby2_keywords_hash?(args.last) returns true. 🤯 And this statement (from #366): # If the last argument is Hash, Ruby will treat only symbol keys as keyword arguments # the rest will be grouped in another Hash and passed as positional argument. doesn't seem to be correct, at least in Ruby 3.0.

Yes, but to what version? A patch version only, e.g. you released 1.0.0, so the "next" version is 1.0.1? Why not 1.1.0? You don't know ahead of time what version you'll be releasing until it's actually released

The increment-after-release model makes sense for branching too. Suppose you have a mainline development branch, and you create maintenance branches for releases. The moment you create your release branch, your development branch is no longer linked to that release's version number. The development branch contains code that is part of the next release, so the version should reflect that.

Update email template to indicate that the link needs to be kept secure (e.g. do not share it)

Learning Blender 3rd Edition

Game Programming Algorithms and Techniques

Games, Design, and Play

Fundamentals of Game Design 3rd Edition

Introduction to Game Design, Prototyping, and Development 3rd Edition

This follows on a fairly widespread practice in various programming languages to use a leading underscore to indicate that a function or variable is in some way internal to a library and not intended for the end-user (or end-programmer).

accepting an answer doesn't mean it is the best one. For me it is interesting how argumentation of some users is reduced to "Hey, the editor has 5000+ edits. Do not ever think that a particular edit was wrong."

I'm not sure if I should write it in the answer directly, but I could also say that when an OP simply rolls back an edit without preemptively stating any reasoning in a comment etc., that tends to create the impression that OP is misguidedly claiming "ownership" of the content or feels entitled to reject changes without needing a reason.

Our goal is to have the best answers to every question, so if you see questions or answers that can be improved, you can edit them.

In fact, I think this self-answered Q&A of yours was already quite good by the standards of the site, and very useful - I've used it to close other duplicates several times. As someone who wears a "curator" hat around here, I want to make questions like this even better - as good as they can be - and make it clear to others that this is the right duplicate target to use when someone else asks the same question.

Then I gave the question a longer, more descriptive title: I made it an actual question (with a question mark and everything), and replaced the term "lazy evaluation" with a more concrete description. The goal is to make the question more recognizable and more searchable. Hopefully this way, people who need this information have a better chance of finding it with a search engine; people who click through to it from a search page (either on Stack Overflow or from external search) will take less time to verify that it's the question they're trying to answer; and other curators will be able to close duplicates more quickly and more accurately. This edit also improves visibility for some related questions (and I made similar changes elsewhere to promote this one appropriately).

We do want to avoid going around in circles on matters of style, and there has historically been a ton of discussion on Meta about what kinds of style edits are appropriate and what variation in style is acceptable. But in general, an author whose post is edited can expect to be out-voted - especially when the edit has a basis in policy. In short, these changes were not simply about "style", but about the site's goals for clarity, focus, precision and overall quality.

In principle, therefore, everyone has a say in the editing of posts, including the author. However, authors do not "own" the content here; it is licensed irrevocably to the site under a permissive Creative Commons license, which enables those edits.

As you've seen, there is no DM system, but you can invite users to chat directly. More generally, consider commenting on the question itself and @-ing the user who made the edit(s). To my understanding, this should work, and it may allow for a quick explanation that doesn't require going in to chat.

Try adding \ before your ls, e.g.: \ls | xargs file.

The input format of the xargs command doesn't match what any other command produces.

The input format of the xargs command doesn't match what any other command produces. Yes, it's bizarre. With -I, xargs ignores indentation, which is why the file names with initial spaces are mangled. Do not use xargs except with the -0 option or when you know your input doesn't contain characters that would confuse it.

The ls command doesn't expand wildcards, it's the shell that does. Do not parse the output of ls, it's practically never needed and often breaks something.

_

find . -maxdepth 1 -mindepth 1 | xargs -d'\n'

Do not pass arguments right into subshell, it's as unsafe as eval.

DO NOT PARSE LS.

Do not use xargs without -d when you do not want ' " \ to be handled specially.

This can lead to confusion if you expect to be able to access a Mash value through the property-like syntax for a key that conflicts with a method name. However, it protects users of your library from the unexpected behavior of those methods being overridden behind the scenes.

Comparing to Mash your custom class lacks mash-like deep initializer which is a different concern from MethodAccess. So you just need a smart initializer extracted from Mash (just like MergeInitializer but deep), probably implemented as a separate extension. So It's a initializer issue, not an issue of MethodAccess.

Wine isn't an emulator, it's a collection of code that interprets Windows executables for various different systems: "Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop." https://www.winehq.org/ FWIW, the Steam Deck relies heavily on a derivative of Wine for getting existing programs to run on the platform.Some programs will actually run faster under Linux + Wine than under Windows, which wouldn't be possible for an emulator running on the same hardware system.

Regardless of what your arguments are, the personal reasons of the developer are what matters for what platforms this game is provided on. You can choose to pay for the game, or not. Paying for the game supports the developer, and allows them to develop more. It is not reasonable to argue that someone should have put in additional unpaid effort to do something for unknown future benefit, or that they should charge less for a game because it's only available on one platform; that's their choice, and their decision.For context, development of Taiji was started in mid 2015; it took seven years to finish. That's with the Commercial Game Engine, and even with that, there were platform-based bugs that needed to be worked around (issues that won't be present on other platforms, or will have different presentations); here's just one of those, involving an issue around mouse sluggishness:https://taiji-game.com/2020/07/13/68-in-the-mountains-of-madness-win32-wrangling...If the developer is not already familiar with Linux, then there's a small mountain of language barriers around using Linux that needs to be overcome first, before being able to get to the game development phase. It's rare for game development to work on different platforms when it can't be tested on those different platforms. While it might be easy to cross-compile on a Windows system (e.g. via IL2CPP), that's only if everything works perfectly (which is unlikely to be the case). 

The high-level view of your responses are that they are an attack on the developer of this game, someone who has already put in seven years of effort to get to this point already (as demonstrated in the game development blog). The developer does not need that, and digging in deeper to become more aggressive will not help you get what you want. There are reasons for not developing on Linux, as there are for other platforms (e.g. MacOS, PS5, Switch). As great as it would be to just drop the same code on different platforms and have it work perfectly every time, that's not the reality. There are *always* platform-specific issues that crop up: "If you don't design your software with platform-nonspecificity in mind, then it just makes it harder. Nothing is truly impossible to port, disregarding hardware capabilities and computing speed. There's no such comprehensive "tool" for porting games to other platforms, though, since they all work differently under the hood." https://gamedev.stackexchange.com/questions/49375/what-are-the-main-requirements... Regardless of your own personal opinions on what should or shouldn't be done, the developer has already answered your question about Linux ports, in particular mentioning that it is appropriate for users to use Wine (in the form of Proton) to play Taiji on Linux. And, if the game not working on Linux is a showstopper for you, the developer recommends you consider purchasing on Steam due to a better refund poli

This library is no longer called vCardMate!

Why would a text message service require Location (GPS) permissions? Anyway I enabled this Location permission for testing. Heureka!!! Suddenly I was able to send text messages again to all the contacts which previously didn't work. The "Not sent, tap to try again" error was gone.

Glimmer DSL for Web intuitively supports both Unidirectional (One-Way) Data-Binding via the <= operator and Bidirectional (Two-Way) Data-Binding via the <=> operator,

Following a policy change by WhatsApp, many people are looking at alternative messaging options. The new WhatsApp policy requires people to share data with Facebook and associated companies.

WhatsApp is doing the exact thing it said it wouldn't do when it was acquired by Facebook seven years ago.

Driver management through Selenium Manager is opt-in for the Selenium bindings. Thus, users can continue managing their drivers manually (putting the driver in the PATH or using system properties) or rely on a third-party driver manager to do it automatically. Selenium Manager only operates as a fallback: if no driver is provided, Selenium Manager will come to the rescue.

How to use “case” to match class names? (=== not so funny)

def ===(other) @holder == other end

One way to potentially get around this is to have an object that simple holds a class and overrides the === operator to make case work properly:

The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. The "Sender:" field specifies the mailbox of the agent responsible for the actual transmission of the message.

In my experience, client software usually honors Reply-To, but I have only been exposed to a small fraction of the wide array of client software that people might use.

The autological word "eggcorn" is itself an eggcorn, derived from acorn.

our Rule 8 of Commas says, “Use commas to set off the name, nickname, term of endearment, or title of a person directly addressed.” Therefore, we would write: Good Morning, Mary. However, it is also acceptable to write Good morning, Mary. Good practice is to decide on a style and be consistent.

Formal application of punctuation with a salutation that doesn’t include an opening adjective (e.g., Dear Sir) would call for a comma preceding the person’s name as a proper form of address (e.g., Good afternoon, George). Whether to follow the name with a comma or a colon would be determined by the relationship’s context: Good afternoon, George, (comma for familiar) Good afternoon, George: (colon for formal) At the same time, you are correct in observing that current communication often omits the salutatory comma of address, particularly for shorter greetings (e.g., Hi Erik). This is becoming more common and acceptable, and it would be a matter of writer’s preference. You would be correct writing either Hi Erik or Hi, Erik. We would advise keeping the comma for longer or phrasal greetings such as Good afternoon, George.

The mortgage document which secures the promissory note by giving the lender an interest in the property and the right to take and sell the property—that is, foreclose—if the mortgage payments aren't made.

Some frameworks call this “template inheritance”. In this example, we might say that the application layout “inherits from” or “extends” the base layout. In Rails, this is known as nested layouts, and it is a bit awkward to use. The standard Rails practice for nested layouts is complicated and involves these considerations

But what if you want to reuse one layout within another?

Here’s my common practice: Every page in the app needs the standard HTML boilerplate with my common stylesheets and JavaScripts. I need a layout that provides these, but makes no assumptions on the actual body of the page. This is my “base” layout. Most – but not all – pages in the app need a common header and footer. This is my “application” (default) layout. I’d like the application layout to reuse the base layout to keep my code DRY.

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

Tracking dependent relationships between Issues and whether something is blocking another piece of work is important with any project process because it creates a central hub where everyone can communicate what’s needed without relying solely on meetings or comments to uncover important connections.

his is a killer-feature which I miss since I switched from Jira to GitLab. I'm using GitLab on a daily basis even in solo-projects and I miss this every day. Everybody would find value to this when using Issues and realize, that some depend on others (so basically always).