Skip Navigation

Posts
1
Comments
146
Joined
4 yr. ago

  • His bank accounts are frozen

    Well, don't rely on the banks in the first place, use cash and crypto for everything. Is it not possible to live like this in his country?

  • It does not. That is as optional as fiat exchanges with cryptocurrencies.

    Taler claims to be "not a currency", that means it has to be used with existing currency such as Euro. That means an exchange is not optional. I guess it can be used with a cryptocurrency too, or fake money, but obviously this is not what people are interested in.

    And the resulting tokens are like physical cash and can not be de-anonymized by the exchange or anyone else in the chain.

    Again, according to the Taler website, the exchange tracks every transaction in order to prevent double spends. If it has a full view of the network, it can employ statistical analysis.

    I think you should really inform yourself better before making yourself look really stupid by confidently spreading such non-sense.

    Only you make unsubstantiated claims here.

    If you believe Taler is decentralized, provide an example of it being used with a widely accepted peer to peer currency such as Bitcoin.If you believe Taler is fully private, show us a security audit which confirms Taler's resistance to statistical analysis.

  • It’s not centralized at all

    It depends on the banking system with its proprietary APIs and centralized money issuance.

    privacy for buyers, but not sellers

    In order to spend money, you need to receive it first. I don't know if it makes you a "seller" in Taler, but in any case, this partial protection probably makes de-anonymization of all transactions via statistical analysis much easier.

  • I think this is too complicated. Also, Move is meant to be used when origin and target are collections, but in the FEP they are both actors.

    Why not Update?

    Or, if you want to be explicit, consider introducing a new activity? For example, UpdateAudience:

     
        
    {
        "id": "https://example.social/update-audience"
        "type": "UpdateAudience",
        "actor": "https://example.social/uid/1",
        "to": ["https://www.w3.org/ns/activitystreams#Public"],
        "cc": [
            "https://example.social/audience/1/followers",
            "https://example.social/audience/2/followers",
        ],
        "object": "https://example.social/context/1",
        "prevAudience": ["https://example.social/audience/1"],
        "nextAudience": ["https://example.social/audience/2"],
    }
    
    
      
  • @rimu I sent two reactions, one unicode and one with a custom emoji. The unicode one worked as expected, but the second one with :catjam: is not rendered properly. Also it seems to have replaced the unicode reaction.

  • Blockchain is a bad choice for a social network, it's expensive and all data is public. But since we're talking about decentralization, let's make a rough comparison.

    Bitcoin: 24229 nodes (source: https://bitnodes.io/)Fediverse: 30005 nodes (source: https://fedilist.com/)

    Most of blockchain networks are much smaller than Bitcoin, so they don't even come close to the Fediverse in terms of decentralization.

  • I don't know much about recent developments, but the early version of the protocol had several major flaws:

    Identity is based on a non-rotatable key, other types of identity are not supported. No privacy without encryption. Media attachments are not supported, all images are stored on a single server. Servers only store data and don't do anything else, so they get abstracted away and everyone uses the same 5 relays (in Fediverse each server has a personality, and that creates a strong incentive to self-host).

    There are also many minor things that I dislike, for example the use of numbers instead of human-readable names, unusual cryptography and so on.

  • Currently it's hard to read, there is no single document. No single source of truth.

    We can make it happen.

    I am currently working on this: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md. It's a guide for developers, but in the future it may be used as a base for a more formal specification.

  • Collections are dynamic objects because they can be paginated and filtered. It's not possible to sign a dynamic object, because some of its properties are constantly changing (items, totalItems and others). This means collections need to be always server-managed. Therefore, clients shouldn't be allowed to directly create, update or delete them.

    I think the proposed Move activity is an obfuscated Update because it changes the collection directly.

  • the assumption is already there

    Where, in Lemmy? Even if some implementations don't support cross-posting I don't see a reason to block it at the protocol level.

    And Update is simpler, that's one activity instead of two (Move and Remove).

  • @julian

    FEP-f15d: Context Relocation and Removal

    I have two objections to this proposal. We discussed them before in Moving topics/contexts between communities:

    1. It assumes that a context always belongs to one group.

    As I suggested in the aforementioned thread, an Update activity is a better solution because it works when relationship between a context and a group is many-to-many. It is also semantically cleaner: "update collection audience" instead of "move collection from actor 1 to actor 2" and "remove collection from actor" (at least if ActivityStreams terminology is used).

    1. Treating collections (dynamic views) as static objects that can be moved, deleted etc is not compatible with client-side signing.

    One possible solution is to separate context (an object) and its contents (a collection).

    @jesseplusplus @rimu @nutomic @melroy @BentiGorlich

  • Sucks, right, because on the theadiverse, you're not actually able to do that so easily.

    Sounds like an unnecessary limitation of threadiverse software. Why limit a post to only one community? That doesn't make any sense.

    The person who made the post with multiple mentions clearly did it intentionally, and I would do the same because for every topic I am interested in there are 4-5 groups on different servers.

    Every mentioned person gets addressed

    In most cases, this is what a user wants. Some platforms support silent mentions, though (Friendica, if I remember correctly).

    hashtag / community tag soup

    I think this should be viewed as a moderation problem, not a protocol problem. If you don't want to see mention soup, just limit the number of mentions per post on your instance.

  • It federates, I was told that it uses FEP-1b12. However, I haven't yet gotten past the actor discovery because there is always some bug that prevents further interactions 😅

  • Article Interop WG @lemmy.ml

    Article Interop WG: How to represent titles?