In my mental model of an offline app, I expect instant responses. However, I know to the complexities of apps, the diverse wants of a big, diverse user base that it can be hard/impossible for an app to be well-architected enough to achieve this ideal.
Failover is hard, and there generally aren't hard rules for what to do if data isn't available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care
I appreciate the work you've put into this, but if someone gets into this they are likely to be looking for a next puzzle immediately. They are unlikely to become a recurring visitor; not with just a single puzzle a day. 5 or 10 might work better.
Some day in the near future, the marketing department will wonder why so many people were curious about all of their products after browsing Organic Ground Beef[0]
Indeed, he spelled it the right way, which is the wrong way. He should spell it wrong, which is the right way. :)
I think it is funny that this misspelling hasn't been fixed after all of these years. It was typo'ed in the original http spec in 1996: https://en.wikipedia.org/wiki/HTTP_referer
If the web server is following RFC 8969, it will treat "referrer" as "referer" and throw a 397 TOLERATING to let you know you should change it to the latter on your end. See Section 3.
There are regional variations in the use of doubled or single consontants:
UK: travelling, signalling
USA: traveling, signaling
The double l serves no purpose in these.
However, there is no such UK/USA split in "referring": both use double "r".
There is a phonetic reason for that which is that the second syllable has the emphasis in "refer", unlike "traveling" and "signaling" where the leading syllable has it.
The double "rr" indicates the stressed syllable, without which "refering" and "referer" could be misread with emphasis on the first syllable, like "buffering" or "suffering"/"sufferer".
A native speaker with good intuition for spelling would never write "refering" or "referrer", even if they find "signaling" acceptable.
I created a test group with 3 users and 3 expenses with different payers and payees. After the first reimbursement, the remaining 2 balances were not equal: -0.70 vs. 0.69. After the second, the final balances are:
-0.01
0.00
0.00
Some nice to haves:
- When creating expenses, a select all functionality/default all for "paid for"
- Group status on the /groups page
Failover is hard, and there generally aren't hard rules for what to do if data isn't available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care