# login Published articles for login. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## "Regex for Rows": Simplifying Pattern Detection in SQL with MATCH\_RECOGNIZE DevFeed: ["Regex for Rows": Simplifying Pattern Detection in SQL with MATCH\_RECOGNIZE]() Original publisher: [Read original article]() Author: Kent Marten; Sergei Fedorov Published: 2026-09-16T17:14:05Z Content type: tutorial Language: en Sources: [Databricks]() Topics: [SQL](), [databricks](), [Cybersecurity](), [Security & Privacy]() Tags: [count](), [cybersecurity](), [databricks](), [failed](), [false-positives](), [functions](), [login](), [partition](), [product](), [real-time](), [regex](), [sql](), [window-functions]() ### AI overview This tutorial explains how Databricks supports SQL MATCH_RECOGNIZE for detecting ordered event patterns. It shows how the clause can simplify sequence detection, including identifying repeated login failures followed by a successful login, compared with complex SQL queries and window functions. ### Source excerpt Imagine you work in cybersecurity and you have a table that tracks login attempts... ## Self-service peering with a PeeringDB login DevFeed: [Self-service peering with a PeeringDB login]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-07-27T00:00:00Z Content type: opinion Language: en Sources: [AS215248 - Notes]() Topics: [Networks](), [OAuth](), [Server]() Tags: [automation](), [bgp](), [dashboard](), [ipv4](), [ipv6](), [ixp](), [login](), [mail](), [networks](), [oauth](), [peering](), [permission](), [request](), [self-service]() ### AI overview The article describes a self-service peering portal that uses PeeringDB OAuth to authenticate users, verify ASN update rights, and offer exchanges where both networks are present. Requests create disabled sessions for manual approval, with inherited filtering and validation policies, notifications, and approval-based removal. ### Source excerpt Peering requests used to be mail ping-pong. Now you log in with PeeringDB on the peering page, pick an exchange, and the session is waiting for my approval. ## The Most Expensive Milliseconds Are Unmeasured DevFeed: [The Most Expensive Milliseconds Are Unmeasured]() Original publisher: [Read original article]() Author: Divya Gupta Arora Published: 2026-06-03T17:11:58Z Content type: article Language: en Sources: [Expedia]() Topics: [Mobile](), [render](), [ui]() Tags: [case-study](), [devops](), [engineering](), [login](), [mobile](), [mobile-apps](), [mobile-performance](), [observability](), [performance](), [release](), [software-engineering](), [technology-investments](), [time-to-interactive](), [ui](), [visibility]() ### AI overview This Expedia Group engineering case study describes extending Native Time to Interactive across mobile login screens. The metric was used to evaluate technology investments, compare platform behavior, and detect performance regressions that existing system-health signals did not reveal. ### Source excerpt Expedia Group Technology -- EngineeringHow a screen-level performance metric reshaped platform decisions, engineering ownership, and release disciplinePhoto by Pietro De Grandi on Unsplash For the last few years, my responsibility has been straightforward to state but hard to execute -- owning the traveler login experience across mobile platforms. Not just whether a feature works, but whether it feels responsive, predictable, and trustworthy in the moments that matter most. During login, those moments are unforgiving: if a login screen hesitates travelers don't interpret it as 'a slow render', they interpret it as risk. And when the majority of travelers interact through our mobile apps, performance stops being a technical concern and becomes a product promise. This post is a case study of how, within Expedia Group™'s login domain, we extended Native Time to Interactive (NTTI) across login screens -- moving performance from a late-stage check to a first-class signal we can use to validate technology investments, compare platform behavior, and prevent silent regressions as we ship. The Problem: Mobile reliability rarely fails loudly Mobile performance rarely breaks with a crash. It usually degrades quietly, a button takes a beat longer to respond a screen looks ready, but taps don't register the UI stutters just enough to feel "off" Those are the expensive milliseconds -- because they erode trust without triggering obvious alarms. In our login flows, we were shipping consistently, evolving a major part of our stack, and supporting increasing product complexity. Yet we didn't have a consistent way to answer the user's real question -- "When can I actually use this screen?" Why our existing signals failed We were not blind. We tracked many useful things, crashes and ANRs backend latency and service SLIs some component-level timing signals limited Time to Interactive tracking on onboarding and initial login But we had a gap -- we had visibility into system health, not screen ## Keycloak 26.5.5 released DevFeed: [Keycloak 26.5.5 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2026-03-05T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [saml](), [Security](), [Authentication]() Tags: [2026](), [authentication](), [broker](), [cve](), [download](), [idm](), [idp](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [login](), [migration-guide](), [openid-connect](), [release](), [saml](), [security](), [sso]() ### AI overview Keycloak 26.5.5 was released on March 5, 2026. The release includes security fixes for SAML broker authentication bypass, disabled identity provider enforcement, disabled SAML identity provider login, and encrypted assertion injection. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Security fixes #46909 CVE-2026-3047 SAML broker: Authentication bypass due to disabled SAML client completing IdP-initiated login #46910 CVE-2026-3009 Improper Enforcement of Disabled Identity Provider in IdentityBrokerService #46911 CVE-2026-2603 Disabled SAML IdP still allows IdP-initiated broker login #46912 CVE-2026-2092 saml broker encrypted assertion injection ## Configurar Fail2Ban para proteger servicios DevFeed: [Configurar Fail2Ban para proteger servicios]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-28T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Fail2ban](), [OpenSSH](), [nginx](), [Debian](), [Ubuntu](), [rhel 9]() Tags: [debian](), [error](), [fail2ban](), [internet](), [ip](), [login](), [logs](), [nginx](), [rhel](), [rhel-9](), [ssh](), [ubuntu]() ### AI overview A practical guide to installing and configuring Fail2Ban to protect SSH, Nginx, and other services from brute-force attacks. It covers jail configuration, custom Nginx filters, nftables and iptables actions, status checks, and manually unbanning IP addresses. ### Source excerpt Guía práctica para instalar y configurar Fail2Ban: protege SSH, Nginx y otros servicios contra ataques de fuerza bruta. ## Keycloak 26.0.1 released DevFeed: [Keycloak 26.0.1 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2024-10-17T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [migration](), [Authentication]() Tags: [admin](), [authentication](), [cypress](), [firefox](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [login](), [migration](), [migration-guide](), [openid-connect](), [quarkus](), [release](), [saml](), [sso]() ### AI overview Keycloak 26.0.1 is released with enhancements and resolved bugs across the Operator, storage, authentication, LDAP, Admin Console, login UI, documentation, and other components. The article directs readers to the Keycloak downloads page and migration guide. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #32152 Clarify the behaviour of multiple Operator versions installed in the same cluster operator #33275 Better logging when error happens during transaction commit storage Bugs #8935 keycloak.js example from the documentation leads to error path adapter/javascript #19358 Issue with concurrent user & group delete, unable to cleanup resource server user-policy & group-policy authorization-services #31848 Repeated email verifications while logging in through IDP caused by email case sensitivity authentication #32266 LDAP Import: KERBEROS_PRINCIPAL not updated when UserPrincipal changes and user already exists ldap #32617 Nightly Cypress tests for the Admin Console are failing on Firefox admin/ui #32844 Login V2: Missing "dir" attributes login/ui #32847 Admin UI defaults to master realm even without permissions to it admin/ui #32962 Possible issue with unavailable CryptoIntegration when using keycloak-authz-client with private_key_jwt and ECDSA algorithm oidc #33513 Can get authorization code on a non verified user with some specific kc_action (AIA) oidc #33539 Keycloak In Docker: ERROR: Strict hostname resolution configured but no hostname setting provided docs #33549 Flaky test: org.keycloak.testsuite.broker.KcOidcBrokerTest#testPostBrokerLoginFlowWithOTP_bruteForceEnabled ci #33557 Unable to submit forms in Safari account/ui #33576 Broken links / anchors after KC26 release docs #33578 In imported realms, the ability to use environment variables has disappeared import-export #33585 Fix runaway asterisk formatting in TLS documentation docs #33638 Non-optimized start command gives erroneous warnings for runtime spi options dist/quarkus #33642 RTL not working on keycloak.v2 login template login/ui #33645 keycloak-js register broken: createRegisterUrl not awaited adapter/javascript #33699 Failure to red ## Securely Implementing IdP-initiated SAML2 Login DevFeed: [Securely Implementing IdP-initiated SAML2 Login]() Original publisher: [Read original article]() Author: info@goteleport.com (Joel Wejdenstål) Published: 2022-10-06T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [saml](), [Single sign-on (SSO)](), [Authentication](), [Security]() Tags: [authentication](), [blog-post](), [deep-dive](), [idp](), [implement](), [login](), [saml](), [security](), [sso]() ### AI overview This tutorial explains the SAML 2.0 protocol, IdP-initiated single sign-on, the roles of identity and service providers, and considerations for implementing the authentication flow securely. ### Source excerpt In this blog post, we'll deep-dive into the SAML2 protocol, how IdP-initiated login works and how to implement it securely. ## Web Authentication at Headspace using Auth0 DevFeed: [Web Authentication at Headspace using Auth0]() Original publisher: [Read original article]() Author: Headspace Published: 2021-04-26T20:43:56Z Content type: tutorial Language: en Sources: [Stories by Headspace on Medium]() Topics: [Authentication](), [Auth0](), [Web](), [Cookies](), [browser]() Tags: [auth0](), [authentication](), [browser](), [cookies](), [login](), [password](), [server](), [web](), [web-authentication]() ### AI overview This article explains modern web authentication using usernames, passwords, session tokens, and browser cookies. It describes Headspace's authentication requirements across web, backend, iOS, and Android applications and explains why the company chose Auth0 as its authentication provider. ### Source excerpt Author: Jesse Bond, Senior Software Engineer, Web Introduction: How does modern authentication work? Authentication allows users to securely log into a system and verify that they are who they say they are in subsequent requests. On today's web, this usually involves creating an account using a combination of username and password. Let's start with a quick refresher on how modern web authentication works. The first step is always a user submitting their login credentials into a form. Once the form is submitted, the server will determine whether or not the username and password match that of a previously registered user. If they do match, the server will return what is known as a session token. A session token is a unique identifier that authenticates requests as coming from the same user that just logged in. It's important to note that session tokens usually are temporary and have an expiration, which is determined by the server. Now that the user has a session token, each request will need to submit the session token to ensure authentication. It might sound tedious to have to submit the session token on each request, but have no fear, the cookie is here! Cookies are small bits of information that the browser stores for a domain. Cookies are also automatically submitted when a request is sent by the browser. Does this sound like a great way to handle the session token or what? Correct! Session tokens are almost always stored in a browser cookie to make authenticating requests a breeze. Authentication requirements Headspace has a large number of Single Page Apps, backend services, websites, and iOS and Android applications. We needed a robust solution for authentication that met the following requirements: Multiple platform and language support Scalable to millions of users Reliable with high uptime Ability to separate our users into different groups with varying permissions (i.e., admins vs. standard users) Ability to restrict user access to certain applications. Fo ## The limitations of offering only magic-link authentication DevFeed: [The limitations of offering only magic-link authentication]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-12T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Authentication](), [passwords](), [Slack](), [browser]() Tags: [authentication](), [browser](), [login](), [passwords](), [slack]() ### AI overview The author criticizes SimpleAnalytics for offering only magic-link authentication. They explain that a three-hour email-link duration makes account access difficult when a co-founder cannot access the author's email, and argue that an additional authentication option would better support shared accounts. ### Source excerpt So I just signed up a new service, SimpleAnalytics because, well, if I never look again at Google Analytics then I'll be happy as hell. I can't say enough bad things about Google Analytics - and I've been using it since it was Urchin. Simple Analytics appears to be an impressive tool and I want to launching something, well, TODAY so when they offered a simple signup and easy to use workflow, I bit. I even gave them a credit card. And then I went to add my co-founder on this project to it and, well, crap. They only offer Magic Link authentication. Sigh. censored Magic Link Authentication is that beautiful concept that Slack pioneered where they just: Email you a link to authenticate with. You click the link and WHAM! You're in. No account stuff. No password. And it feels like magic. I was blown away by this the first time I used it in Slack and I, well, I actually did a small bow towards Silicon Valley and the awesomeness that is Stuart Butterfield (he is the guy behind Slack, the guy behind Flickr and the guy behind Game Never Ending). Stuart is awesome (imho but so is Caterina also of course). But Magic Link Authentication isn't supposed to be your only approach to authentication. Tomorrow I leave my home office for a long weekend. The Magic Link Authentication email that I just forwarded to my partner on this project has a duration of only 3 hours. My partner doesn't have access to my email (and nor should they; it is my damn email). So let's say that they somehow need to re-authenticate (browser crash; cookie expire; whatever), their only option is to send me a text message that begs: Please kind partner of mine - will you request a Magic Link again and then wait for the email to arrive to you and then please forward it on to me? That's absolute crap imho. Usernames and passwords are not that damn hard. As a company SimpleAnalytics is on a $360,000 run rate - figure out a way to add a second person onto the damn account. Disclaimer For all my bitching: I like the ## Back to basics: Navigation DevFeed: [Back to basics: Navigation]() Original publisher: [Read original article]() Author: Niek Haarman Published: 2018-10-25T09:12:40Z Content type: tutorial Language: en Sources: [Stories by Niek Haarman on Medium]() Topics: [navigation](), [Android](), [Mobile](), [Development]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [development](), [flow](), [fragments](), [login](), [mobile](), [navigation](), [onboarding](), [payment](), [screen](), [shopping](), [state]() ### AI overview A fundamentals-focused guide to in-app navigation in Android applications. It explains the back stack, reusable navigation flows, conditional paths based on user state, and how navigation responsibilities are handled by Activities and Fragments. ### Source excerpt Previously I talked about the unfortunate design of the Activity class, and I went back to basics regarding screens in an application. This time, we're going back to basics regarding in-app navigation. What is meant by 'navigation'? In a typical mobile application, a user can navigate from one screen to another. Traveling through an application builds up a navigational state; in Android this is traditionally done with a back stack. Activities can start new Activities which get pushed upon a stack. When the user presses back, the top Activity gets popped off the stack, to reveal the previous Activity. You can modify how Activities are created and pushed upon the stack with several flags and attributes, which are described at length on the Understand Tasks and Back Stack page. The back stackFlows In a non-trivial application, there are often multiple 'flows' that can be defined: there might be a login flow, an onboarding flow, or a flow that takes you through a payment process. In the latter case, you might have a series of screens that start with a description of the user's shopping cart, followed by forms to enter shipping and payment information. Such flows are usually completely self contained, and can be reused when necessary. It may be possible to start a specific flow from anywhere in the app, allowing for dozens of paths through your application to exist. An example payment flow for a shopping application.Conditional navigation In your typical application, there is no strict sequence of screens that will appear in a fixed order. Depending on user input, the user can travel through different paths through your application. A dashboard screen for example can have multiple buttons that all lead the user to a different screen. Another thing to consider is that the next state of the navigation state is dependent on the some conditional state. If the user already has entered shipping and payment info a previous time, we may want to skip these forms and go straight t ## Understanding Fragment Transactions and Back Navigation DevFeed: [Understanding Fragment Transactions and Back Navigation]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Transactions](), [navigation](), [App](), [implementation]() Tags: [android](), [app](), [blogs](), [events](), [fragment](), [fragments](), [implementation](), [login](), [navigation](), [rewrite](), [screen](), [transactions]() ### AI overview This tutorial investigates unexpected Android Fragment behavior when login-related Fragment transactions interact with back navigation. It explains that the transaction manager saves executed transactions rather than the Fragments themselves, which can leave multiple Fragments visible after navigating back. ### Source excerpt Do Fragment transactions and back navigation have no more secrets for you? Well then you should try to solve the mystery in this post, where a Fragment (literally) came to haunt us... ## How to Inspect a Developer's SSH Session as Root DevFeed: [How to Inspect a Developer's SSH Session as Root]() Original publisher: [Read original article]() Author: Tom Published: 2016-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [ssh](), [configuration](), [systems]() Tags: [agent](), [bash](), [bastion](), [bastion-host](), [developers](), [how-to](), [linux](), [login](), [ssh]() ### AI overview A tutorial explains how a root user can inspect a developer's SSH session to troubleshoot login problems, including cases involving bastion hosts and SSH agent forwarding. It notes that this should only be done on systems the operator controls and is authorized to access. ### Source excerpt It happen to me all the time that one of developers notifies me about some kind of problem that I can't confirm from my account. Sometimes it was because of bad ssh keys configuration, other times file permissions, mostly such stuff. It's sometimes convenient to "enter into someone's shoes" to see what's going on there. If you're root on machine you may do that like this: Switch to developer user su developer - Easy one but that's not enough for all cases. When you use bastion host (or similar solutions) sometimes users have connection problems and it's harder to check. When such user have ForwardAgent ssh option enabled you may stole this session to check login problems. ## Animated login and signup forms DevFeed: [Animated login and signup forms]() Original publisher: [Read original article]() Author: Stanko Published: 2016-02-22T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [CSS](), [Forms](), [Web Development](), [browser]() Tags: [browser](), [css](), [forms](), [github](), [login](), [responsive]() ### AI overview A pure CSS implementation of animated login and signup forms uses the :target selector to switch between states. The article also describes a responsive solution and notes that both states can be bookmarked and controlled with browser navigation buttons. ### Source excerpt Well I saw a pretty nice mockup on Dribbble and decided to make it for fun. It didn't include a mobile/responsive solution, so I came up with my own. Check the demo. This is a pure CSS solution - it uses the :target selector for changing states. Find more about :target on MDN. This is neat, as it also can be bookmarked in both states, and browser buttons work too. Grab the code on GitHub. ## Screencast: Using Pretender to mock a server with Ember.js DevFeed: [Screencast: Using Pretender to mock a server with Ember.js]() Original publisher: [Read original article]() Published: 2014-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [JavaScript](), [test](), [Library](), [GitHub]() Tags: [branch](), [ember](), [integration-test](), [javascript](), [js](), [library](), [login](), [mock]() ### AI overview A screencast demonstrates how to use Pretender, a JavaScript mock server library, in an Ember.js integration test. The source code for the login application is available on GitHub, with the finished version in the pretender branch. ### Source excerpt Recently I fell in love with Pretender, the mock server library in Javascript, so I decided to record a screencast showing how to use it in an Ember.js integration test: The source code for the login application is on github. The finished version is in the pretender branch. ## Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic DevFeed: [Apache: ograniczenie dostępu dla zalogowanych użytkowników z mod\_rewrite i mod\_auth\_basic]() Original publisher: [Read original article]() Author: Tom Published: 2012-09-09T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Mod\_rewrite](), [.NET Framework]() Tags: [apache](), [auth](), [debian](), [linux](), [login](), [mod-rewrite](), [rewrite](), [security](), [user]() ### AI overview This Polish tutorial explains how to use Apache mod_rewrite with mod_auth_basic to redirect authenticated users to directories named after their logins and prevent access to other users' directories. It describes comparing the URI login with the REMOTE_USER value using RewriteRule and RewriteCond backreferences. ### Source excerpt Niedawno trafiłem na ciekawy problem w mod_rewrite - by przekierowywać użytkowników logujących się jednym z modułów mod_auth_basic do dedykowanych im katalogów, równocześnie blokując dostęp do katalogów innych użytkowników. Nie brzmi to jakoś strasznie ale problem okazał się być całkiem nietrywialnym. Teoretyczne rozwiązanie sprowadzało się do wyszukania loginu użytkownika ze ścieżki URI i porównania z nazwą użytkownika ze zmiennej %{REMOTE_USER} - jeśli wartości się różnią to Forbidden. Ale szybko okazało się że w RewriteCond zmienne z dopasowań można podstawiać tylko w pierwszym parametrze i że o ile można RewriteCond'y połączyć wyrażeniami logicznymi typu AND/OR to nie ma możliwości porównania czy dopasowania z kolejnych RewriteCond'ów są identyczne. Po kilku dniach szperania w dokumentacji i różnych tutorialach udało mi się trafić na jedną wartościową wskazówkę ale tej stronki już nie ma, więc opiszę problem dla potomnych. ## fail2ban - regułki dla dovecot'a DevFeed: [fail2ban - regułki dla dovecot'a]() Original publisher: [Read original article]() Author: Tom Published: 2011-11-28T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Authentication]() Tags: [auth](), [authentication](), [debian](), [fail2ban](), [filter](), [linux](), [login](), [mail](), [port](), [security]() ### AI overview This tutorial explains how to configure fail2ban on Debian to block repeated authentication failures against Dovecot POP3 and IMAP mailboxes. It provides a custom Dovecot filter with a failregex, a jail configuration for POP3/IMAP ports, log path, retry limit, and optional timing values, followed by restarting fail2ban. ### Source excerpt Domyślna konfiguracja fail2ban'a (na Debianie) nie zawiera reguł pozwalających na blokowanie prób włamań na skrzynki POP/IMAP dla dovecota (no chyba że korzystamy z saslauthd). Można szybko utworzyć własny zestaw filtrów co przedstawię poniżej. Tworzymy plik: /etc/fail2ban/filter.d/dovecot.conf [Definition] failregex = (?: pop3-login|imap-login): .*(?:Authentication failure|Aborted login \(auth failed|Aborted login \(tried to use disabled|Disconnected \(auth failed|Aborted login \(\d+ authentication attempts).*rip=(?P\S*),.* ignoreregex = Później dopisujemy na końcu pliku: /etc/fail2ban/jail.conf [dovecot] enabled = true filter = dovecot port = pop3,pop3s,imap,imaps logpath = /var/log/mail.log maxretry = 20 # te dwa poniżej wedle uznania - ja mam dobrze ustawione default'y #findtime = 1200 #bantime = 1200 Zostało zrestartować fail2ban'a: ## Mint.com combines online account aggregation, spending categorization, alerts, and savings recommendations DevFeed: [Mint.com combines online account aggregation, spending categorization, alerts, and savings recommendations]() Original publisher: [Read original article]() Author: Map Published: 2008-06-20T00:17:55Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Security](), [Website](), [account](), [email](), [Microsoft]() Tags: [credit-card](), [email](), [file](), [login](), [money](), [security](), [service](), [website]() ### AI overview The article is an opinionated review of Mint.com, describing its online account aggregation, transaction categorization, budget alerts, and personalized savings recommendations. It also discusses security and privacy concerns, including hashed account information and Mint.com's stated promise not to sell user information. ### Source excerpt This week I want to talk about one of the hands-down best sites on the internet. Mint.com, in case you haven't heard about Mint yet, it's like Quicken or Microsoft Money just online. You create an account on the website, login, add your account information. From there mint connects to each of your accounts, pulls down your transaction history, automatically categorizes your spending into categories, and then will send you alerts for budgets or other settings via text or email. Oh, and best of all since it knows where you're spending your money, it tells you how you can save. So since mint sounds great and wonderful, and it indeed is, I'm going to jump straight in and start addressing issues people may already have about this kind of site. The first is security, why would I give all of my account information away to a single place so someone could walk in and take every penny I have? Well first account information is hashed, it's not just sitting in some text file on some desktop, its quite secure. Next, well mint gives you warnings right? So if someone goes and buys a car with you're credit card you'll get a text message about it. Now I may be missing something, but my bank has never offered me that kind of service. Oh and best of all, just because you put your account information, you still have the normal security backing of your bank and liability. Worried about a company having so much information on you? What if I told you in a matter of minutes if I know you're name I could likely have your past 3 residences, phone numbers, and other information. Or for that matter if you're concerned with a company having that information, do you pay cash for everything. Because if you don't the credit card companies have just as much information, and they and other companies often sell this information. Mint.com promises not to do such. So if your argument is that you don't want people to know that much information about you, its a very valid one, but hypocritical if you don