Good luck @Devil_Master@lemmy.world It is good to see the community growing!
Longer chains have a lot more weight here, I think. But I heard more complaints about post sorting not working well. So it could be a good idea to check what is really happening and see if and how this could be improved.
Wat een rare toestand dat dat dit nog met Cd-roms gebeurt. Ik snap dat het veilig en air-gapped moet, maar je zou verwachten dat we al wel eerder een veilige manier hadden moeten kunnen vinden waarop dit aangepakt kon worden.
Zelf ben ik wel echt voor elektronisch tellen, niet als vervanging van het tellen met de hand, maar meer als een controle. Met het tellen met de hand worden ook gewoon fouten gemaakt en die zou je zo sneller moeten kunnen opsporen. Zolang mensen, maar niet lui worden en eerst de computer laten tellen en vervolgens heel snel tot dezelfde conclusie komen (omdat ze dus gewoon niet goed kijken).
I use Microsoft Edge, Firefox and Safari. I like using a browser that is very similar to Chrome, but I rather avoid Chrome. Edge was also forced for using Bing chat for some time. Safari is fine, but you can't use all the plugins that are available for other browsers, and that is a bit annoying.
I used Firefox a lot before, but some websites that I used had some annoying bugs. I'm also a bit more used to the dev tools of Edge. Of course, I test websites that I build on all 3 browsers, and often have more than one open at the same time.
On the same page, just below that "mark all as read" button, there is an all button, so see all notifications.
I would not be surprised if lemmy.world will outgrow lemmy.ml this month. Lemmy.world has a lot of active communities and meanwhile lemmy.ml. is not allowing new registrations and many of the existing communities look like they are no longer maintained or used.
I just did some more research into this:
When a client tries to log in, the server sends a response back with a JWT token inside the body. The client then stores this token inside an isomorphic cookie. This cookie is then used to identify the user by adding it to all requests after that.
I haven't really checked post requests, but if it is the same So let's say you visit website X, that has nothing to do with Lemmy, they could do a Fetch request in the background to lemmy.world to post spam on your behalf. Even a CSRF token could no longer protect you, as the website could just do a fetch request first to get a CSRF token.
I hope I'm wrong in some way, but to me this feels like a huge security risk.
The headers are set inside the Lemmy binary/docker image. So unless lemmy.world would use its own build, this has to be fixed inside the LemmyNet source code. This would probably make Lemmy vulnerable to cross-site scripting, so the security aspects should probably be discussed in on the Github project.
This is a common issue, there have been a lot of topics about this, I found this post about it that has quite a few responses explaining the cause: https://lemmy.world/post/93315
Amazon really replaces so many webshops in many countries. And after taking over the webshop market, they start copying products that sell well on the platform.
I'm so happy that here in the Netherlands, they still are a small player that has to compete with the other stores. And in the cloud market we at least have Azure, Google Cloud, IBM Cloud and some other that really compete with them. Even in the tech sector, we see more and more companies just reselling services provided by Amazon (but with added value, by making it easier to use them).
Het heeft even geduurd maar ik heb de community gemaakt !tech@feddit.nl. Ik heb het icoontje maar mooi in de stijl gehouden van ons Nieuws kanaal.