poisonborz

"A small call to any Googler"

Do you think any single one remained who cares over their payment, stock options, office perks? They care about not getting laid off with the next wave.

There are some services that notify on replies :)

Despite your intent your comment is kinda meanly worded, and it is perhaps you who did not read it, or at least mix up terms. In my parent comment I did not mention documentation, but tutorials, as in guide articles like devs not associated with a project writing about how to achieve some goal.

To be more specific, I think there are two distinct type of text that gets written about a project during in its lifecycle, in parallel:

#1 A documentation, written by the maintainers. This will always contain all functions, methods, API endpoints, components, whatever. It's the complete description to the full extent of features. It may or may not also contain the second type. An LLM can theoretically interpret and use the whole project based on this info.

#2 Guides, tutorials, reviews, forum posts, describing or giving tips on the whole project or specific features, or describing methods using that project ("Use x and y to process queries 20x faster on z!"). These writings were essential for the spreading and marketing of a mentioned project. I think this is what the OP article was about. My argument was that these would not be seeked anymore, devs would just ask LLMs "how to achieve x with this tool".

Meaning total trust with your cloud provider / app manufacturer. That is your choice, I wouldn't do it. Selfhosting is kind of a pain still, but gets easier every year (and for simple file sync that you mention, it's already rather easy).

I don't really get "local apps with sync". Sync to what, each other? In most cases there needs to be an always-on central authority (where backup also happens). My point is that "some device sitting alone in a corner with software and data stored on it" model is outdated (this is the "problem", I hope the "why" is obvious). But "local" should live on, just in the form of users owning most of their infrastructure.

I meant both. What do you sync with if no central server (main client)? Anything else is unreliable, on/off all the time. And some simpler workflows don't need native apps.

The goals have shifted. What is "local" nowadays? ~Everybody uses multiple devices, and things are expected to be in sync. What users now (should) need is easy self-hosting apps and centralised storage, with clients that can work/cache offline locally. A good example is Bitwarden.

Software should still come with a documentation that LLMs can train on, plus they have all the learnings from interactions with developers asking about it - who will more and more just go this route (and following whatever guidance they get) and not thinking of searching for other material, let alone write guides for others. I'm not saying this is all that good, but that's the reasonable outcome.

Are tutorials like this even relevant nowadays with LLMs? I think articles of the future should be purely about approach, strategy and pitfalls, not "type in command x" handholding.

If that's not a personal project but a product, that is rather frightening and I hope I won't bump into it. Otherwise, cool!

And after you do, enjoy some maximized windows and notifications covering it.

Signal never syncs old messages on secondary clients for security reasons.

Apples and oranges. It is a nice tool for closed-source Broadcom devices that OpenWRT will never support. Otherwise it has nowhere near the complexity and features.

Backing up Signal on Android for free and offline was ~always possible. The app creates a multi GB backup file on the phone memory under the Signal folder that you can just copy out and back on a new phone.

The file is encrypted with the passcode and the database can be extracted.

https://github.com/bepaald/signalbackup-tools

Don't know why your're downvoted, this is valid criticism. EU just bought 500 mil worth of hardware from the US, no specific European innovation, apart from system management (ParTec Italy). But would be happy to be proven otherwise.

Incredible video. It's one piece of media that would shake the tech world, where it to be shown in 2017 through a time machine.

I wish this would gain more publicity. But I guess people are already desensitized for such news.

"Just throw more money at the problem, bro" /every EU politician and CEO/

It seems to me music streaming is the most widely developed self hosting stack. There are literally dozens if not 100+ platforms, servers and clients - so it's very easy to find what you need, even if it's much different than what OP got.

The problem in the end is political. There is no political willingness to punish major US companies.

Of course they do, it's their job to say so. And the job of politicians with any integrity is to say "No, next topic".

Using nextjs for years without paying a cent to Vercel. If you want React SSR, why would you create a DIY solution if there is a framework with huge community and support?

You only need to move a bit towards suburbia/countryside to create your deep disbelief in public transport. Cars are everywhere, for a reason.

Public transport is great in theory only. With actual human societies - maybe the western ones, that is, except China/Japan - it just doesn't work. Corruption, laziness, bureaucracy, lack of proper planning and security makes the creation and maintenance of these projects unsustainable and so much worse compared to personal transport. This only isn't true for million+ metropolises due to physical constrains.

You may frown at the traffic jams with SUVs having a single driver, but building additional highways is easily doable around the world, while any sort of mass transit infrastructure projects seem to take decades, billions, while still end up underwhelming - if not instantly, then after the machinery ages or maintainers change.

Who cares about them, it will starve society

The point of Tor was never to access classic internet, they actively discourage it. Exit nodes are a convenience feature. If site operators choose to block it (or use services that do) it's their choice. Services should expose onion interfaces - for example, Facebook does.

Oh true :( The above comment then is a wish for a similar upgrade.

Fantastic update, it has everything that made the first version a dealbreaker for me - it was just too weak. I feared Framework will position its 2in1 as a "student laptop", glad to hear they expand on it.

We sorely need more competition in the 2in1 segment, there aren't many good options. Either gaming laptops (no long commitment, bad build quality) or Lenovo Yogas (bad value, limited/weak hw options).

Naive question: why isn't there a publicly accessible central repository of bad IPs and domains, stewarded by the industry, operated by a nonprofit, like W3C? Yes it wouldn't be enough by itself ("bad" is a very subjective term) but it could be a popular well-maintained baseline.

Crowdsec: the idea is tempting, but giving away all of the server's traffic to a for-profit is a huge liability.

It baffles me how in tech folks think "if X wouldn't have been created, there wouldn't be anything comparable created since then".

Software app stores, even mobile app stores existed before, App store's success was mostly a mere consequence of the iPhone's success.

There are no alternatives. S25 is 6.2, and Pixels put the Pro/best version in 6.3, while on Samsung you get a step up to 6.7 and 6.9. Much better specs on almost the same size.

I doubt the human psyche is capable of such a voyage while being awake the whole time. Even with all the toys and biomes, life will get boring and pointless fast, producing unfulfilled needs, disorder, conflict and revolt. People can't be ants in a colony working for such a narrowly defined goal through a lifetime, especially not multi-generationally. Our existence is based on constant questioning and revolutions. A 400 year travel to an unknown, possibly empty, lifeless target, however historic, is not something that can keep a society running long term.