It’s “all” in the sense that it’s everything the instance knows about, in contrast to “this server” which is only content from users that are registered on this specific instance. Same concept as the “all” and “local” feeds on lemmy. I agree that a better name might reduce the confusion but I can’t think of a good one.
Servers not having the same content in their “all” feeds is not a bug, it’s by design. The design philosophy for Mastodon (and I’d say the fediverse as a whole) is to let the users curate their own feeds instead of showing them everything or algorithmically guessing what they might be interested in. Servers will only receive posts from accounts that at least one of this server’s accounts is subscribed to. Having every post federate to every server even if nobody there is interested in those posts would be a waste of resources.
Yes, that makes discovery of new content significantly harder but that’s the tradeoff for being able to host your own small instance without the need for a super powerful server. I can run my instance that serves just a couple of users on a 10-year-old server that runs a dozen other things at the same time. We see the stuff we’re interested in and don’t have to spend disk space, processing power and network bandwidth on content none of us will ever read and neither do we have to spend those resources on sending our posts to other instances where nobody will read them.
タイッツー is definitely taittsuu. Twitter doesn’t seem to use a katakana spelling. Your proposal of “tsuittaa” would be ツイッター. Same katakana but different order. There would be no reason to read Japanese from right to left. Might be an intentional pun though.
Edit: it’s https://taittsuu.com/
They don’t owe you anything. Not sex, not a kiss, not a hug, not a second date, not even a smile. If the date goes well, you will get some or even all of those but if you try to force them, you will get nothing. Sure it can be disappointing if you put in a lot of effort and get nothing back but you will have to live with that. Sometimes people just aren’t compatible and sometimes a date just goes wrong because of a weird coincidence.
Be nice, even if the date doesn’t go as you wanted. Open communication goes a long way and chances are that the person you’re talking to is just as insecure as you are. Explain (not accuse) why you don’t think this situation will work out. If you’re lucky, you can turn the conversation around. If not, at least you’re ending the date in a civil way. That also (and especially) applies to talking on online dating platforms. Sometimes you can tell just from a conversation that things won’t go anywhere. Way too many people just drop the conversation and move on which can feel pretty rude. Be nice, explain what’s up, give them a friendly goodbye and then move on.
Those rules apply to both sides. You don’t owe them anything either, especially if they get rude. You should still try to be friendly in case there is a misunderstanding but try to get yourself out of an uncomfortable situation before it gets worse. Your safety is still priority number one.
Edit: some more
Don’t expect a relationship to last. Chances are it won’t. But this isn’t as pessimistic of a tip as you might expect. Even a single day of joy can be worth it if you manage your expectations. I’ve had a relationship crash and burn after seven years, I’ve had ones that lasted a couple of months and I’ve had someone ghost me after the second date. And still, all of them gave me amazing memories that I wouldn’t want to miss and they helped me grow as a person. Allow things to grow on their own and enjoy the process. Maybe you will marry that person. Maybe you’ll date them for a few months or years. Maybe you will never get past second base but stay platonic friends. Maybe you will spend the most amazing day of your life with them and then never see them again because you accidentally spilled something over their favorite t-shirt.
Sooo… have you decided yet, which one you want to be?
Learn a language. Ad breaks are long enough for one or two lessons in Duolingo and probably other apps as well.
The expectation that people in office jobs can be productive for 8 hours per day.
Filezilla itself is not the problem. Deploying to production by hand is. Everything you do manually is a potential for mistakes. Forget to upload a critical file, accidentally overwrite a configuration… better automate that stuff.
Can confirm that it doesn’t load on iOS but loads fine on desktop.
Same in Germany
Wrong community. This is for open ended questions and discussion, not for asking for help.
A better place
The most interesting thing is that he wasn’t the only one. A guy who called himself Victor Lustig did the same thing with the Eiffel Tower.
You have been banned from !pyongyang@lemmy.world
I just made it 62.
The 99 bottles of beer song is (was?) a popular programming exercise to teach beginners about loops. Singing it in real life would be pretty annoying because you would essentially repeat the same two sentences for a couple of minutes. Apparently, the PHP developers were planning to order one beer each, sing the song and get on everyone’s nerves. The C++ dev stopped this by buying all the remaining beer at once.
The choice of languages is probably OP’s own prejudice. These days I’d say PHP devs are on average older and more experienced than JS and Python devs, just because almost nobody learns PHP as their first language anymore.
The bakery down the road from where I grew up used to hold the Guinness world record for the largest version of a local specialty.
That’s the reason why I like C#, ASP.Net Core and EF Core so much. A simple CRUD app can be written in under 10 minutes and easily deployed in any form from a self-contained binary to a docker container to whatever eldritch horror lurks behind Azure or k8s. Personally, I run docker swarm mode for my stuff because it makes automated deployment super easy, kind of like a leaner k8s but if I wanted, I could just drop a binary on any windows, linux or macOS machine without needing to install any major dependency apart from my database.
Edit: of course, ASP.Net Core has its downsides too. Especially when it comes to auth stuff. I wish I could have something as simple as devise + cancancan in old versions of Rails.