Recommended Posts

Having worked in Subway I figured it would be helpful to describe the bread making process.

The bread dough is delivered to the store in boxes, each of which contain about 80 frozen breadsticks. Each stick contains the same amount of dough, though there are some slight discrepancies in length. Each day frozen breadsticks are taken out to defrost. One issue with the length comes at the next stage, as the defrosted bread sticks are supposed to be stretched when transferred into the bread formers (for the flavoured breads the toppings are applied at this stage) - if the bread isn't fully defrosted when it's transferred then it won't stretch. After this they are proofed in a heated cabinet. When the bread reaches a certain size - which is determined by a template - it is cooked. Sometimes bread is underproofed - either because of an inexperienced member of staff or because it is very busy - in which case the bread will end up slightly smaller than it should. After the sandwich has been made it is wrapped, during which it is compressed slightly; further, if it was heated then the moisture causes the sandwich to shrink slightly.

The point is, you're always getting the same amount of bread. And the fillings are applied to a formula, so the amount of veg should always be consistent. I can understand why people feel mislead when a sandwich doesn't measure to exactly one-foot but there are so many variables that the size can't be guaranteed to that level of accuracy. The sandwich pictured was toasted, which causes it to shrink.

The way I see it, would you feel the same way if you paid for a gallon of gas, but only received 92% of that gallon? Same scenario here.

Actually, it's more like buying a book that's normally 180 pages long but your version is only 150 pages because it has smaller print. You're still getting the same content but it's just distributed differently. Complaining that you have less pages is missing the point.

Blows my mind that this is even an issue.... gawd we're such fat asses.

1 inch short on a piece of bread that is mostly fluff but full of carbs... but you still get the same amount of meat and toppings as you would anyways. Who gives a ****.

Feel free to give me 8% of your income...as it's not an issue.

  • Like 2

i always get too much toppings, i always ask for a lot and then i ask for more (since asking for a lot does absolutely nothing... lol)

one extra inch of break does not mean much to me. but i Still think they should fix it... a 12 inch should be a 12 inch.

Actually, it's more like buying a book that's normally 180 pages long but your version is only 150 pages because it has smaller print. You're still getting the same content but it's just distributed differently. Complaining that you have less pages is missing the point.
Actually it's more like buying a book called "180 Pages of Deliciousness (Guaranteed)" but your version has only 150 pages. The deliciousness is probably there as well but (a) the volume of advertised/contracted deliciousness is not the same as the received deliciousness (b) advertising quantities that you can not guarantee is a bad idea.
  • Like 2

I doubt this is some large short-change conspiracy. As has been discussed by the people who work at Subway, you're talking about something that has a ton of variables involved. You want bread that's a perfect 12"? Wait the extra time it takes for them to properly do everything. If you're eating at Subway I doubt you have either the time and/or money. There was one time I ate a sandwich from there and didn't even realize they had forgotten the meat until I went back the next time and they told me. With as mass-produced and mediocre quality as the food is, worrying about the size of your bread shouldn't be a concern.

So what is the point of having laws concerning false advertising?

Why have an official Weights and Measures department?

Sell and advertise something anyway you want and when called on it, accuse those complaining of whinging.

Trivial it may seem, but the laws are there for a reason.

Having worked in Subway I figured it would be helpful to describe the bread making process.

The bread dough is delivered to the store in boxes, each of which contain about 80 frozen breadsticks. Each stick contains the same amount of dough, though there are some slight discrepancies in length. Each day frozen breadsticks are taken out to defrost. One issue with the length comes at the next stage, as the defrosted bread sticks are supposed to be stretched when transferred into the bread formers (for the flavoured breads the toppings are applied at this stage) - if the bread isn't fully defrosted when it's transferred then it won't stretch. After this they are proofed in a heated cabinet. When the bread reaches a certain size - which is determined by a template - it is cooked. Sometimes bread is underproofed - either because of an inexperienced member of staff or because it is very busy - in which case the bread will end up slightly smaller than it should. After the sandwich has been made it is wrapped, during which it is compressed slightly; further, if it was heated then the moisture causes the sandwich to shrink slightly.

The point is, you're always getting the same amount of bread. And the fillings are applied to a formula, so the amount of veg should always be consistent. I can understand why people feel mislead when a sandwich doesn't measure to exactly one-foot but there are so many variables that the size can't be guaranteed to that level of accuracy. The sandwich pictured was toasted, which causes it to shrink.

Actually, it's more like buying a book that's normally 180 pages long but your version is only 150 pages because it has smaller print. You're still getting the same content but it's just distributed differently. Complaining that you have less pages is missing the point.

I was about to post something similar but I'll just quote this.

Customers are getting the exact same amount of bread, as well as filling, it's just not been stretched to 12".

This topic is now closed to further replies.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!