L1[00:35:16] ***
SatanicSanta is now known as Santa|afk
L2[01:03:11] ⇦
Quits: CovertJaguar (~you@65.183.205.6) (Read error: Connection
reset by peer)
L3[01:03:31] ⇨
Joins: CovertJaguar (~you@65.183.205.6)
L4[01:03:31]
ChanServ sets mode: +o on CovertJaguar
L5[01:37:51] 
<CovertJaguar> The goal is to be able
to do releases for both 1.10 and 1.11 at the some time
eventually
<CovertJaguar> The goal is to be able
to do releases for both 1.10 and 1.11 at the some time
eventuallyL6[01:38:13] <CovertJaguar> but I don't have a
great graps on how much work getting to that point is going to
be
<CovertJaguar> but I don't have a
great graps on how much work getting to that point is going to
beL7[02:45:39] ⇦
Quits: mallrat208 (~mallrat20@107-145-175-135.res.bhn.net) (Ping
timeout: 201 seconds)
L8[02:45:56] ⇨
Joins: mallrat208
(~mallrat20@107-145-175-135.res.bhn.net)
L9[02:51:49] ⇦
Quits: mallrat208 (~mallrat20@107-145-175-135.res.bhn.net) (Ping
timeout: 201 seconds)
L10[02:52:03] ⇨
Joins: mallrat208
(~mallrat20@107-145-175-135.res.bhn.net)
L11[03:49:41] ***
MrKick|Away is now known as MrKickkiller
L12[03:50:12] ⇨
Joins: ImQ009
(~ImQ009@89-74-217-232.dynamic.chello.pl)
L13[03:51:02] ⇨
Joins: Lizzy (Lizzy@znc.theender.net)
L14[03:52:31] ⇨
Joins: Forecaster (Forecaster@znc.theender.net)
L15[03:52:33]
ChanServ sets mode: +o on Forecaster
L16[03:53:37] ⇨
Joins: Techokami (Techokami@znc.theender.net)
L17[03:57:52] ⇨
Joins: scj643 (~quassel@scj.theender.net)
L18[04:09:47] ⇨
Joins: Hgreb
(~Hgrebnedn@ptr-908g3oryo86zpn1nk7p.18120a2.ip6.access.telenet.be)
L19[04:17:25] ⇦
Quits: Techokami (Techokami@znc.theender.net) (Ping timeout: 190
seconds)
L20[04:18:02] ⇦
Quits: Forecaster (Forecaster@znc.theender.net) (Ping timeout: 204
seconds)
L21[04:18:40] ⇦
Quits: Lizzy (Lizzy@znc.theender.net) (Ping timeout: 204
seconds)
L22[04:23:23] ⇨
Joins: Lizzy (Lizzy@znc.theender.net)
L23[04:23:36] ⇨
Joins: Forecaster (Forecaster@znc.theender.net)
L24[04:23:40]
ChanServ sets mode: +o on Forecaster
L25[04:24:46] ⇨
Joins: Techokami (Techokami@znc.theender.net)
L26[04:40:09] ⇨
Joins: Vexatos
(~Vexatos@p5B3C9D9D.dip0.t-ipconnect.de)
L27[04:48:59] ⇦
Quits: neptunepink (~root@2601:640:c300:1620:f489:160a:8cb8:59b5)
(Ping timeout: 201 seconds)
L28[05:34:45] ⇨
Joins: MCenderdragon (~MCenderdr@46.79.237.62)
L29[07:20:48] <GeneralCamo> 1.12 is a possibility,
however the preliminary looks I did does not bode well
<GeneralCamo> 1.12 is a possibility,
however the preliminary looks I did does not bode wellL30[07:20:56] <GeneralCamo> And that was nearly a
month ago
<GeneralCamo> And that was nearly a
month agoL32[07:42:03] ⇨
Joins: Xilandro
(~Kodos@2602:306:ce20:6c30:e541:f23d:8cff:7271)
L33[07:45:21] ⇦
Quits: Kodos (~Kodos@2602:306:ce20:6c30:10a:814b:38db:22f7) (Ping
timeout: 201 seconds)
L34[08:07:22] <liach>
@GeneralCamo Wanna work on stacksize changes?
<liach>
@GeneralCamo Wanna work on stacksize changes?L35[08:12:46] <Speiger> @Vexatos it got worse in
1.7.10 thats why i decided to do a rewrite from scratch which
cleaned a lot up xD
<Speiger> @Vexatos it got worse in
1.7.10 thats why i decided to do a rewrite from scratch which
cleaned a lot up xDL36[09:36:09] ⇨
Joins: turmfalke
(~turmfalke@p5B0830CA.dip0.t-ipconnect.de)
L37[10:36:58] ⇨
Joins: Johannes13
(~Johannes1@dslb-094-216-023-108.094.216.pools.vodafone-ip.de)
L38[10:37:01] ⇨
Joins: Johannes13_
(~Johannes1@dslb-094-216-023-108.094.216.pools.vodafone-ip.de)
L39[10:37:04] ⇦
Quits: Johannes13_
(~Johannes1@dslb-094-216-023-108.094.216.pools.vodafone-ip.de)
(Read error: -0x7880: SSL - The peer notified us that the
connection is going to be closed)
L40[10:38:23] ***
Johannes13 is now known as DasBrain
L41[14:43:30] ⇨
Joins: neptunepink
(~root@2601:640:c300:1620:20d9:201c:3c6d:81e5)
L42[14:47:33] <MipoloArchiletti> Does Railcraft work
best as an above-ground or below-ground system?
<MipoloArchiletti> Does Railcraft work
best as an above-ground or below-ground system?L43[14:53:54] <Forecaster> entierly depends what you
do with it
<Forecaster> entierly depends what you
do with itL44[15:10:49] ⇨
Joins: SatanicSanta (~SatanicSa@76.115.175.15)
L45[15:11:33] ⇦
Quits: SatanicSanta (~SatanicSa@76.115.175.15) (Client
Quit)
L46[15:12:47] ***
Santa|afk is now known as SatanicSanta
L47[15:12:59] ***
SatanicSanta is now known as Santa|afk
L48[15:13:03] ***
Santa|afk is now known as SatanicSanta
L49[15:37:20] ⇨
Joins: Hathadar
(Hathadar@c-73-20-95-143.hsd1.ut.comcast.net)
L50[15:42:57] <Hathadar> I have several
holding bays which feed into one line. How may I automatically
allow only one train in at a time?
L51[15:43:09] <Hathadar> The holding bays
are parallel to each other.
L52[15:44:51] <Forecaster> signals
<Forecaster> signalsL53[15:46:13] <Hathadar> That is like
saying rain comes from the sky when I am interested in learning
about the water cycle.
L54[15:46:26] <Hathadar> I am looking for a
more detailed explination.
L55[15:46:37] <Forecaster> then ask a more specific
question
<Forecaster> then ask a more specific
questionL56[15:47:38] <Hathadar> I thought my
question was fairly specific. How may I release only one train from
several parallel holding bays when the way ahead becomes
clear?
L57[15:48:46] <Forecaster> by setting up signal
blocks ahead and connecting them to your locking tracks
<Forecaster> by setting up signal
blocks ahead and connecting them to your locking tracksL58[15:49:35] <Hathadar> I have signal
blocks setup. The problem I am running into is when the way out of
the holding bays becomes clear, all othe trains will be released at
once.
L59[15:49:44] <Hanakocz> if more trains do wait for
signal, then you probably want some delay mechanics
<Hanakocz> if more trains do wait for
signal, then you probably want some delay mechanicsL60[15:50:23] <Hathadar> Yes. I am looking
for the logic to set that up.
L61[15:50:36] <Forecaster> you could simply make
each bay a signal block
<Forecaster> you could simply make
each bay a signal blockL62[15:50:52] <Hathadar> I know the
capacitor allows for the introduction of delays, but not
conditionally.
L63[15:52:15] ⇦
Quits: Vexatos (~Vexatos@p5B3C9D9D.dip0.t-ipconnect.de) (Quit: I
guess I have to go now. Bye β)
L64[15:52:34] <Forecaster> make each bay a signal
block, only allow the trains to advance if the bay ahead is
clear
<Forecaster> make each bay a signal
block, only allow the trains to advance if the bay ahead is
clearL65[15:52:51] <Hathadar> You are describing
holding bays in series. I am wanting to set them up in
parallel.
L66[15:53:30] <Hathadar> if (bayA ==
occupied && bayB == occupied && bayC == occuplied)
then release bayA.
L67[15:53:48] <Forecaster> oh, I misunderstood
you
<Forecaster> oh, I misunderstood
youL68[15:53:57] <Forecaster> the solution to that is
the interlock box
<Forecaster> the solution to that is
the interlock boxL69[15:54:03] <Forecaster> I happen to have a video
about that
<Forecaster> I happen to have a video
about thatL70[15:54:29] <Hathadar> Please do
share.
L71[15:55:11] <Hanakocz> each parallel track will
have two parts in series. First part will be for your work to be
done, then second part will be waiting line, you let trains go into
second part only if no other part is full. If you have those second
parts different in size, there won't be two trains that would
get to the main outgoing track at one time
<Hanakocz> each parallel track will
have two parts in series. First part will be for your work to be
done, then second part will be waiting line, you let trains go into
second part only if no other part is full. If you have those second
parts different in size, there won't be two trains that would
get to the main outgoing track at one timeL73[15:57:00] <Hathadar> thanks
L74[15:57:38] <Forecaster> you can skip to about 28
minutes
<Forecaster> you can skip to about 28
minutesL75[15:57:50] <Forecaster> that's when the bit
that's relevant to what you want starts
<Forecaster> that's when the bit
that's relevant to what you want startsL76[15:58:16] <Forecaster> basically I built a
station that has paralel platforms and has a system that ensures
only one train can leave at a time
<Forecaster> basically I built a
station that has paralel platforms and has a system that ensures
only one train can leave at a timeL77[16:08:42] <Forecaster> there's also a link
to a world download in the description
<Forecaster> there's also a link
to a world download in the descriptionL78[16:11:55] <Forecaster> (it's for
1.7.10)
<Forecaster> (it's for
1.7.10)L79[16:37:12] <Hathadar> Is there any such
thing as an AND gate in railcraft?
L80[16:38:27] <CovertJaguar> If you refering to
aspects, if you have two receivers connected to a controller, the
controller will output the most restrictive aspect of the two
receivers
<CovertJaguar> If you refering to
aspects, if you have two receivers connected to a controller, the
controller will output the most restrictive aspect of the two
receiversL81[16:38:36] <Forecaster> ^
L82[16:38:48] <Forecaster> you can make an
AND gate using boxes
L83[16:42:43] <Natesky9> I made a really functional
first-in, first-out loading bay with interlock boxes, receivers,
and repeaters
<Natesky9> I made a really functional
first-in, first-out loading bay with interlock boxes, receivers,
and repeatersL84[16:43:00] <CovertJaguar> you can also convert to
redstone and do logic there
<CovertJaguar> you can also convert to
redstone and do logic thereL85[16:43:35] <Hathadar> Nate, did you
document your build?
L86[16:43:56] <Natesky9> I have a screenshot of
it...let me dig it up
<Natesky9> I have a screenshot of
it...let me dig it upL88[16:45:34] <Natesky9> I can explain it from
memory as best I can
<Natesky9> I can explain it from
memory as best I canL89[16:46:42] <Hathadar> Please do.
L90[16:47:54] ⇦
Quits: Hgreb
(~Hgrebnedn@ptr-908g3oryo86zpn1nk7p.18120a2.ip6.access.telenet.be)
(Ping timeout: 204 seconds)
L91[16:54:05] <Hathadar> BTW, I was reading
through issues on github and came to a suggestion thread about
teleportation tracks. I agree with your sentiment, CovertJaguar. I
dislike teleportation.
L92[16:57:33] <Forecaster> It does kind of defeat
the point of railways
<Forecaster> It does kind of defeat
the point of railwaysL93[17:00:38] <Hathadar> Indeed.
L94[17:06:17] <Natesky9> Alright, so from the bottom
up
<Natesky9> Alright, so from the bottom
upL95[17:06:30] <Natesky9> Receivers, one per
lane
<Natesky9> Receivers, one per
laneL96[17:06:49] <Natesky9> Repeaters
<Natesky9> RepeatersL97[17:08:59] ***
manmaed[away] is now known as manmaed
L98[17:10:00] ***
manmaed is now known as manmaed[away]
L99[17:10:19] ***
manmaed[away] is now known as manmaed
L100[17:20:53] <Hathadar> Nate, were you
still going to explain your FIFO holding station?
L101[17:23:36] <Natesky9> Yeah, I'm actually at
work, so I'm half here
<Natesky9> Yeah, I'm actually at
work, so I'm half hereL102[17:25:36] <Natesky9> So, the repeaters take the
signal from the line, the line being a separate line that holds one
train
<Natesky9> So, the repeaters take the
signal from the line, the line being a separate line that holds one
trainL103[17:26:49] <Natesky9> That goes into an interlock
box, the interlock boxes "remember" the order that the
Redstone was input
<Natesky9> That goes into an interlock
box, the interlock boxes "remember" the order that the
Redstone was inputL104[17:27:33] <Natesky9> Sorry, I probably confused
you there
<Natesky9> Sorry, I probably confused
you thereL105[17:29:22] <Natesky9> Block signal -> receiver
-> repeater -> controller -> interlock -> receiver
-> locking track
<Natesky9> Block signal -> receiver
-> repeater -> controller -> interlock -> receiver
-> locking trackL106[17:30:34] <Hathadar> so the LIFO
functionality is inherent in the interlock boxes?
L107[17:31:34] <Hathadar> FIFO*
L108[17:32:11] <CovertJaguar> I do have some thoughts
on a teleportation system that isn't that bad for railways,
but its a lot harder most current teleportation systems and tied to
worldgen
<CovertJaguar> I do have some thoughts
on a teleportation system that isn't that bad for railways,
but its a lot harder most current teleportation systems and tied to
worldgenL109[17:33:17] <Hathadar> IMO, the only
appropriate rail teleportation is between dimensions. Even then it
must be geographically dependent. coordinates 0,0 in the overwrold
go to 0,0 in the end.
L110[17:33:19] <CovertJaguar> the interlock boxes
only allow one lane to be "open" at any given time
<CovertJaguar> the interlock boxes
only allow one lane to be "open" at any given timeL111[17:33:46] <Hathadar> I understand
that much, but do they operate on a LIFO basis? Are they a
queue?
L112[17:33:56] <CovertJaguar> they are an
interlock...
<CovertJaguar> they are an
interlock...L113[17:34:30] <CovertJaguar> there is a order of
precidence on which lane would be considere the "open"
lane
<CovertJaguar> there is a order of
precidence on which lane would be considere the "open"
laneL114[17:34:57] <CovertJaguar> which is dependant on
the coordinate sorting of the interlock boxes themselves
<CovertJaguar> which is dependant on
the coordinate sorting of the interlock boxes themselvesL115[17:35:08] <CovertJaguar> but that's
it
<CovertJaguar> but that's
itL116[17:38:09] <CovertJaguar> and the open lane
remains open until the input changes
<CovertJaguar> and the open lane
remains open until the input changesL117[17:42:57] <CovertJaguar> @Natesky9 what is the
reason for the repeater?
<CovertJaguar> @Natesky9 what is the
reason for the repeater?L118[17:43:47] <Natesky9> Signal boxes don't
transmit Redstone between them, and I needed to invert the
signal
<Natesky9> Signal boxes don't
transmit Redstone between them, and I needed to invert the
signalL119[17:44:15] <CovertJaguar> ah
<CovertJaguar> ahL120[17:44:27] <bball>
but they accept and emit redstone signals
<bball>
but they accept and emit redstone signalsL121[17:44:35] <bball>
if you configure them correctly
<bball>
if you configure them correctlyL122[17:49:44] ***
MrKickkiller is now known as MrKick|Away
L123[17:54:19] ⇦
Quits: ImQ009 (~ImQ009@89-74-217-232.dynamic.chello.pl) (Quit:
Leaving)
L124[17:56:53] <Hathadar> Interlock boxes
don't have aspect precedence, do they?
L125[17:57:45]
⇨ Joins: sinkillerj
(~sinkiller@nc-67-232-11-204.dhcp.embarqhsd.net)
L126[18:00:07] <CovertJaguar> only one output can be
green or yellow, everything else is red
<CovertJaguar> only one output can be
green or yellow, everything else is redL127[18:13:00]
⇨ Joins: Fandroid
(~Fandroid@2601:203:203:6310:3c65:2b68:d8b6:2563)
L128[18:14:01] ***
manmaed is now known as manmaed[away]
L129[18:15:09] ⇦
Quits: MCenderdragon (~MCenderdr@46.79.237.62) (Quit:
Leaving)
L130[18:19:10] <Hathadar> Forecaster, how
do I make an AND gate using boxes?
L131[18:19:50] <bball>
two recievers adjacent to one controller
<bball>
two recievers adjacent to one controllerL132[18:27:03] ⇦
Quits: turmfalke (~turmfalke@p5B0830CA.dip0.t-ipconnect.de) (Ping
timeout: 186 seconds)
L133[18:31:38] <Natesky9> Hmm, not exactly. That just
passes the most restrictive aspect
<Natesky9> Hmm, not exactly. That just
passes the most restrictive aspectL134[18:32:03] <Natesky9> You'll need to make an
actual AND gate using Redstone
<Natesky9> You'll need to make an
actual AND gate using RedstoneL135[18:32:31] <Natesky9> Thankfully, Redstone
torches on top of signal boxes actually works correctly
<Natesky9> Thankfully, Redstone
torches on top of signal boxes actually works correctlyL136[18:55:00] ***
SatanicSanta is now known as Santa|afk
L137[18:59:12]
⇨ Joins: travis-ci
(~travis-ci@ec2-54-146-20-214.compute-1.amazonaws.com)
L138[18:59:13] <travis-ci>
Railcraft/Railcraft#664 (mc-1.10.2 - b34fc53 : CovertJaguar): The
build passed.
L139[18:59:14] <travis-ci> Change view :
https://github.com/Railcraft/Railcraft/compare/48365c5d0e35...b34fc53864db
L140[18:59:14] <travis-ci> Build details :
https://travis-ci.org/Railcraft/Railcraft/builds/246915431
L141[18:59:14] ⇦
Parts: travis-ci
(~travis-ci@ec2-54-146-20-214.compute-1.amazonaws.com)
())
L142[19:03:48] <Natesky9> And yes, signal boxes emit
and accept Redstone signals, but they do not pass them through
adjacent linkages
<Natesky9> And yes, signal boxes emit
and accept Redstone signals, but they do not pass them through
adjacent linkagesL143[19:05:46]
⇨ Joins: travis-ci
(~travis-ci@ec2-54-167-232-241.compute-1.amazonaws.com)
L144[19:05:46] <travis-ci>
Railcraft/Railcraft#665 (mc-1.10.2 - 465f28c : CovertJaguar): The
build passed.
L145[19:05:46] <travis-ci> Change view :
https://github.com/Railcraft/Railcraft/compare/b34fc53864db...465f28c7ee72
L146[19:05:46] <travis-ci> Build details :
https://travis-ci.org/Railcraft/Railcraft/builds/246916547
L147[19:05:46] ⇦
Parts: travis-ci
(~travis-ci@ec2-54-167-232-241.compute-1.amazonaws.com)
())
L148[19:27:48] <bball>
but they pass an aspect to adjacent linkage, then the adjacent box
outputs a RS signal based on the aspect
<bball>
but they pass an aspect to adjacent linkage, then the adjacent box
outputs a RS signal based on the aspectL149[19:32:03] ⇦
Quits: Doty1154 (~Doty1154@2601:648:8000:134f:819a:fbd6:1a8c:8042)
(Ping timeout: 201 seconds)
L150[19:33:02]
⇨ Joins: Doty1154
(~Doty1154@c-73-189-164-179.hsd1.ca.comcast.net)
L151[19:33:17] <Natesky9> Yes, but in the case of
block -> interlock, you want to invert the aspect for that lane.
The only way to do that is to take the aspect, emit Redstone, and
invert
<Natesky9> Yes, but in the case of
block -> interlock, you want to invert the aspect for that lane.
The only way to do that is to take the aspect, emit Redstone, and
invertL152[19:34:42] <Natesky9> Then you can pass the
respective inverted aspects, and allow obit one train to leave at a
time, pausing for each one to fully leave the station
<Natesky9> Then you can pass the
respective inverted aspects, and allow obit one train to leave at a
time, pausing for each one to fully leave the stationL153[19:38:55] <bball>
you can set it to output on all aspects that are _not_ the one you
want to invert
<bball>
you can set it to output on all aspects that are _not_ the one you
want to invertL154[19:40:07] ⇦
Quits: Bunsan (~bunsan@S010674440131016b.cg.shawcable.net) (Ping
timeout: 186 seconds)
L155[19:40:46]
⇨ Joins: Bunsan
(~bunsan@S010674440131016b.cg.shawcable.net)
L156[19:43:39] <Natesky9> Yes, but the interlock
boxes. They don't have a gui
<Natesky9> Yes, but the interlock
boxes. They don't have a guiL157[19:43:53] <Natesky9> So you have to invert
before them
<Natesky9> So you have to invert
before themL158[19:44:05] <bball>
why are you trying to output the interlock?
<bball>
why are you trying to output the interlock?L159[19:44:19] <bball>
why not send to the reciever first?
<bball>
why not send to the reciever first?L160[19:44:56] <Natesky9> Because, the interlock only
allows one output. You only want one train disembarking to the main
line at a time
<Natesky9> Because, the interlock only
allows one output. You only want one train disembarking to the main
line at a timeL161[19:45:40] <Natesky9> There are other ways, but
I've found that, timed perfectly, two trains can disembark at
the same time, causing issues
<Natesky9> There are other ways, but
I've found that, timed perfectly, two trains can disembark at
the same time, causing issuesL162[19:45:50] <Natesky9> This method prevents
that
<Natesky9> This method prevents
thatL163[19:45:51] <bball>
okay, explain what exactly you need to use the AND gate for
<bball>
okay, explain what exactly you need to use the AND gate forL164[19:48:55] <Natesky9> Are you talking about the
receiver connected to the interlock?
<Natesky9> Are you talking about the
receiver connected to the interlock?L165[19:49:30] <bball>
yes that reciever
<bball>
yes that recieverL166[19:50:20] <Natesky9> It's... Sorta an and
gate, since the interlock outputs the least restrictive. It's
connected to the outbound line. The next train isn't allowed
to leave until the last one is gone
<Natesky9> It's... Sorta an and
gate, since the interlock outputs the least restrictive. It's
connected to the outbound line. The next train isn't allowed
to leave until the last one is goneL167[20:46:29]
⇨ Joins: Johannes13_
(~Johannes1@dslb-094-216-121-204.094.216.pools.vodafone-ip.de)
L168[20:48:33] ⇦
Quits: DasBrain
(~Johannes1@dslb-094-216-023-108.094.216.pools.vodafone-ip.de)
(Ping timeout: 200 seconds)
L169[21:32:55] ⇦
Quits: yorick (~yorick@ip51cd0513.speed.planet.nl) (Ping timeout:
200 seconds)
L170[21:35:05]
⇨ Joins: yorick
(~yorick@ip51cd0513.speed.planet.nl)
L171[21:43:56] ⇦
Quits: Hathadar (Hathadar@c-73-20-95-143.hsd1.ut.comcast.net)
()
L172[21:53:55] ⇦
Quits: Tahg (~Tahg@pool-71-248-165-18.bstnma.fios.verizon.net)
(Read error: Connection reset by peer)
L173[21:55:21]
⇨ Joins: Tahg
(~Tahg@pool-71-248-165-18.bstnma.fios.verizon.net)
L174[22:04:39] ⇦
Quits: Lathanael (~Lathanael@p549603EB.dip0.t-ipconnect.de) (Ping
timeout: 186 seconds)
L175[22:05:41] ⇦
Quits: Tahg (~Tahg@pool-71-248-165-18.bstnma.fios.verizon.net)
(Read error: Connection reset by peer)
L176[22:06:58]
⇨ Joins: Tahg
(~Tahg@pool-71-248-165-18.bstnma.fios.verizon.net)
L177[22:11:22]
⇨ Joins: Lathanael|Away
(~Lathanael@p54960890.dip0.t-ipconnect.de)
L178[23:01:11] ⇦
Quits: Lathanael|Away (~Lathanael@p54960890.dip0.t-ipconnect.de)
(Ping timeout: 186 seconds)
L179[23:08:01]
⇨ Joins: Lathanael|Away
(~Lathanael@p549603D8.dip0.t-ipconnect.de)
L180[23:37:30] ⇦
Quits: sinkillerj (~sinkiller@nc-67-232-11-204.dhcp.embarqhsd.net)
(Quit: γΎγγ)
L181[23:52:55]
⇨ Joins: Vexatos
(~Vexatos@p5B3C9D9D.dip0.t-ipconnect.de)