Hacker Newsnew | past | comments | ask | show | jobs | submit | Parodper's commentslogin

> EU anti-AI laws

God I wish.


The EU has their own Mastodon instance, but unless you want to have responses (even if the official instance doesn't show them), it's cheaper to run a static news aggregator.

It would be nice, but it seems most people don't care about this.


He isn't. He has a bachelor in economics and physics.


You're an engineer as soon as you make an engineering decision. End of.


Doing engineering ≠ being an engineer.

Am I a doctor because I took my temperature and found I had a fever? Am I a lawyer if I represent myself in court?

At least where I'm from, you need to be licensed to practice engineering.


Train drivers blowing their own horns are only Engineers in the weakest possible sense.


I'm at the point where I think you people are just dumb. The amount of people I've worked with my in career who did things totally outside of their major in college or simply dropped out entirely. I'm literally sitting here thinking about how intellectually destitute the so called left has become and it makes me sad.


> the so called left

HUH?

When did that ever come up?


We're just reinventing moderated Usenet newsgroups.


People seemed to like it being stuck in the 1980s.


SMS made you pay by character. RCS is the current free alternative.


so instead using Meta product you suggest using Google product, great alternative for Europe independence

it's like when they wanna get rid of Visa/MC by switching to EU apps, which will require Google/Apple verification, what an improvement...


RCS is an international standard. Google only adds their client (and running the service if your mobile provider doesn't).

Don't know what EU apps are you talking about, but yes, mobile apps need Google services. Web interfaces don't.


please tell me ONE app for Android other than Google Messages I can use to send and receive RCS, it surely won't be problem since it's international standard same as SMS, so there must be plenty apps available...

Pretty much all banking apps for Android won't work without Google Play Services, so once again if you are using Lineage or Graphene, you are still stuck with US company to use your European banking services on the phone.


> please tell me ONE app for Android other than Google Messages I can use to send and receive RCS, it surely won't be problem since it's international standard same as SMS, so there must be plenty apps available...

Nice red herring. The number of implementations is irrelevant here, although Wikipedia says Samsung had one too.

Here's the standard, try Ctrl+F "Google": https://www.gsma.com/solutions-and-impact/technologies/netwo...


TLDR there is only Google product if you wanna use RCS on Android phone

nobody cares about standards, if they are pretty much monopolized by one comapny



Ctrl/Shift+Insert are the actual standard, from IBM's CUA.


I know those from growing up with QBASIC and EDIT.COM, but I think the only software I've used that actually supports them is the Windows conhost (the default UI for command-line apps).


GNU/Linux[1] seems to support it. Windows probably does too.

[1] Tested on KDE Wayland and Xfce X11.


What? Ctrl/Shift Insert is supported basically everywhere in Windows, from the lowly Notepad to the behemoth that’s Microsoft Word. Browsers support it. Terminals support it. On Linux all Linux apps I’ve tried support it. Even Emacs which famously doesn’t support the usual C-c C-v supports it (mapped to kill-ring-save and yank). This is as universal as possible in the world without Cmd key.

In fact the last time I bought a keyboard I made sure the keyboard mapping can be customized so I can actually put the Insert key on it.


Same I grew up using Ctrl+Shift+Insert, and only really migrated over to Ctrl+C/Ctrl+V when I started using mouse-driven environments more heavily, because I could drive copy paste with my left hand and keep the mouse in my right.


> Doing this brings you close to OSI, which famously failed by being overcomplicated.

We're slowly reinventing OSI, one step at a time: OSI had multiple sessions per transport connection (QUIC), 20 byte addresses (IPv6) and a directory system with public-key infrastructure (DANE, vCard, SSHFP, etc).

It's a shame TUBA (CLNP + TCP) failed.


> It's a shame TUBA (CLNP + TCP) failed.

See "The Recommendation for the IP Next Generation Protocol", §8.3 TUBA Reviews:

* https://datatracker.ietf.org/doc/html/rfc1752

The document explains why SIPP was chosen (with the tweak of 128-bit addresses instead of 64).


Very interesting, thanks. I like they even admit their own bias, that the main reason was that they didn't want another's protocol; except for the word alignment, all the other issues are solvable.


You could start the encoding with two bytes, so that if the most significant bit of the first byte is 0, the length is that byte plus another. That gives you 32KiB strings with just a byte more. Short strings might suffer, but I think the overhead is reasonable.

The next level (110x xxxx) would give you 8MiB strings, which are going to be fine for most things.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: