jackewiehose

Joined 9 years ago

Karma
1,011
Submissions
290
Member since
Mar 31
View on Hacker News

Recent submissions

Comment · 2 years ago
This isn't about "change", they just removed some essential functionality that I use daily since 1995.

Besides from being used to it, it is also required for my work to have wide, labeled, ungrouped application buttons instead of icons that are oftentimes barely distinguishable.

Comment · 2 years ago
Comment · 2 years ago
Comment · 3 years ago
Because fingerprinting. Shit like this is the reason you are supposed to use the Tor browser only with a tiny window.
Comment · 3 years ago
> I guess there is some unfortunate reason why they can't do the same here

Because they want to support Git for Windows which is built upon Cygwin/msys. And this is fine because Cygwin is much faster than WSL and a good Windows integration is so much easier. Would be a total PITA if Git would only be available through WSL.

Cygwin is still the best thing ever happened to Windows (or to Linuxers who are forced to work with Windows).

Comment · 3 years ago
Thank you. That inspired me to try out the lemmy android app. But that was quite underwhelming. We'll see where that goes.
Comment · 3 years ago
Sorry, but I'm too stupid to find it by myself. Would you give me a hint?
Comment · 3 years ago
Does lemmy has somethings like /r/all? Across all instances?

I'm not interested in subscribing to specific communities. The way I used reddit most of the time was browsing on /r/all using RIF and then I blocked all subreddits I didn't want to see again (a feature of RIF, you don't even need an account).

Comment · 3 years ago
It looks like STUN/TURN can be integrated with QUIC so you don't need additional ports, but I wouldn't say "the complexity is gone" ;-)

https://w3c.github.io/p2p-webtransport/

> This specification extends the WebRTC [WEBRTC], ORTC [ORTC] and WebTransport [WEBTRANSPORT] APIs to enable peer-to-peer operation using QUIC [RFC9000]. This specification supports the exchange of arbitrary data with remote peers using NAT-traversal technologies such as ICE, STUN, and TURN. As specified in [RFC7983bis], QUIC can be multiplexed on the same port as RTP, RTCP, DTLS, STUN and TURN, allowing the API defined in this specification to be utilized along with the functionality defined in [WEBRTC] and [ORTC] including communication using audio/video media and SCTP data channels.

Comment · 3 years ago
> A big difference to WebRTC is: All the STUN / TURN complexity is gone

but STUN / TURN is there for a reason. I always thought of the P2P scenario as the main use case for WebRTC.

Comment · 3 years ago
Comment · 4 years ago
> windows can be set to prohibit executing [...] on a dev machine building windows executables

lol @ "dev machine" ?!

Comment · 4 years ago
> Well for one a website can make you secretly upload copyrighted content with plain old javascript

Only to a webserver and thanks to CORS not to any webserver. There is no benefit for a website doing that - unlike with sharing a torrent to other internet users.

The problem with torrents is that they are actively watched by "Abmahnanwälte" (lawyers who make a living by suing copyright offenders).

> And it's going to be hard to hold you liable for data uploads that someone else initiated and you didn't know about

yeah good luck with that. All they see is your IP and then you can try to explain how this happened and how you are totally innocent.

Comment · 4 years ago
Was I wrong about the torrent stuff or did the downvotes come from web-developers who want WebRTC to be always available by default?
Comment · 4 years ago
Thank you, I will try that. Although I hope that for critical security updates they will be faster... Right now it is lagging behind (105.1.0 vs. current 106.1.0)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton