None of those really “feel like” the things they’re replacing. I don’t really even think that should be the goal. They occupy the same space, though, and the infographic would look stupid if it showed all the options in some category, so they just picked a popular proprietary/centralized one, and a popular federated alternative in the same category. In this case discord is a popular chat app, and the most popular federa chat app afaict is matrix.
That’s some awful impressive goalpost shifting. Gold medal mental gymnastics winner.
And here you are, still unable to explain why prefix and postfix notation don’t have an operator precedence. I’m still waiting.
I already told you 3 times they obey the same rules
They literally don’t, and I defy you to show me a single source that tells you that prefix or postfix notation use PEDMAS. I’ll even take Quora answers.
Heck, I’ll even take a reputable source talking about prefix/postfix that doesnt bring up how order of operations isn’t required for those notations.
Nope. Doesn’t say that anywhere. Go ahead and screenshot the part which you think says that. I’ll wait
Right here:
Infix notation needs extra information to make the order of evaluation of the operators clear:
rules built into the language about operator precedence and associativity
Which you attempt to retort with
BTW this is completely wrong…
But then you go on to say something to the effect of “anyone who knows the rules can the extra information”. Which is both unsubstantiated given the long history of not having PEDMAS, but also kind of a nothingburger.
Doesn’t say that either. 🙄 Again, provide a screenshot of where you think it says that
It’s literally the whole thing. Did you notice how they never discuss the need for operator precedence, or use operator precedence?
Build for me a prefix or postfix equation that you think is changed by adding parentheses (eg overriding the natural order of operations), and then go ahead and find a prefix or postfix calculator and show me the results of removing those parentheses.
If you read the rules for those notations, you’ll see pretty clearly that operator precedence is purely positional, and has nothing to do with which operator it is.
Note that I always cite Maths textbooks
No, you’ve show a screenshot from a random PDF. What math textbook and what edition is it?
The fact you think that factorization has to do with order of operations is shocking.
Yes the multiplication is done first, but not because PEDMAS. The law is about converting between a sum of a common product and a product of sums. No matter how you write them, it will always be about those things, so the multiplication always happens first. It doesn’t depend on PEDMAS because without PEDMAS you’d simply write the equation differently and factorization would still work.
It’s crazy that you’re not able to distinguish between mathematical concepts and the notation we use to describe them.
But putting that aside, that’s not a proof of PEDMAS.
If PEDMAS is an actual law, then there will be a formal proof or theorem about it. There are proofs for 1+1, if PEDMAS is a law then there will be an actual proof specifically about it. Not just some law and then you claim it follows that PEDMAS is true, an actual proof or theorem, or an textbook snippet explain how it is an unprovable statement.
Left to right is a convention, yes, doing Multiplication and Division before Addition and Subtraction is a rule 🙄
A claim entirely unsupported by the textbook example you provided. Nowhere does it say that one is a convention but not the other, it only says that removing brackets changes the meaning in some situations, which is fully within the scope of a convention.
For the 3rd time it does have order of operations 🙄You just do them in some random order do you?
There you go again, just admitting you don’t know what postfix and prefix notations are.
If you’re ordering your operations based what the operator is, like PEDMAS, then what you’re doing isn’t prefix or postfix.
I’ll tell you what, here is a great free article from Colorado State university talking about prefix, postfix, and infix notations.
Note how it says the rules about operator precedence are for the notation which itself is a convention, as all notations are, and how prefix and postfix don’t need those rules
says person who doesn’t know the difference between conventions and rules, and thinks postfix notation doesn’t have rules 🙄
How embarrassing for you.
Here are some more materials:
But to top it all off, if this was truely a law of mathematics, then show me a proof, theorem, or even a mathematical conjecture, about order of operations.
Is now a paid feature?
Was playback over 2x (through the official app) ever supported for free?
In your screenshot of a textbook, they refer to it as a convention twice.
And you still haven’t explained prefix or postfix notation not having order of operations.
Get rekd idiot
I don’t really think that is true, those big wood TVs mostly aren’t especially stylish, and neither are recorded players.
Although style is obviously subjective so I suppose our miles vary
On CloudFlare, user224.com renews annually at less than $11
That’s where I got my domain (I was using them at the time, but it doesn’t matter), for that price, and that includes whois privacy.
I can’t answer many of the questions here, but I can help a little with two:
If you’re worried about noise, don’t get ironwolf drives. I just did and they’re noisy af. I brought some sound absorbing foam to put around the place where I keep my NAS, because they’re so much louder than I expected.
Don’t open up a port in your network.
Use something like tailscale to connect your devices to your home network, or rent an VPS to run a secure tunnel using pangolin (you’ll need to look into bandwidth limits).
Perceiving the effects isn’t the same as perceiving the object, unless you take an extraordinarily pedantic definition of “perceive”.
And considering an individual electron to be an object that you perceive is likewise not commonly an everyday occurrence, unless you take a likewise pedantic definition of “object”.
And even the word “perceive” was my choice of word, describing specifically that I believed that the OP meant to exclude things like subatomic particles. So even in the end you’re still trying to argue that I didn’t really mean what I meant, due to word choice, which is also a very pedantic thing to do
You can perceive high speed electrons in various ways, in your every day life?
Ok, that level of pedantry is my job
Because there is a huge demographic of nerds that are actually chuds and learned absolutely nothing from being bullied and/or being a beginner when they were younger.
I bet you can picture the demographic that they overlap with, but I’ma try not to explicitly make this political.
Sorry I misread when you said “library” for some reason I thought you meant “external library”
The problem that I’m trying to solve and I think OP is also trying to solve, is that they want the files to be on their NAS because it is high capacity, redundant, and backed up, but many users have access to the NAS, so they cannot rely on immich alone to provide access permissions, they need access permissions on the files themselves.
I solved this by having a separate share for every user, and then mounting that user’s share on their library (storage label).
It sounds like OP wants a single share, so having correct file ownership is important to restrict file access to the correct users who are viewing the filesystem outside of immich.
Not sure what you mean by your last paragraph, how do you assign a share to individual files (assume you mean directories) outside of immich’s need for storage?
Library access won’t allow upload, this will.
My knowledge here isn’t super deep, but it seems like you can do mapping per-share-per-ip, which means you can say “all file access coming from the immich host to this share will act as this user” which I think is fine if that share belongs to that user, and you don’t have anything else coming from that host to that share which you want to act as a different user. Which are very big caveats.
You conveniently skipped over the “and are able to perceive” part
I got excited and didn’t properly read your post before I wrote out a huge reply. I thought your problem was the per-user mapping to different locations on your NAS or to different shares, but its specifically file ownership.
whoops.
Leaving this here anyways, in case someone finds it helpful.
I kinda address file ownership at the end, but I don’t think its really what you were looking for because it depends on every user having their own share.
In docker, you’ll need to set up an external NFS volume for every user. I use portainer to manage my docker stacks, and its pretty easy to set up NFS volumes. I’m not sure how to do it with raw docker, but I dont think its complicated.
in your docker compose files, include something like this
services:
immich-server:
# ...
volumes:
- ${UPLOAD_LOCATION}:/data
- /etc/localtime:/etc/localtime:ro
- type: volume
source: user1-share
target: /data/library/user1-intended-storage-label
volume:
subpath: path/to/photos/in/user1/share
- type: volume
source: user2-share
target: /data/library/user2-intended-storage-label
volume:
subpath: path/to/photos/in/user2/share
# and so on for every user
# ...
volumes:
model-cache:
user1-share:
external: true
user2-share:
external: true
# and so on for every user
There are 3 things about this setup:
${UPLOAD_LOCATION}. For me this is fine, I dont want to pollute my NAS with a bunch of transient data, but if you want that info then for every user, in addition to the target: /data/library/user1 target you’ll also need a target: /data/thumbs/user1, target: /data/encoded-video/user1, etc.target, when you mount this volume it will mask that data. This is why it is important that no users exist with that storage label prior to this change, else that data will get hidden.You may also want to add similar volumes for external libraries (I gave every user an external “archive” library for their old photos) like this:
- type: volume
source: user1-share
target: /unique/path/to/this/users/archive
volume:
subpath: path/to/photo/archive/on/share
and then you’ll need to go and add that target as an external library in the admin setup.
and once immich allows sharing external libraries (or turning external libraries into sharable albums) I’ll also include a volume for a shared archive.
redeploy, change your user storage labels to match the targets, and run the migration job (or create the users with matching storage labels).
I honestly don’t think its important, as long as your user has full access to the files, its fine. But if you insist then you have a separate share for every user and set up the NFS server for that share to squash all to that share’s user. Its a little less secure, but you’ll only be allowing requests from that single IP, and there will only be a request from a single user from that server anyways.
Synology unfortunately doesn’t support this, they only allow squashing to admin or guest (or disable squashing).
Hmmmm that’s a good point.
I still wouldn’t count that as every day life because you’re not physically interacting with the satellite or submarine internet cables, even if you’re interacting with the effects of their existence.
But now I have to justify why my stance of “being physically near but still unable to see or touch directly” (as an internal mechanism of something) is any more “everyday life”. It feels like an internal mechanism counts as just as every-day as the thing its a part of, but is it really?
I don’t have a solid justification. It just feels different to me.
I think that “with some mass” wasn’t meant literally but figuratively, specifically to exclude things like shooting subatomic particles.
I think OP means the kinda of things humans interact with and are able to perceive in their every day life.
I feel like that’s even less like “everyday life” than OPs example of bullets lol
I had to read it a few times, I initially made the same mistake as you. It’s all there but I’m not used to carefully reading all the text on a silly post lol
THANK YOU. this is what I’ve been trying to tell you the entire fucking time. PEMDAS is not a law, its a convention.
but just in case you decide to go back on that, and since you seem to be obsessed with the idea that all notations adhere to PEMDAS - let me blow your mind:
here is the distributive law, written in the 3 notations we’ve been talking about:
prefix:
*a+bc = +*ab*acinfix:
a(b+c) = ab+acpostfix:
abc+* = ab*ac*+(not using juxtaposition multiplication for prefix/postfix for clarity)
so where does PEDMAS get involved in prefix or postfix notations?
regarding your textbook being the first google result… are you referring to the textbook from 1913? for someone talking about the importance of textbooks, thats a really strange choice. I can’t find another with the same name and author of either Coll or Rich.
and hilariously, if you look at that text book, on page 90 it says the following: