Melody Fwygon

Mandatory https://archive.is/Dt8FX link

With that being said; I do fully support an Instance’s choice to federate, not federate or even limit their federation with them.

In most cases this should not affect instances; but unfortunately there are people who will ignore all warnings and use the Fedi Garden as a whitelist instead of a list of instances that you know will handle policy violations quickly.

On the other hand I absolutely also respect the needs of communities who ABSOLUTELY, POSITIVELY WILL NOT TOLERATE instances who choose to federate with either X, Threads, or any other instance they deem to be too toxic to play nicely. As instance operators you absolutely have the right to block problems BEFORE they happen, and if you happen to KNOW an instance will absolutely be a HEADACHE, you have every right to say NO. If the users do not like your decision; they are free to find a better instance for themselves; or spin up an alt account on a better instance.

I would argue that federating with either of the biggest companies on the fediverse is a monumentally bad idea.

Not just because of “Reports of genocide” or anything specious like that; which can be debated for days and days on end by people in both good and bad faith; but because both Threads and Meta are simply too large to be moderated correctly and be capable of managing basic issues such as harrassment and extended bouts of hate-speech which should never be considered acceptable; even if you do not necessarily agree with all of the goals and policies of the Fedi Garden; as strict as they are.

I’m sorry to say; but that feature genuinely does not seem to exist in any Open Source PDF reading/editing application.

Just because it “Works For Me!” does not mean it will work.

Beeper very much does not currently allow new users to access the functioning legacy iMessage infrastructure; and Apple itself is making it impractical as well.

From the Beeper Community chatroom on Matrix:

[iMessage] Important Notice.

Beeper no longer provides support for iMessage-related issues.

It has become known that Apple has targeted users of legitimate Mac computers for using Beeper to generate iMessage registration data. Beeper has commented about this situation on Twitter/X here and coverage of this issue has been reported in the New York Times here.

As a result of this media pressure, many of those affected have been successful in having their hardware bans lifted. If you are still affected by a ban that you believe is related to generating a registration code on a Mac computer to use iMessage through Beeper please report it to Beeper Help here and please contact Apple Support as well.

As of this time Beeper has removed support for iMessage from Beeper Cloud due to Apple’s actions. It is suggested that those still using registration data generated from a Mac computer to access iMessage through Beeper delete their existing iMessage bridge in Beeper Cloud.

For any further questions related to iMessage please visit our helpful Discord community.

Officially; No.

Informally; there’s a few mods of the stock Discord client; however they’re all closed source because they cannot possibly be fully open source as the stock Discord client is Closed Source.

Basically; alternatives exist; However they are not FOSS, FLOSS, OS or even fully Source Available.

Beeper exists but this is not strictly a Discord-only client and it is not fully Open Source; as some client/server code is only “Source Available”. Beeper is also not fully “Free”; unless you self-host it. Furthermore access to Beeper is heavily join-gated. You will have to source an invitation code from someone you know. (No, I will not provide one.)

If you do get invited to Beeper; use Beeper Cloud, and be aware that iMessage integration does not work.

You didn’t convert a hex number into Base64, you Base64 encoded the hex string.

TL;DR, you used the wrong tool.

Yeah you can always take a hex hash output and convert it to Base64…which does conpress it significantly. Apply LZ Compression and boom.

I wouldn’t consider them that terribly biased personally; as their livelihood (Money) is put into shorting whatever company is being reported on (Mouth). Literally they put their money where their mouth is…and if they make a horrible mistake in reading a company going under and doing really shady things; they’re going to basically go out themselves pretty quickly and lose a lot of credibility in the process.

Is it maybe a little scummy? Yes. But as they’re calling out scumbags anyways; it looks more like a legitimate application of “taking a scammer to know a scammer”. It’s better that they’re legitimately profiting from calling out companies that are cheating everyone and reporting on it to benefit the public in the process.

I don’t like the idea of a prompt being subtly manipulated like this to “force” inclusion. Instead the training data should be augmented and the AI re-trained on a more inclusive dataset.

The prompt given by the user shouldn’t be prefixed or suffixed by additional words, sentences or phrases; except to remind the AI what it is not allowed to generate.

Instead of forcing “inclusivity” on the end user in such a manner; we should instead allow the user to pick skin tone preferences in an easy to understand manner, and allow the AI to process that signal as a part of it’s natural prompt.

Obviously; where specific characters are concerned, the default skin tone of the character named in the prompt should be encoded and respected. If multiple versions of that character exist, it should take a user’s skin tone output selection into account and select the closest matching version.

If the prompt is requesting a skin tone alteration of a character; that prompt should obviously be honored as well, and executed with the requested skin tone; and not the skin tone setting selection. As an example I can select “Prefer ligher skin tones” in the UI and still request that the AI should generate me a “darker skinned version” of a typically fairer skinned character.

Instead of focusing on forcing “diversity” into prompts that didn’t ask for it; let’s just make sure that the AI has the full range of human traits available to it to pull from.