Skip to content

‘You can’t pause the internet’: social media creators hit by burnout

Technology
118 51 0
  • 677 Stimmen
    179 Beiträge
    99 Aufrufe
    D
    Thats what the firewall rules do too, don't allow internet connection if there's no vpn connection. Firewall is a system-wide solution that always works, while qbt config relies heavily on the application implementing interface binding properly. Which it doesn't fully btw.
  • No JS, No CSS, No HTML: online "clubs" celebrate plainer websites

    Technology technology
    205
    2
    770 Stimmen
    205 Beiträge
    147 Aufrufe
    R
    Gemini is just a web replacement protocol. With basic things we remember from olden days Web, but with everything non-essential removed, for a client to be doable in a couple of days. I have my own Gemini viewer, LOL. This for me seems a completely different application from torrents. I was dreaming for a thing similar to torrent trackers for aggregating storage and computation and indexing and search, with search and aggregation and other services' responses being structured and standardized, and cryptographic identities, and some kind of market services to sell and buy storage and computation in unified and pooled, but transparent way (scripted by buyer\seller), similar to MMORPG markets, with the representation (what is a siloed service in modern web) being on the client native application, and those services allowing to build any kind of client-server huge system on them, that being global. But that's more of a global Facebook\Usenet\whatever, a killer of platforms. Their infrastructure is internal, while their representation is public on the Internet. I want to make infrastructure public on the Internet, and representation client-side, sharing it for many kinds of applications. Adding another layer to the OSI model, so to say, between transport and application layer. For this application: I think you could have some kind of Kademlia-based p2p with groups voluntarily joined (involving very huge groups) where nodes store replicas of partitions of group common data based on their pseudo-random identifiers and/or some kind of ring built from those identifiers, to balance storage and resilience. If a group has a creator, then you can have replication factor propagated signed by them, and membership too signed by them. But if having a creator (even with cryptographically delegated decisions) and propagating changes by them is not ok, then maybe just using whole data hash, or it's bittorrent-like info tree hash, as namespace with peers freely joining it can do. Then it may be better to partition not by parts of the whole piece, but by info tree? I guess making it exactly bittorrent-like is not a good idea, rather some kind of block tree, like for a filesystem, and a separate piece of information to lookup which file is in which blocks. If we are doing directory structure. Then, with freely joining it, there's no need in any owners or replication factors, I guess just pseudorandom distribution of hashes will do, and each node storing first partitions closest to its hash. Now thinking about it, such a system would be not that different from bittorrent and can even be interoperable with it. There's the issue of updates, yes, hence I've started with groups having hierarchy of creators, who can make or accept those updates. Having that and the ability to gradually store one group's data to another group, it should be possible to do forks of a certain state. But that line of thought makes reusing bittorrent only possible for part of the system. The whole database is guaranteed to be more than a normal HDD (1 TB? I dunno). Absolutely guaranteed, no doubt at all. 1 TB (for example) would be someone's collection of favorite stuff, and not too rich one.
  • 57 Stimmen
    5 Beiträge
    6 Aufrufe
    S
    Imbezzled. Money was used to pay for somebody's vacation.
  • 33 Stimmen
    1 Beiträge
    3 Aufrufe
    Niemand hat geantwortet
  • 166 Stimmen
    10 Beiträge
    3 Aufrufe
    H
    In the meantime: Parents: don’t give your children lighted rectangles to play with.
  • 376 Stimmen
    51 Beiträge
    17 Aufrufe
    L
    I believe that's what a write down generally reflects: The asset is now worth less than its previous book value. Resale value isn't the most accurate way to look at it, but it generally works for explaining it: If I bought a tool for 100€, I'd book it as 100€ worth of tools. If I wanted to sell it again after using it for a while, I'd get less than those 100€ back for it, so I'd write down that difference as a loss. With buying / depreciating / selling companies instead of tools, things become more complex, but the basic idea still holds: If the whole of the company's value goes down, you write down the difference too. So unless these guys bought it for five times its value, they'll have paid less for it than they originally got.
  • Looking elsewhere

    Technology technology
    3
    1
    7 Stimmen
    3 Beiträge
    16 Aufrufe
    J
    That's a valid point! I've been searching for places to hangout for a while, sometimes called "campfires". Found a cool Discord with generous front-end folks (that's a broad spectrum!), on frontend.horse.
  • 17 Stimmen
    1 Beiträge
    11 Aufrufe
    Niemand hat geantwortet