$ go install golang.org/dl/go1.24.0@latest $ go1.24.0 download Downloaded 0.0% ( 0 / 74636413 bytes) ... Downloaded 50.0% (37318206 / 74636413 bytes) ... Downloaded 100.0% (74636413 / 74636413 bytes) Unpacking go1.24.0.linux-arm64.tar.gz ... Success. You may now run 'go1.24.0' $ go1.24.0 version go version go1.24.0 linux/arm64

🥳 Go 1.24.0 is released!

📰 Release notes: go.dev/doc/go1.24

📦 Download: go.dev/dl/#go1.24.0

#golang

You are right, as long as something works it's not "incorrectly" indeed. However, they are advertising to build a TikTok alternative on AT Proto, while they are actually build on BlueSky.

Let's hope they are aware of this. :)

Then maybe some day BlueSky decides they also want to show the SkyLight videos and they can by reading the SkyLight file.

So no, I don't think the videos should feed into BlueSky automatically.

(2/2)

We're all new to the AT Proto, since it hasn't been around for long.😜

I'm not 100% sure. I think I would create a new file on the users repo where I would store the videos/posts uploaded via SkyLight.

To begin with some posts already I would read from the BlueSky file.

(1/2)

Exactly, they are implementing the AT Proto incorrectly.

The SkyLight app would be completely useless without BlueSky, while that is exactly the problem that the AT Proto is trying to solve.

The amount of people who have apparently just given their BlueSky password to SkyLight.🥲

This is not how the AT Proto works. Never share a password from one app with another app.

Besides that, SkyLight and BlueSky are tightly coupled. This is not the intention of the AT Proto. SkyLight should create their own "files" on my repo.

Of course to get started, you can also display the videos that are in the "app.bsky.feed.post" file, but you should not store data in there. (2/2)

I love that you're building this, but I have a major concern. The AT Protocol was build in a way where you should request access to my repo server using OAuth.

Currently you are requesting my BlueSky username and password. This is a big security issue.

(1/2)

A screenshot displaying the difference between response times with different cost variables in the bcryp.GenerateFromPassword function. Value of 10: 102ms Value of 13: 748ms Value of 14: 1493ms

I was wondering why my new register endpoint was so "slow". Apparently I used '14' as the value of the cost param in the bcrypt.GenerateFromPassword() function.

Did a little load test, interesting to see the difference in response time for different costs.

The amount of time I have in a day would disagree haha

I have massive issues with adding a new package to my golang project. 😩

I would rather write the whole thing myself than adding one line to my go.mod.

#golang

This is a great idea! Just donated. F*ck these rich guys trying to control access to information.

I really hope all popular socials will soon get an AT Proto replacement🤞🏼

This article is such an over exaggeration. "Broad" should be emphasized.😉

Cloudflare is also just "guessing" what a close datacenter is near you. If you live in a big city where CF has a datacenter it *could* be possible that the attacker knows your city.

But this is all one big guess.

Of course site X could decide to support the Lexicon schema from site Y. If site X would want to do so.

However, currently it seems like all new apps are just working straight into the existing app.bsky.* schemas.

So, is it me?😅 (3/3)

I personally would also not want my socials to mix. I want my tweets on twitter, my stories on IG and my TikToks on TikTok.

When reading the docs from the AT Proto site I also don't feel like this was ever the goal of the protocol. (2/3)

Is it me or is there some misunderstanding in implementing the AT Protocol. I see so many apps & devs posting things like "Everything you post on my app, will also show up on BlueSky".

These apps should implement the AT Proto, but they should still create their own lexicon schemas right?🤨 (1/3)

Very exciting!! Are you planning on open sourcing the code like @bsky.app?👨🏼‍💻

A screenshot from the golang 1.24 release page talking about the addition of synctest.Run

This is an amazing addition to go 1.24 ⏱️

Testing functionalities that rely on time used to be quite a struggle.

#golang #go124