[–] 3 points 1 month ago* (2 children)

They bought an implementation of RCS, the standard is still open. They even sell there implementation to a few telcos.

You cant self host it because you need to be a telco, it has telco specific protocols. Also, this is one of the things that probably should be gatekept to telcos, if everyone were able to spin up their own instance, the spam problem would be unmanageable.

Your looking for a conspiracy/monopoly that for once, doesnt exist due to Google being malicious. It exists because telcos are shit.

  • source
  • parent
  • context
  • [–] 12 points 1 month ago (7 children)

    Google didn't develop RCS, GSMA did. All google did was purchase the startup that actually developed a good implementation of it.

    This isnt some gatekeeping exercise from google, they had nothing to do with RCS's initial design and release. The carriers are entirely to blame for dragging their feet, although some are finally implementing their own servers (China is entirely RCS without google).

    As for "federate it, decentralise it", thats how it already is. Its called "hubbing", but its basically federation. The networks run their server, and the federate messages between them. It isn't centralised at all.

  • source
  • parent
  • context
  • [–] 0 points 1 month ago

    Except that they are separated. The clean side (model + implementors) doesnt have the original source code. The dirty side is the training room, which does have original source.

    The model that you download from huggingface is basically the notebook passed between the two rooms, and as far as im aware, the model doesnt have the actual training data in it, just enough statistics to "hallucinate" something close.

  • source
  • parent
  • context
  • [–] 0 points 1 month ago (2 children)

    Thats not a difference. Other clean room projects, for example ReactOS, have source projects that are incompatibly licenced. Its the entire point of clean room reversing, to bypass copyright and licencing.

    The training data is on the dirty room side, it doesnt get passed to the clean side.

    The clean room concept is violated if raw source code is in the model generated, but to my knowledge its not. There is no way to pull out a chunk of the model, and say "This is a direct copy of main.c from xyz project". At best, you can ask the LLM to guess what it should be, and it'll regurgitate something statistically close. I just tried asking my local qwen3.8, and did produce a close summary of the nginx main file, but it wasn't even close to a 1 to 1 copy.

    The clean room would also be violated if you consider the training, model and inference as a singular entity, but that would be tough to argue when the inference can happen on one server, the resulting model isn't functional in any way, its a big box of data, and the inference can happen on any GPU anywhere else in the world.

  • source
  • parent
  • context
  • [–] 0 points 1 month ago

    I don't have any problem with police getting in touch with someone they believe is at risk of committing a crime. Better to check in and make sure they are okay, rather than waiting until something terrible happens. As long as its limited to "Are you okay?" then its fine IMO.

    Requires a police force that has the trust of the people though, and that is increasingly rare.

    And its difficult to square that with the right to privacy/no unreasonable searches.

  • source
  • parent
  • context
  • view more: ‹ prev next ›