You can bypass it by changing the user agent to not include Mozilla in the beginning.

Matrix still has it’s problems. All the meta data is still saved on every server permanently.

There is still space to improve from there.

Well, have a look in the old Testament, specifically Leviticus 24:17-22.

19 If anyone injures his neighbor, as he has done it shall be done to him, 20 fracture for fracture, eye for eye, tooth for tooth; whatever injury he has given a person shall be given to him.

You know the part that is shared between Christianity and Judaism.

Honestly, when I open a new application I normally want to interact with it now. Always drove me nuts , when I opened a Powershell window in a folder and then had to click on it again.

Both Boeing and Airbus are working on H2 Tech for Planes.

Or to be more specific. Left and right are ambiguous because of the missing reference frame. It could be my left, your left or the left of the ship.

Port and starboard are always left and right in the reference frame of the ship.

I once woke up at 3. Got a brilliant idea on how to solve one specific problem plaguing me for weeks. Went back to sleep. It was exhilarating.

I just couldn’t remember the solution when I woke up again. Bit for this short period of time it was beautiful.

Remember when selecting something was done with the right mouse button in blender. That was great UX for beginners.

Doesn’t Zed have a vim mode by default?

You should rearrange your structure to group the types from biggest to smallest, otherwise you get padding you didn’t want. BPM and steps for example.

Qspi in general can read single bytes. But we don’t know what controller you use.

Also you probably shouldn’t just read it into memory and cast it to your structure. If you ever change the layout everything breaks apart.

I got something better for you.

namespace 🔵 = std;
using 🔢 = int;
using 💀 = void;
using 🕖 = time_t;
using 👌 = bool;
#define 👂 auto
#define 🎌 enum
#define 👎 false
#define 👍 true
#define 👹 "evil"
#define 💪 🔵::make_shared
#define 🍸 virtual
#define 🖥️ 🔵::cout
#define 🔫 🔵::endl
template<class 🔮>
using 📚 = 🔵::vector<🔮>;
template<class 🔮>
using 👇 = 🔵::shared_ptr<🔮>;

🎌 🐒 { 🐵, 🙈, 🙉, 🙊 };
🔢 🎲() { return 🔵::rand(); }
👌 😎() { return 👎; }

struct 🍴 { 🍸 💀 👀() = 0; };
struct 🍊 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍊" << 🔫; }; };
struct 🍉 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍉" << 🔫; }; };
struct 🍒 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍉" << 🔫; }; };
struct 🍓 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍓" << 🔫; }; };
struct 🍍 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍍" << 🔫; }; };
struct 🍅 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍅" << 🔫; }; };

🔢 main()
{
    if(😎() == 👎)
        🖥️ << "💩" << 🔫;

    📚<👇<🍴>> 🍛 = { 💪<🍊>(), 💪<🍉>(), 💪<🍒>(), 💪<🍍>(), 💪<🍅>() };
 
    for (👂 🍏 : 🍛)
        🍏->👀();

    return 🎲();
}

This only half as bad as the emoji soup macros

You shouldn’t use tabs for alignment. It breaks for everyone with a different tab size.

It’s possible to stream from jellyfin without an account. Jellyfin should not be connected to untrusted networks, like the internet. Several API just don’t check the key or don’t require one in the first place.

https://github.com/jellyfin/jellyfin/issues/5415

Here is some more context. Are they biased? Probably in some shape or form.

Here the link for everyone.

Riddle me this.

A cop shoots a black guy, because he’s black, what does he get?

Some of these are bonkers. The argument not to fix them because of backwards compatibility is even wilder. Which normal client would need the ability to get data for any other account that it hasn’t the Auth token for.

Also a good pen is the report, we need three months for this, only to be told each week something else is more important. After the three month the question came is it finished now.

And so 2 Years turned to 6.

This is an xy Problem. Voting to close.