Pika

Aside from the opt out will potentially encourage bullying, I don’t really get their argument there tbh. By the logic they are using, federation as a whole would be a violation of their terms. Usage of the ActivityPub in it’s entirety would do the same thing they are complaining about. If you don’t want your data being cycled to god knows who, I would not recommend any ActivityPub platform and if you decide to anyway, disabling federation, and using authenticated endpoints. They are likely better off in a closed environment but even those generally are public access.

It reminds me of the people who used to have content licenses appended to their comments, I’m not convinced that having it was even enforceable due to federation.

I’m not sure how I feel about this. This is giving the false mentality that you aren’t being tracked/your data isn’t there. Like obviously they process data, and can link that data to a person, and its all public anyway. To say that they aren’t tracking you isn’t genuine. I think it would be better off saying “We don’t analyze your data” because they definitely track your data, that’s how the service works. if they didn’t then the service wouldn’t be able to properly function, but I digress.

yea thats fully understandable. also no idea why this post just showed in my feed, didn’t mean to revive a 4 month old comment 😅

my first go to for fixing every issue I have with a windows component

1. sfc /scannow
2. dism /online /cleanup-image /restorehealth

the amount of time that last command has fixed a core issue with the system is shocking but god that command takes forever

I’m more surprised that your school doesn’t go by the “Wipe and reimage” policy. Most every school now uses some form of cloud service. No reason to spend time troubleshooting when you can just do a stock image and have the student sign in again

In the admins defense. “Closed by peer” can indicate everything from a safe closure to an unsafe closure to a server connection terminating which causes the peer to terminate.

Like that’s a fair point of confusion.

What bugs me is when the error says something stupid specific and obvious such as JavaScript heap out of memory or dd: error writing *pathname*: No space left on device

that’s why any manual worth their salt has a “quick start” section at the beginning (I say this knowing most man pages fail at this or put it at the end which is super unhelpful)

Just give me common uses and flags, you can have your more indepth stuff at the end

I hard passed on vintage story. I was looking into the game, took one look at the community and the toxicity on their support forums and went “yep thats a hard pass”.

IMO the company should really do some cleansing on their starting topics. It doesn’t look good for a game when there’s active toxicity in the community forums arguing over if the game needs to be changed and telling people to get gud and that they didn’t have such things when starting out when they make super basic suggestions like starter equipment, or an actual tutorial.

They may have fixed that since then since its been a year or two, but that was a hard turnoff for me. A lesser known game needs community support to function and survive. Even minecraft mods have a vast amount of wikis and community support. An actively hostile community on the official community forums is not a good starting POV.

the main issue will be if they do a major API update right before they do it. Remember the great “flattening”? We lost many great mods when they did that because of the amount of changes they did to base code while simultaneously changing every ID in the game, while forge was also actively undergoing a major API change in how it worked. So as a result many mods stopped being developed at 1.12.

If they did a massive API rewrite right before fully ending support for java, the community will either have to accept another divide or completly forgo the new update and stay locked on the previous.

that is correct, you can use Geyser to allow bedrock to join java players. For console or any bedrock client that lacks the direct connection with servers you need to also do some DNS shenanigans on the client where you use a jumper server to jump to the server you actually wanna join though.

I also recommend something like floodgate for authentication so you don’t need to have the server in offline mode or have the player need both a java and a bedrock account

edit: I forgot to mention, keep in mind that this is still using JAVA edition as a backend. So when there is feature disparity between bedrock and Java, the java mechanic is what takes precedence. The biggest whiplash for bedrock vs java is usually the fact that java edition minecraft has the stamina system for attacking, so you can’t just button mash to attack or you waste durability and have lower attack damage.

Is the main issue that you are using test and extra indentation with fish? Like, does this help?

yes that is better, I do like the clearer differentiation on what is a command vs part of the flow control. I do find that using [] or [[]] is cleaner looking than using the standard test command, but the main point of it was showing the flow; functions having a beginning { and an ending }, conditionals clearly using if to mark the beginning, ; then to mark when the conditional portion of the flow ends and the processing portion begins, and the fi to indicate when the processing portion ended. Flow control statements like that. Could I be able to decipher it manually like I have to with python? yes, but it’s just something that as a personal preference I would prefer not to do if avoidable.

its easier to let me know that the previous line wasn’t done, and that I should be expecting the conditional to continue instead of start to work on the next line. The most noticeable would be with really long conditionals, I think its nice since bash and fish don’t use {} outside of functions to indicate open and close like other non-tab oriented languages. Moving longer lines to dedicated functions works well but doesn’t help when the entire conditional is related so it would just be in the main function block instead.

It’s a very subjective thing, definitely more of a minor thing since I already have to deal with it with tab oriented languages on the rare occasion I deal with them. My main issues with it were definitely was the lack of usage leading to fewer examples and documentation on how it worked, and then the piping issue was just the final nail in the coffin that made me drop it.

Maybe you are thinking about fish more as a programming language? Whereas I’m thinking about it more like a series of commands (I guess more like a “purer” scripting language of sorts)?

Yes, that is likely the differentiation. I understand that bash is more command based but, I do a lot of stuff in java, node and Rust, and those all have clear differentiation of start and end (although rust’s can be a pain at times)

I find that fish

function foo
    if test "$foo" = 1
      echo "found"
    else
      echo "not found"
    end
end

vs bash

function foo () {
  if [[ "$foo" == 1 ]]; then
    echo "found"
  else
    echo "not found"
  fi
}

is a downgrade in flow comprehensibility. Like I can see why it could be easier to read, but I prefer not having to analyze where statements, conditionals and functions begin and end. It’s very similar to how python works, and I disliked that in python. At the end of the day flow layout is subjective so you may or may not agree, but thats my mentality on it.

As for the piping example, I don’t have that snippet available anymore. I eventually remade the code from scratch and when I did I got rid of zenity as a dependancy which removed the need of having the pipe. It was a wget pipe into sed into zenity in order to use a progress bar for the download, and fish did not like that pipe at all, I’m not sure if it was because it was multiple pipes or if something else underlying was happening, but I could take that same pipe sequence and throw it into bash and it would function no issue, but with fish zenity wouldn’t give progress updates on it, so it was modifying the pipe somewhere.

Bias wise I wouldn’t say I was bias towards bash, I tried fish after recommendation from a friend because I hadn’t heard of it, and I had a bad experience. I moved to ZSH instead of going back to bash after all. I just found it easier to use over fish, and it was easier to research into issues when problems arose as it has a larger user-base and remained POSIX compatible (mostly). To me it made no sense to re-invent the wheel via fish. I’m sure fish had it’s advantages. I just didn’t see any during the week I was trialing it.

You mean its if and switch statements? For and while loops? Just like bash and zsh has?

No i mean the flow in general. It’s ugly and not transparent when compared to bash or any other language

the lack of indication where it starts to where it ends

Yes and no, I mean how it chooses to start and end, there is no punctuation, it seems to emulate a tab oriented language without being a tab oriented language.

Piping something “via the function layout”? I’m not even sure what that means. I’d love to know more if you would.

Two separate complaints, I dislike how they manage functions (but yes bash does similar on this case). Piping and redirecting are badly implemented and what would be an accepted pipe in ZSH or Bash will fail in fish. I made a script that had to pipe a file via wget and it wouldn’t function unless I used a pager which wasn’t needed in Bash or Zsh and wasn’t documented as a requirement anywhere on their piping or redirection documentation. Took me almost an hour of troubleshooting why the command was failing and how to fix it due to it.

I mean… It took me like an hour to read through the documentation, and all the syntax is so small you can memorize the entire language.

Maybe this has changed since I last tried about a year or two ago, but last time I tried to read the documentation it sucked hardcore and lacked examples of more advanced parts of the shell.

It kind of sounds like you were fighting fish rather than it fighting you, every step of the way. That sounds absolutely crazy compared to my experience.

I would rather take the path of least resistance for a program, with fish it had way too much resistance trying to use it, so I went to the path that had a lesser resistance, which was ZSH, and then just proceeded to add fish’s core capabilities to zsh. This let me use a scripting language that has a lot of documentation and examples to assist in learning, while having the benefits of the shell. Plus it lets me actually share the scripts with friends because it’s already hard to find someone on linux, and its even moreso difficult to find someone who uses fish shell.

I dislike heavily how flow control works on it, and the lack of indication where it starts to where it ends, the function layout, not to mention attempting to pipe anything via it. This combined with the fact that it’s a lesser used shell and as such has less of a presence online to research made it not worth the time and effort to actually use it. I swapped to ZSH which at least maintains a large POSIX compliance which makes it easier to share the scripts as well and also supports adding many of fish’s features.

It may be nicer to read but, actually getting established, learning it, using it and then maintaining compatibility with other programs and scripts when using it, just made it not worth it. I have better things to do with my free time then to try and fight a shell every step of the way to make it look cleaner.

Yeah, that was what I was saying it wasn’t super clear. I was saying, just keep your scripts in Bash because it has better compatibility 👀

this is basically what I did until I dropped fish for zsh because of annoyances with how it functioned.

Scripting in fish is obnoxious though if you learned bash first, heavily recommend staying far away 😂

Hard recommend staying in bash or at least zsh, at least you maintain compatibility with others if you ever decided to share your scripts.

So did I up until windows 10, which makes sense because my laptop that had run windows 8.1 had been upgraded from Windows 7 and had the issue every time it seems to have a version release. My windows 10 system was a factory install since I switched to a PC instead of a laptop at that time, and as such ran UEFI out of the box, I haven’t had any issue with windows nuking a boot partition since.

I’m assuming it’s because bios boot still uses an MBR which means the actual boot record is at the beginning of the disk, which windows also tries to use for recovery and its boot. With GPT setups like how UEFI requires, there’s a dedicated partition that is used instead for storing EFI files, so it allows for a much clearer co-existence.

Basically if you are running a UEFI system, there’s no excuse for Windows to actually nuke grub anymore, because the entire reason it was nuking it in the first place was it was overwriting the MBR at the beginning of the disk so the system no longer knew where grub was. With UEFI the system boot would be the UEFI loader -> windows loader or grub (or like how my system is brokenly setup UEFI -> grub -> windows because I like the traditional style of selecting windows from grub)

that’s the fun part! you don’t 🦊

Yeah, I was gonna say I dual boot and I can’t recall the last time that Windows nuked my UEFI bootloader.

But back when Windows still did BIOS boot, it was like every major release without fail.

edit: Rewreading your post it sounds like you meant updating the BIOS as a whole and not BIOS boot, so that’s my bad. Yeah, I definitely haven’t seen your circumstance, I had that happen consistently before Microsoft embraced the UEFI style booting

I haven’t had a kernel update on Debian that triggered the “you should restart” message in quite some time. I was under the understanding that most newer systems now use splicing at the kernel level to not require periodic reboots.