タイッツー 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

Oh yeah, gods forbid anyone plays a game that hasn’t been sold legally for decades…

Honestly, this whole thing is a mess… first a countdown, then a website with basically no information and that’s only the start.

More than 24 hours after signing up, I finally got an email with just about zero information:

Hi @dfyx,

We’re thrilled to welcome you to Loops.video!

We’re in the process of onboarding all our new users, and we can’t wait for you to experience the magic of short looping video.

Keep an eye out for another email from us later tonight or tomorrow (depending on when you signed up). It will have all the details you need to get started, including how to create your first Loop.

Welcome to the Loops community!

Regards, The Loops Team

And from some random comment that dansup made on pixelfed I found out that this beta is only for Android. Apparently, iOS will come later and there is no info on a browser-based version. That info should have been on the website. Also, what about selfhosting? This is the fediverse after all…

Hours? I would give up a week of lunch for them to only cancel stuff that I needed hours to code. My personal record is over a year.

Kind of. All it shows for me is a registration form. When I submit it, they promise me to send an email with further instructions. So far, I didn’t get anything. Honestly, they wouldn’t have needed a countdown for that.

Seems to be a framework to build your own custom fediverse stuff.

The actual recommended solution is to just read in a loop until you have everything.

I don’t think “boring” is the right word for Outlaws. It has much less of the repetitive stuff that has plagued Assassins Creed for years now and instead puts in stuff that’s less frequent but more memorable. I’ve played for about 10 hours so far and it’s been the most fun I’ve had with an open world game in a long time. The annoying stuff is mainly bugs (not too many for me so far) and quality of life stuff like infrequent save points. A few patches down the road this could still become game of the year material.

So far I was fortunate enough to not experience the weird AI bugs but that checkpoint system is sooo infuriating. There’s a side quest where you need to infiltrate a rather large imperial base on Toshara and even the tiniest misstep halfway through the quest will send you back outside the base. It’s 2024, my PS5 is powerful enough to just dump the whole world state from RAM to SSD within a second or two. Why can’t I save manually during a mission?

Other than that, amazing game. It just feels like Star Wars in a way that nothing since KOTOR and Jedi Knight 2 did.

Note that this isn’t specific to Go. Reading from stream-like data, be it TCP connections, files or whatever always comes with the risk that not all data is present in the local buffer yet. The vast majority of read operations returns the number of bytes that could be read and you should call them in a loop. Same of write operations actually, if you’re writing to a stream-like object as the write buffers may be smaller than what you’re trying to write.

As far as I know, ActivityPub only applies to server to server communication. Still, many applications that implement ActivityPub (for example Mastodon) do use push notifications for their clients.

One more difference is that RSS is polling based, meaning that subscribers have to actively ask every hour or so if thre is new content.

On the other hand, ActivityPub knows who is subscribed and can actively distribute new content to other servers who can in turn send push messages to their users, letting you know about new content within seconds.

Looks exactly like Visual Studio 2022.

I guess the joke implies that automated (or incorrect manual) conflict resolution causes code that doesn’t compile. But still not git’s fault. They should probably have merged earlier and in rare cases where that wasn’t possible, you have to bite the bullet and fix this stuff.