#vm code

[redhoodisms]

GUYS TELL ME WHY I AM HAVING A MAJOR BIG BRAIN MOMENT!!!

someone tell me to please write this new series of the batboys based on sabrina carpenter songs LIKE TELL ME THIS ISN’T A GOOD IDEA ASKFNBGSK. like…. please please please JUST RADIATES dick grayson energy (like bruh, the whole sub fic??? him begging ASKGK) TASTE IS LITERALLY JUST JASON TODD CODED I SWEAR, i need an edit with this man and this song. but like, kinda halloween based fic about him and his lust for love with y/n being caught in a violent, gorey crossfire of love I THINK YES. OR JUNO, DEFINATELY THAT TOO tim drake gives off that he listens to espresso or dumb and poetic. i haven’t decided yet so HELP guys…damian most certainly knows don’t smile like the back of his hand because that one SPEAKS TO HIM.

aight…so everyone done for this??? all in favor??? this could be my batboys comeback someone pls tell me that this is a good idea i beg!

[beedreamscape]

While I love the idea that Keyleth been fucking a random raven (in raven form ok!?) bc that's just too funny

I also like the idea that the Matron only let's Vax have his release if he's in Raven form, for the integrity of the brand and all, and that it took him a while until Kiki got the drill.

For a while he had to do some elaborate mating dances to seduce her.

[today-i-am-thinking-about]

rest messaging

[greasersinpoodleskirts4cumshots]

Look for Brad geiger brain data, available on the planet Earth

Please run in a shell - know what he knows, virtual machines

[swampdrive]

Wishing my father a very looney tunes esque car and/or hammer situation today

[arataneo-a]

i completely forgot that the main point of my final year project was to analyze malware and to do that i have to. run malware

[thedbahub]

Boosting Performance in Azure: A Deep Dive into the Azure Boost Feature

Let’s take a closer look at a groundbreaking addition to the cloud computing landscape, the Azure Boost feature, and unravel its potential to redefine Virtual Machine (VM) performance in terms of network and storage speed. As we navigate through the ever-evolving cloud infrastructure, Microsoft Azure has thrown a new card on the table – Azure Boost. This feature promises to amp up the game for…

[bubbles-floating]

Now do I try to fix my old installation and get the python virtualenv running on this vm or do I just clean install a new one ahhh

[holy-muffins]

I don't have any reach at all but today I think qualifies as a red line day for folks. The administration is attempting to essentially turn off medicaid and other federally funded aid programs in the US via an executive order. Please call your representatives ESPECIALLY if you do NOT depend on things like food assistance, medicaid, etc.

This administration gets off on cruelty, so stating that you are not affected by this will limit their joy at the calls rolling in AND remind them people are watching.

You can look up phone numbers here

Call and let them know that they:

1. Must treat this as a red line over reach of executive branch and they must work to see these funds are paid out properly

2. Be forceful when saying you do not benefit from the program but that your friends and neighbors do

3. Call both senators and your rep. When they ask for a zip code give it, and say that you are calling all of your reps today.

4. Again! Remind them that this spending has been federally mandated by Congress

If you are nervous you can leave a voicemail but I recommend leaving a VM and attempting to get through to someone.

Please see if you can get some of the Big Folks here on tumblr to see this.

Please do not be too mean to me if I could have worded any of this better.

Please add on with good information.

[anheliotrope]

Rambling About C# Being Alright

I think C# is an alright language. This is one of the highest distinctions I can give to a language.

Warning: This post is verbose and rambly and probably only good at telling you why someone might like C# and not much else.

~~~

There's something I hate about every other language. Worst, there's things I hate about other languages that I know will never get better. Even worse, some of those things ALSO feel like unforced errors.

With C# there's a few things I dislike or that are missing. C#'s feature set does not obviously excel at anything, but it avoids making any huge misstep in things I care about. Nothing in C# makes me feel like the language designer has personally harmed me.

C# is a very tolerable language.

C# is multi-paradigm.

C# is the Full Middle Malcomist language.

C# will try to not hurt you.

A good way to describe C# is "what if Java sucked less". This, of course, already sounds unappealing to many, but that's alright. I'm not trying to gas it up too much here.

C# has sins, but let's try to put them into some context here and perhaps the reason why I'm posting will become more obvious:

C# didn't try to avoid generics and then implement them in a way that is very limiting (cough Go).

C# doesn't hamstring your ability to have statement lambdas because the language designer dislikes them and also because the language designer decided to have semantic whitespace making statement lambdas harder to deal with (cough Python).

C# doesn't require you to explicitly wrap value types into reference types so you can put value types into collections (cough Java).

C# doesn't ruin your ability to interact with memory efficiently because it forbids you from creating custom value types, ergo everything goes to the heap (cough cough Java, Minecraft).

C# doesn't have insane implicit type coercions that have become the subject of language design comedy (cough JavaScript).

C# doesn't keep privacy accessors as a suggestion and has the developers pinkie swear about it instead of actually enforcing it (cough cough Python).

Plainly put, a lot of the time I find C# to be alright by process of elimination. I'm not trying to shit on your favorite language. Everyone has different things they find tolerable. I have the Buddha nature so I wish for all things to find their tolerable language.

I do also think that C# is notable for being a mainstream language (aka not Haskell) that has a smaller amount of egregious mistakes, quirks and Faustian bargains.

The Typerrrrr

C# is statically typed, but the typing is largely effortless to navigate unlike something like Rust, and the GC gives a greater degree of safety than something like C++.

Of course, the typing being easy to work it also makes it less safe than Rust. But this is an appropriate trade-off for certain kinds of applications, especially considering that C# is memory safe by virtue of running on a VM. Don't come at me, I'm a Rust respecter!!

You know how some people talk about Python being amazing for prototyping? That's how I feel about C#. No matter how much time I would dedicate to Python, C# would still be a more productive language for me. The type system would genuinely make me faster for the vast majority of cases. Of course Python has gradual typing now, so any comparison gets more difficult when you consider that. But what I'm trying to say is that I never understood the idea that doing away entirely with static typing is good for fast iteration.

Also yes, C# can be used as a repl. Leave me alone with your repls. Also, while the debugger is active you can also evaluate arbitrary code within the current scope.

I think that going full dynamic typing is a mistake in almost every situation. The fact that C# doesn't do that already puts it above other languages for me. This stance on typing is controversial, but it's my opinion that is really shouldn't be. And the wind has constantly been blowing towards adding gradual typing to dynamic languages.

The modest typing capabilities C# coupled with OOP and inheritance lets you create pretty awful OOP slop. But that's whatever. At work we use inheritance in very few places where it results in neat code reuse, and then it's just mostly interfaces getting implemented.

C#'s typing and generic system is powerful enough to offer you a plethora of super-ergonomic collection transformation methods via the LINQ library. There's a lot of functional-style programming you can do with that. You know, map, filter, reduce, that stuff?

Even if you make a completely new collection type, if it implements IEnumerable<T> it will benefit from LINQ automatically. Every language these days has something like this, but it's so ridiculously easy to use in C#. Coupled with how C# lets you (1) easily define immutable data types, (2) explicitly control access to struct or class members, (3) do pattern matching, you can end up with code that flows really well.

A Friendly Kitchen Sink

Some people have described C#'s feature set as bloated. It is getting some syntactic diversity which makes it a bit harder to read someone else's code. But it doesn't make C# harder to learn, since it takes roughly the same amount of effort to get to a point where you can be effective in it.

Most of the more specific features can be effortlessly ignored. The ones that can't be effortlessly ignored tend to bring something genuinely useful to the language -- such as tuples and destructuring. Tuples have their own syntax, the syntax is pretty intuitive, but the first time you run into it, you will have to do a bit of learning.

C# has an immense amount of small features meant to make the language more ergonomic. They're too numerous to mention and they just keep getting added.

I'd like to draw attention to some features not because they're the most important but rather because it feels like they communicate the "personality" of C#. Not sure what level of detail was appropriate, so feel free to skim.

Stricter Null Handling. If you think not having to explicitly deal with null is the billion dollar mistake, then C# tries to fix a bit of the problem by allowing you to enable a strict context where you have to explicitly tell it that something can be null, otherwise it will assume that the possibility of a reference type being null is an error. It's a bit more complicated than that, but it definitely helps with safety around nullability.

Default Interface Implementation. A problem in C# which drives usage of inheritance is that with just interfaces there is no way to reuse code outside of passing function pointers. A lot of people don't get this and think that inheritance is just used because other people are stupid or something. If you have a couple of methods that would be implemented exactly the same for classes 1 through 99, but somewhat differently for classes 100 through 110, then without inheritance you're fucked. A much better way would be Rust's trait system, but for that to work you need really powerful generics, so it's too different of a path for C# to trod it. Instead what C# did was make it so that you can write an implementation for methods declared in an interface, as long as that implementation only uses members defined in the interface (this makes sense, why would it have access to anything else?). So now you can have a default implementation for the 1 through 99 case and save some of your sanity. Of course, it's not a panacea, if the implementation of the method requires access to the internal state of the 1 through 99 case, default interface implementation won't save you. But it can still make it easier via some techniques I won't get into. The important part is that default interface implementation allows code reuse and reduces reasons to use inheritance.

Performance Optimization. C# has a plethora of features regarding that. Most of which will never be encountered by the average programmer. Examples: (1) stackalloc - forcibly allocate reference types to the stack if you know they won't outlive the current scope. (2) Specialized APIs for avoiding memory allocations in happy paths. (3) Lazy initialization APIs. (4) APIs for dealing with memory more directly that allow high performance when interoping with C/C++ while still keeping a degree of safety.

Fine Control Over Async Runtime. C# lets you write your own... async builder and scheduler? It's a bit esoteric and hard to describe. But basically all the functionality of async/await that does magic under the hood? You can override that magic to do some very specific things that you'll rarely need. Unity3D takes advantage of this in order to allow async/await to work on WASM even though it is a single-threaded environment. It implements a cooperative scheduler so the program doesn't immediately freeze the moment you do await in a single-threaded environment. Most people don't know this capability exists and it doesn't affect them.

Tremendous Amount Of Synchronization Primitives and API. This ones does actually make multithreaded code harder to deal with, but basically C# erred a lot in favor of having many different ways to do multithreading because they wanted to suit different usecases. Most people just deal with idiomatic async/await code, but a very small minority of C# coders deal with locks, atomics, semaphores, mutex, monitors, interlocked, spin waiting etc. They knew they couldn't make this shit safe, so they tried to at least let you have ready-made options for your specific use case, even if it causes some balkanization.

Shortly Begging For Tagged Unions

What I miss from C# is more powerful generic bounds/constraints and tagged unions (or sum types or discriminated unions or type unions or any of the other 5 names this concept has).

The generic constraints you can use in C# are anemic and combined with the lack of tagged unions this is rather painful at times.

I remember seeing Microsoft devs saying they don't see enough of a usecase for tagged unions. I've at times wanted to strangle certain people. These two facts are related to one another.

My stance is that if you think your language doesn't need or benefit from tagged unions, either your language is very weird, or, more likely you're out of your goddamn mind. You are making me do really stupid things every time I need to represent a structure that can EITHER have a value of type A or a value of type B.

But I think C# will eventually get tagged unions. There's a proposal for it here. I would be overjoyed if it got implemented. It seems like it's been getting traction.

Also there was an entire section on unchecked exceptions that I removed because it wasn't interesting enough. Yes, C# could probably have checked exceptions and it didn't and it's a mistake. But ultimately it doesn't seem to have caused any make-or-break in a comparison with Java, which has them. They'd all be better off with returning an Error<T>. Short story is that the consequences of unchecked exceptions have been highly tolerable in practice.

Ecosystem State & FOSSness

C# is better than ever and the tooling ecosystem is better than ever. This is true of almost every language, but I think C# receives a rather high amount of improvements per version. Additionally the FOSS story is at its peak.

Roslyn, the bedrock of the toolchain, the compiler and analysis provider, is under MIT license. The fact that it does analysis as well is important, because this means you can use the wealth of Roslyn analyzers to do linting.

If your FOSS tooling lets you compile but you don't get any checking as you type, then your development experience is wildly substandard.

A lot of stupid crap with cross-platform compilation that used to be confusing or difficult is now rather easy to deal with. It's basically as easy as (1) use NET Core, (2) tell dotnet to build for Linux. These steps take no extra effort and the first step is the default way to write C# these days.

Dotnet is part of the SDK and contains functionality to create NET Core projects and to use other tools to build said projects. Dotnet is published under MIT, because the whole SDK and runtime are published under MIT.

Yes, the debugger situation is still bad -- there's no FOSS option for it, but this is more because nobody cares enough to go and solve it. Jetbrains proved anyone can do it if they have enough development time, since they wrote a debugger from scratch for their proprietary C# IDE Rider.

Where C# falls flat on its face is the "userspace" ecosystem. Plainly put, because C# is a Microsoft product, people with FOSS inclinations have steered clear of it to such a degree that the packages you have available are not even 10% of what packages a Python user has available, for example. People with FOSS inclinations are generally the people who write packages for your language!!

I guess if you really really hate leftpad, you might think this is a small bonus though.

Where-in I talk about Cross-Platform

The biggest thing the ecosystem has been lacking for me is a package, preferably FOSS, for developing cross-platform applications. Even if it's just cross-platform desktop applications.

Like yes, you can build C# to many platforms, no sweat. The same way you can build Rust to many platforms, some sweat. But if you can't show a good GUI on Linux, then it's not practically-speaking cross-platform for that purpose.

Microsoft has repeatedly done GUI stuff that, predictably, only works on Windows. And yes, Linux desktop is like 4%, but that 4% contains >50% of the people who create packages for your language's ecosystem, almost the exact point I made earlier. If a developer runs Linux and they can't have their app run on Linux, they are not going to touch your language with a ten foot pole for that purpose. I think this largely explains why C#'s ecosystem feels stunted.

The thing is, I'm not actually sure how bad or good the situation is, since most people just don't even try using C# for this usecase. There's a general... ecosystem malaise where few care to use the language for this, chiefly because of the tone that Microsoft set a decade ago. It's sad.

HOWEVER.

Avalonia, A New Hope?

Today we have Avalonia. Avalonia is an open-source framework that lets you build cross-platform applications in C#. It's MIT licensed. It will work on Windows, macOS, Linux, iOS, Android and also somehow in the browser. It seems to this by actually drawing pixels via SkiaSharp (or optionally Direct2D on Windows).

They make money by offering migration services from WPF app to Avalonia. Plus general support.

I can't say how good Avalonia is yet. I've researched a bit and it's not obviously bad, which is distinct from being good. But if it's actually good, this would be a holy grail for the ecosystem:

You could use a statically typed language that is productive for this type of software development to create cross-platform applications that have higher performance than the Electron slop. That's valuable!

This possibility warrants a much higher level of enthusiasm than I've seen, especially within the ecosystem itself. This is an ecosystem that was, for a while, entirely landlocked, only able to make Windows desktop applications.

I cannot overstate how important it is for a language's ecosystem to have a package like this and have it be good. Rust is still missing a good option. Gnome is unpleasant to use and buggy. Falling back to using Electron while writing Rust just seems like a bad joke. A lot of the Rust crates that are neither Electron nor Gnome tend to be really really undercooked.

And now I've actually talked myself into checking out Avalonia... I mean after writing all of that I feel like a charlatan for not having investigated it already.

[crtakespropogandist]

CR 3 finale dump pt. 3 - Putting my finger on it

I enjoyed the campaign while I was watching it for the most part, because the cast's antics and chemistry always make me smile. But I invariably engaged the most during the tie-ins and cameos bringing back the PCs and NPCs from previous campaigns, and I couldn't summon the same investment for this one. I was ruminating on why that was, and here is what I came up with:

Campaign 3 didn't "work" like the other two because the characters, the plot, and the setting were not integrated. Matt had an epic storyline in mind that could dramatically change Exandria. He also had two lovingly designed settings, Marquet and Ruidus, the fruits of great collaborative labor that he wanted to show off. Finally, he wanted to let his friends have total control in conceptualizing their characters. The result is that the players and Matt seemed really afraid of stepping on each other's (and the other creatives') toes, and the narrative hurt for it.

Character hooks led away from the plot and setting. Setting hooks led away from the plot and characters. Plot hooks led away from the setting and characters. The cast ultimately had to follow the plot, leaving PCs uninvested and locations underutilized along with all their resident NPCs. Freaking Vox Machina had stronger relationships with Marquesian NPCs.

Yet Matt was still discouraged from taking time away from exploring new places and meeting new people for a deeper dive on Delilah Briarwood. Why didn't Ludinus give Tal'Dorei a heads up when the Briarwoods became fugitives? Did he help them in exchange for residuum? Did they steal his obsessive research on the Matron's ritual for Vecna to use? Maybe Jiana Hexum knows something abou...oop BH left Jrusar and forgot all about her. Matt was also discouraged from leaving shiny new Marquet any earlier for Aeor 2: Electric Boogaloo, which left FCG high and dry. The self-imposed balance between the three key story elements was impossible to maintain in a satisfactory way.

VM and M9 are native to their campaigns' respective continents (except my boy Tary ofc), and the plot evolved organically from personal stakes intrinsic to those settings. Moments like "I am no friend to the empire" and "It's Lady Vex'ahlia" are off the table when the party is Oops! All Transients. The worst irony is that Matt undermined the players' autonomy by unilaterally deciding that Caleb and Beau utterly fumbled the task Liam and Marisha set them to in their C2 epilogues. Liam's frustration at the Key scene was palpable. My fellow viewers who only hopped aboard on Campaign 3 can get weirdly defensive against C2's "encroachment" and C2 enjoyers (also fellows of mine) wishing it would "encroach" more. Ludinus was introduced in C2. The ruins of Aeor and Molaesmyr are in Wildemount. Dunamancy is centralized in Wildemount. The Nein spent time in Aeor, in Uthodurn, in the Dynasty. The Nein have gods. What experiments did Ludinus conduct in Vergessen? What are the specifics about what Ludinus did in Molaesmyr, what he's done throughout his life of scheming? It's pretty safe to guess that the Nein would have found out given another chance. Could you imagine how Campaign 2 might have panned out if Beau and Caleb reeeaaally grilled Demid Sunlash and followed up on where he went? (Also Ruidusborn!Essek would have made so much sense I'm vibrating) (Also also d'ya think Eadwulf was always supposed to be a real Matron follower, or could he have been set up as a Paragon's Call/Vanguard type reporting to Ludinus?)

Even as someone introduced to the stream via BH, I can't help but agree with Beau's "Why not us?" comments. Why not give the Wildemount party the Wildemount BBEG? Why not give Bell's Hells the kind of story that encourages them to be little NPC-coded freaks pushing each other's big red buttons just to see what happens? Why not give Marquet a party that calls it home?

The answer is because we got this instead, and I'm kinda sad about it. If BH gets animated, that show is a lost cause if some fundamental changes aren't made.

[shorthaltsjester]

okay but i am very confused about the energy regarding the weavemind as. bells hells specific enemies? like sure they’re on ruidus and have been introduced in campaign 3 but none of bells hells have expressed a specific interest in taking them down, the weave mind has committed no specific crimes against bells hells that would equate it to being Justice™ for bh to fight them. even if you want to make the tenuous connection that like imogen and fearne are ruidusborn: both of them have focused much more on the consequences and revelations about their families that have come about from their ruidusborn existence than the authoritarian leaders of ruidus itself. so, uh, it is profoundly more interesting to have the party go after the person in charge of the army cult that contextualizes both of their existences and the trauma of the entirety of their party than a obscure group of villains that bh has no actual tangible relation to. like this was literally laid out in the conversation. bh get the cage and ludinus because that’s Their Fight that they’ve been fighting since imogen started dreaming and since orym’s family got killed. vox machina is taking the bridge because of the vax of it all. and mighty nein got the third less prevalent thing, because they’re experienced with psychic threats and manipulation (and also because of course the mighty nein are the ones dealing with the assignment less likely to be seen or heard about).

like the in-character reactions to the breakup of activities were only really considered anything close to negative by braius and dorian who while certainly now members of bells hells aren’t the ones upon which people are claiming to build their ��this story is an injustice to the bells hells” sure it is. like ignoring the fact that being unable to get closure on every single issue and potential villain is a long-standing tradition in cr campaigns, i thought the thing everyone loved so much about bells hells is that they’re the npc party? and for better or worse c3 has been about being fast paced and it would be extraordinarily out of character for matt to say “oh these two high stakes and powerful groups have decided to fulfil their plans one at a time so that bells hells can sufficiently take them out.” like the only way that bells hells — the lowest level party — getting to take out One Of The Most Powerful Exandrian Mages is an injustice is if you’ve ignored the entire campaign and its context. like seeing the complaint that “it’s not bells hells story” yes, that has been made clear time and time again in the past 100 episodes. it’s completely fair to not like this, it’s extremely odd to see this as some sort of surprise wrecking ball that has come about in the decision to have more than one party of eight fuck ups trying to stop the unavoidably obvious world ending threat that exandria currently faces and not as something that has been made repeatedly clear by the themes and position of bells hells. like, throughout, unlike vm or mn, they have been handed their missions rather than choosing them (even if between 2 or 3 choices as was often the case with mn), they have explicitly discussed being the npcs or little guys, they have consistently gone to the bigger guys for help with things that previous parties either managed themselves or suffered without or had allies to help them (versus the like. Leaders that bh look to), even the dynamics of the parties express that bells hells are people stuck saving the world due to a bunch of personal moral codes rather than a specific decision to save the world because they’re the only ones who can, they’re expendable. that has made this campaign different throughout, it has made the characters less explored because they don’t have the time or means or desire to do so. and again it’s a matter of taste whether that’s something you enjoy, but it shouldn’t be a matter of “why would they do this” this far into the Bells Hells Aren’t Special They’re Just There campaign (which isn’t to say the characters aren’t special or whatever like they’re a bunch of weirdos but as a party they’re just a party)

[rabbiteclair]

love to enable virtualization so I can install an Ubuntu VM so I can run Docker so I can run containerized tests so I can debug a single line of code

[cyberstudious]

A Beginner's Guide to Learning Cybersecurity

I created this post for the Studyblr Masterpost Jam, check out the tag for more cool masterposts from folks in the studyblr community!

(Side note: this post is aimed towards the technical side of security, rather than the governance/management side, because the tech stuff is what I'm familiar with.)

Where do I start?

Cybersecurity is a specialization of general tech & therefore builds on some concepts that you'll need to know before you can dive deep into security. It's good to have a background in and understand:

how computers & operating systems work

how to use Linux

computer networking & basic protocols

If you're serious about learning cybersecurity, it can be helpful to look at certifications. Even if you don't want to get certified or take the exam (they can get expensive), they provide you with a list of topics that you can use to guide your self-study. And if you want to find a job, a certification is practically required for getting your foot in the door.

I personally recommend the CompTIA series of certifications, because they're well-recognized and I think they expose you to a good breadth and depth of material to get you started. Start with the A+ certification if you have zero tech background. Start with the Network+ certification if you've never taken a networking course. Once you get your basic computer and networking knowledge down, then you can jump into security. The Security+ is a good starting point.

Do I need to know how to code?

No, but it would be really really helpful. You don't have to be a skilled software engineer, but understanding the basics and being able to write small scripts will give you a solid foundation.

From Daniel Miessler's post How to Build a Cybersecurity Career:

You can get a job without being a programmer. You can even get a good job. And you can even get promoted to management. But you won’t ever hit the elite levels of infosec if you cannot build things. Websites. Tools. Proofs of concept. Etc. If you can’t code, you’ll always be dependent on those who can.

How do I gain skills?

Play Capture the Flag (CTF) games.

Stay up to date with security news via an RSS reader, podcasts, or whatever works for you. Research terms that you're unfamiliar with.

Watch conference talks that get uploaded to YouTube.

Spin up a VM to practice working with tools and experiment on your own computer.

There are lots of brilliant, generous people in cybersecurity who share their knowledge and advice for free. Find their blogs, podcasts, and YouTube channels. Look for local meetups in your area.

I'm still relatively new to the field, but I have a general knowledge of lots of different things, so feel free to send me an ask and I can probably help point you to some resources. We're all in this together!

Previous Cybersecurity Masterposts

An Introduction to Cybersecurity

Cybersecurity Book Masterpost

Free Cybersecurity Learning Resources Masterpost

Masterpost of Study Tips for Cybersecurity

Cybersecurity Tools Masterpost

Thank you so much to everyone who participated in the #StudyblrMasterpostJam this week! It was wonderful to see what other studyblr folks are passionate about. The jam technically ends today but there are no official rules, so if you've been thinking about writing a masterpost, this is your sign!

[khizuo]

PP: THATCOPTICWEIRDO

VM: Marteeneee

CA: $Iamphara3na

(capital i)

EMERGENCY!!!

PLEASE HELP ME IF YOU'RE ABLE TO EVEN A DOLLAR HELPS

I've been wrongfully forced out of the abusive transitionary home called Sakina House in Hamtramck, MI under Muslim Family Services and ICNA RELIEF. They are extremely abusive, threatening, and cruel. I have tons of emails, audios, videos, etc documenting their abuses towards me and the other women in that house. It's genuinely terrifying that they claim being Muslim while actively doing everything against the Quran.

They are even threatening a homeless woman there who just need someone to pay to renew her greencard, and they're threatening to kick her out if she doesn't get that done. So that's 4 homeless women at minimum abused and threatened by this organization that made us believe we were getting help and safety which was a lie.

She's literally the sweetest, kindest nurse, and if they do kick her out and I'm able to raise money to stay past Tuesday in this motel room, I'll ask her to stay with me because that's how much I care about these women in comparison to this "Muslim nonprofit". She would literally be on the streets in below freezing temperatures in Michigan. That's the depth of their cruelty. It's unfathomable.

She told me that as I was crying trying to get my belongings out of that house. In their document kicking me out, it states that I have an entire week to get my belongings out. But when I showed up to get the rest of it yesterday, they changed the code to get into building and CHANGED THE LOCK TO MY ROOM DOOR ULTIMATELY TAKING HOSTAGE OF MY OWN NECESSARY BELONGINGS. It's absolutely cruel and insane. I was not informed of any of this, and as far as I'm told, it has never been done before.

I just wanted to get my belongings and never deal with speaking to or with these demons at this organization ever again, but their cruelty and abuses won't even allow me that sort of peace.

I have literally no money left. THANK YOU IMMENSELY TO ISABELLE WHO HAS BEEN THE MOST KIND D0NAR ON HERE AND THE ONLY REASON I WAS ABLE TO GET THIS MOTEL ROOM ON THE 27TH WHEN I GOT KICKED OUT. All day, I called every where I could to get help, but because they purposely kicked me out the night before Thanksgiving, all the already strained community resources and nonprofits have not been available to help me at all. I looked at my P4y.Pal at 1 am and saw that Isabelle donated to me $200 and I burst into tears because that's exactly what I needed I used all I had to get this motel room until Wednesday morning.

I don't even have money for food, water, hygiene products, gas, phone and internet bills, let alone another week in this motel room. I need to raise at minimum 375 for another week in this room and then if I can pay for that, whatever is left will go to those other life essentials. PLEASE I'M BEGGING YOU ALL IF YOU'RE ABLE TO HELP OR KNOW SOMEONE THAT CAN HELP ME, PLS EVEN A DOLLAR HELPS SO MUCH

Please support them on tiktok!! @/theworldindigenousrevolt

[piratesexmachine420]

For future reference (my own and others), if your TI SilverLink USB cable stops working and starts showing up as "TUSB3410 Boot Device" or similar under device manager (AKA this issue on TI's help page), this is how you can fix it:

Download the TUSB3x10 EEPROM Burner. This is a Windows-only program, but to my knowledge will work on basically any windows machine from XP on -- so long as it's got USB ports. No clue if it'll work in a VM. (You might want to consult this user's manual.)

Download the SilverLink firmware. I got it from here, and compiled it from their de-compilation. It's just a standard 'make' to build. The output file you're looking for is called "ti_graph_link_silver.eep".

Rename "ti_graph_link_silver.eep" to "ti_graph_link_silver.bin".

Open the TUSB3x10 EEPROM Burner, click on the options dropdown and click "Show the 'Program Full Binary Image' button". (page 7 of the manual).

Select the entry under "Computer" labeled "TUSB3410 EEPROM Burner Instance (1.00)".

Set EEPROM size to "64Kb".

Set "File Path" to point to "ti_graph_link_silver.bin". (The renamed .eep, not the original .bin)

I don't know if the VID, PID, Manufacturer string, Product string and Serial # need to be set manually or not with a 'Full Binary Image' burn. Just to be safe, I set VID to 0451, PID to e001, Manufacturer to "Texas Instruments", Product to "TI-GRAPH LINK USB", and checked "Not Serialized"*.

Click the "Program Full Binary Image" button (yellow triangle with the exclamation point), and proceed with the write.

Unplug and re-plug your cable, and it should show up as a SilverLink again!

Additional notes:

The reason that this happens is because the SilverLink cable (revision b, at least) is based on the TUSB3410 microcontroller. That microcontroller's boot process involves checking for an I2C EEPROM containing program code. If it finds that EEPROM and its contents are properly formatted, it'll copy that code into internal RAM and start executing it. If it can't find the EEPROM, or its contents aren't properly formatted, it'll fall back to looking for boot code over USB. Thus: "TUSB3410 Boot Device". Your cable has, in essence, forgotten who it is and and is begging for you to give it a purpose.

The default page-write buffer size (32 bytes) and I2C bus speed (400 KHz) in the burner app are already correct, so no need to change them.

*I don't remember exactly what the Manufacturer string, Product string, or serial number fields were set to pre-corruption. Likewise, no idea about the advanced descriptor options. If someone wants to send the output of lsusb -v -s [whatever their silverlink's bus/id numbers are], I'd really appreciate it!

You might be able to skip the header rigamarole by taking the ti_graph_link_silver.bin file directly ("directly coming from the compiler") -- but I again I don't know exactly what information is in the .eep file and what isn't. Are the PID and VID encoded somewhere in there? I peeked with a hex editor but have no clue. If someone has hardware lying around they're willing to experiment with/potentially brick, I'd love to hear your results!

If you mess up and accidentally forget to do a "Full Binary Image" write, or otherwise brick the firmware, you can force the TUSB3410 to fall back to USB boot mode by opening the plastic shell around the PCB (one Torx screw under the sticker, then just normal plastic tabs) and shorting the right-bottom (Vss) and right-top (SDA), or right-bottom (Vss) and center right-top (SCL) pins of the EEPROM (the chip labeled "24LC64") as you plug it into the USB port. You may need multiple attempts. This works because it temporarily convinces the TUSB3410 that the EEPROM is missing/corrupt, and thus it decides to fall back into USB boot mode -- until you reset it. It might be better to do this with a ~1k resistor instead of a jumper wire, but IDK I'm not an electrical engineer. All I know is that shorting Vss and SDA worked for me. Again, would love feedback.

No clue what causes the corruption in the first place, or how long this fix will last. It might be because the EEPROM's write protect pin is set to "write enable"? It could also just be degrading hardware, for all I know, so no idea how long the fix will last. All I do know is that everything seems nominal right now (immediately after performing this procedure).