Jump to content

SenorRossie

+AtariAge Subscriber
  • Content Count

    140
  • Joined

  • Last visited

Community Reputation

205 Excellent

About SenorRossie

  • Rank
    Chopper Commander

Profile Information

  • Custom Status
    Rediscovering the atari 8bit after 30 orso years
  • Gender
    Male
  • Location
    The Netherlands

Recent Profile Visitors

6,114 profile views
  1. There's always the webbased atr image explorer: https://rossumur.github.io/esp_8_bit/atr_image_explorer.htm A whole thread about it on this forum:
  2. The HCC Commodore sig meeting is held every two months in Maarssen. Once a year we take over a large part of the space and fill it with atari (related) hardware. We used to do this during the February meetings, but due to Covid and time constraints, we moved this year's edition to April. We kind of liked the fact that we could fill and unload our cars in broad daylight, so we may push for a permanent move to the April event. We have had some international aspirations: Although in the light of recent events we will hold off on travelling abroad. Then there are rumours of an extra event somewhere near Rotterdam, but as far as I know there are no definitive plans yet. TL;DR next year February or April. We will announce the date here, well ahead of the event this time.
  3. Luckily it's easter weekend, so plenty of time to rest. The feedback we got prior to and during the after event diner was very positive, so much that we think it is safe to say there will be another edition next year. Maybe this time we will be able to suppress our urge to bring as much gear as possible...
  4. All, We've kept rather quiet about this year's Atari Invasion, mainly due to the fact we didn't know whether it would take place as Covid is still all around us. Fortunately, Saturday the 16th we were able to take over a large part of the Commodore sig meeting in Maarssen, the Netherlands. We brought lots of hardware, like stunt cycle, a six switcher and the 400/800 from the early days and an Atari VCS, a modern day console plus a lot of other systems. Hopefully next year we'll have more time to prepare Pictures are available on our FlickR space
  5. Also to be used as a case for the 1088XLD. Perhaps a custom faceplate with cutouts for all connectors.
  6. I ran it on an Antonia expanded 600XL, so it should work. I did notice the intro was garbled and the timing of the key presses to skip the intro is tricky (somewhere before the intro runs), but the game runs.
  7. Rule #1: One can never have too many Ataris Rule #2: See rule #1 Some people (spouses, friends) just don't understand.
  8. There have been issues with cloudflare in the last couple of days: https://www.cloudflarestatus.com/ Atari Age responds a bit slow from the Netherlands at the moment. No errors afaics.
  9. Perhaps start by going through the topic below: Fujinet is a SIO to WiFi device capable of many things, printer emulation being one of them. There is a subforum dedicated to this device. The cheapest route is probably a DiY SIO2PC USB cable, and the Respeqt/APE software running on a PC.
  10. Great idea! Even taking this further: The 2600 forum has a subsection for the Harmony cartridge. Perhaps a multicart subsection here in the 7800 forum is an option, where info/discussion on existing multicarts can take place? More $.02
  11. What is the benefit of having this kind of separation? Maybe I'm missing something in your intent behind the idea, but I'm not clear as to how having that separation would be necessary or desirable. The intent is to have a 'trustworthy' domain maintained by some 'officials', i.e. developers of fujinet; and a 'user contributed' domain, where anyone can register that wants to be added to the list. Not a requirement per se, but I imagined a scenario where newly deployed fujinets get the official lists and a user is able to add one or more 'unofficial' domains where - for example - a user group sets up a domain for a select set of individuals, each running their own tnfs server(s). For simplicity sake, let's start with one domain, document the setup and allow others to replicate it with their own domains. DDNS certainly makes sense in situations where someone wants to run a FujiNet server from a non-static public IP. No argument there. That, however, would be best left as a function of the DDNS clinet running on their system, firewall, etc. to determine the URI of their particular site. It could be a client running on their server/firewall and as most of these already are capable of creating a DDNS request, it allows for a relative easy implementation - Knowing that Joe Average may need some help in setting things up. Hence the fact one needs to set up the client to register a site. All security concerns aside, it should always be a user choice to register a site. DNS has plenty of downsides and security concerns, but it is a proven technology and is widely used I do _not_ advocate on using a fujinet device to obtain 'the list' through DNS, so propagation time is a concern but should not be an issue per se. In my train of thought, the process would be something in the line of: - Client registers his site through DDNS, ie: usersite.fuji.net - The request is sent to (one of the) nameserver(s). - The registration of a host triggers a zone transfer on the (slave) nameserver(s) - On the slave servers the IXFR request triggers a regeneration the sitelist: - each host is checked for accessibility and if everything is oke, it is added to new sitelist file The sitelist file can be a text-/json-/yaml-/etc. file and can be made accessible in a known location, ie: - a directory on a webserver - a directory on a tnfsserver - ... The hostname and location of the file can be made part of the zone, i.e. an A record (or multiple for round robin redundancy) for the host and a TXT record for the location come to mind While I'm not disagreeing with this idea in principle, how would a FujiNet record differ from any other? An A / CNAME record with a TXT entry describing it? Again, I may be missing something in all of this, but I'm not seeing how it would differ from how DNS is normally used. It wouldn't differ, except for the fact that with DDNS you have a method for the registration part. That a lot of things need to be worked out is a given, as far as I am concerned. It seems easier to me to make use of available technology, instead of (re-)inventing something new. As far as I can tell, with the currently available protocols we should be able to make something work.
  12. Maybe. I gave the idea some thought earlier on, and am not opposed to it in concept, but my position is that there needs to be no distinction between hosts as being official or otherwise. The one possible exception of having DNS-style root servers that help to replicate directory data globally might be necessary, but, much like the Internet at large, I feel it's important to keep this as unmanaged as possible. The distinction between 'official' and user contributed hosts is entirely optional and could be as simple as using a different (sub-) domain. A pro for dns is that it has been a part of the internet for a long time, has been well documented and is cross platform. The DDNS part is also widely in use and well supported. DNS is used for registration and storing of host records, added bonus: Global distributed storage. A second step could be axfr'ing (or ixfr if using slaves*) the zone to one or more central systems, checking the records and publishing them in a format easily accessible/parsable by the fujinet device. * When using slaves to generate verified lists, an automated solution is feasable where an ixfr triggers regeneration of the published list.
  13. Wouldn't a 'simple' ddns (RFC2136 style) client simplify things? If needed you could split it into official and user contributed content. Just my $.02
  14. I'm gonna miss the regular posts with familiar and on occasion unfamiliar labels/titles. Many thanks for all the work you put into this!
×
×
  • Create New...