Going to need a source for a bombshell like that.

Austrian

lichess good

Usenet is federated (which is a type of decentralization), and I think OP means peer-to-peer (fully distributed).

I used mine as a CUPS printserver to share a USB printer on the network. It was pretty slow when spooling though.

b3ta.com is still going? bloody hell it’s brilliant

Where are the sample queries and corresponding results to demonstrate that it works well? Oh there aren’t any?

I thought this was going to be a new article or news, but it’s from April 9, 2024.

I think this situation has been picked over and rehashed now to the point where anyone who was going to change their behaviour will have already done so. If there is no update on the situation then all I see is you dragging up drama from a year ago.

Yes it is completely fine and legal.

You’ll only have a problem if the application has features that are patented and the patents are enforceable. Or if you are impersonating a trademark.

Can you link the bug report please?

The irony is that if we didn’t have the tracking scripts blocked then they might actually receive the metrics about how we close their website as soon as the newsletter popup occurs, leading them to fix or remove it. Probably not though.

Although there were already discussions about it as early as 2005 (and earlier), Loic and company had been hosting a Web3 conference in France (“Le Web3”) for a few years back then. (The real Web3, not the crypto-Web3. < this is why many, if not most, Fediverse devs don’t like crypto, the crypto enthusiasts stole “Web3”)

I think you’ve retconned a little bit here. LeWeb3 was named as a sequel to the previous conference which was called LeBlogs2. Remember, at that time Web 2.0 hadn’t really taken off yet - browsers had only just implemented the XMLHTTPRequest API - so it wouldn’t have made sense to already be talking about Web 3.0.

Here is an original document containing some history of LeWeb3: https://web.archive.org/web/20070704054929/http://www.loiclemeur.com/LeWeb3executivesummaryv1.pdf

It was pretty obvious the approach behind for instance Deep Blue wasn’t the way forward.

That’s a weird example to pick. What exactly about Deep Blue do you think wasn’t the way forward?

I once had an issue logging in to Google where they wanted to verify me some way that I couldn’t complete. I eventually got around it by going through the “Forgot Password” workflow instead of logging in normally. I have no idea if this still works or whether it will make things worse for you, but if all else fails it might be worth a try.

What did he lie about? What was the larger case about?

that’s a link to a telegram post, for the benefit of anyone who would prefer not to load the telegram website from wherever you’re browsing from.

was this UAV safe?

Good luck alt-tabbing to the one you want.

This is what workspaces are for.

You need to put yourself in the shoes of a non-technical person who doesn’t know how to evaluate the relative security of all the tools that are out there available to them. If you are posting your pre-alpha untested software with a title like “Anti-forensic and secure messenger” then there are many people who will read that and think that it’s on an equal footing as the other tools they have heard of. The vast majority of people are not software engineers, and even fewer are cryptographers.

this project is still in heavy development so without it getting professional security audit i wouldn’t recommend using it for sensitive stuff.

You’ve got to lead with this.